Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Maybe you could use the web interface to configure the server they way you want, then export the settings and apply them to other servers? Web Interface Configuration Or, are you trying to get the license applied in order for the server to connect to eset.com and download updates? Activate ESET File Security 8 for Linux Or, do you have an old license type? If so, convert the username/password into the newer license key? License converter
  2. We run EES and CbR as well. We usually see this happen with external storage and time machines (usually 100,000's of files, suspect it's trying to scan them all). Also, when an installer is mounted and has adware, EES and CbR will go back and forth touching the same file causing high CPU usage. Seems as though EES goes to scan it so CbR touches it, then EES sees CbR touch it and scans it, etc, etc... We've had 60,000 events get logged in our ERA in an hour due to this. Mostly happens with mounted installers, so just get the user to unmount it.
  3. Our current policy locks all settings with a password. Therefore, users cannot change any of the settings. We originally deployed ESET for the first time last year with version 6.4.2014.0, replacing Symantec Endpoint Protection. With SEP, we could upgrade versions without users knowing it. No splash screens, no notifications, no calls to the support desk. This is our first update to EES in our environment since initial deployment. We have a small group of about 20 machines that we have been testing newer versions. The last version they had before getting 6.6.2072.2 was 6.6.2068.0.
  4. Thanks. Although I opened a ticket for this issue and was told it was expected behavior.
  5. If we do a rename task using ComputerName, the Active Directory sync won't match up. If HostName was an option in the rename task, it would work because we have the FQDN set as the HostName. Then the AD sync will match up correctly. So if you gathered HostName as a Device Identifier on a Mac, you could add HostName as an option in the rename task which will make getting a FQDN to match up with an AD sync much more reliable. Or, at least something a company using LDAP/AD has a chance for a more reliable method of getting FQDN. Also, we can't use FQDN as the ComputerName because it woul
  6. Since there hasn't been a response, I'm hoping you were able to recreate this issue and are working on a fix before responding? If this is the case, is there an ETA on a fix? We are holding off on our 6.4 -> 6.6 upgrade for Windows machines until we hear back. We would prefer to not risk user phone calls to the support desk due to notifications showing up if we can avoid it.
  7. Here's the results: testmac.example.com testmac.example.com testmac.example.com Here's locale: LANG="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_CTYPE="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_ALL= If this is similar to the method that is being used by the server, then we know why we are getting these results. Here is the NSLOOKUP results from the test machine: testmac.example.com:~ username$ nslookup testmac.example.com Name: testmac.example.com Address: Name: testmac.example.com Addre
  8. This occurred immediately after upgrading the server from 6.4 to 6.5. All the machines with this issue should have had both the Agent and Endpoint Security before the upgrade took place. Sorry for being unclear. We discovered the removing from the console was not a good idea already. So I wasn't planning on doing that again. But, because removing from the console wasn't a good idea, we want to try uninstalling both the Agent and EES and then reinstall again. Hopefully it will generate a new GUID and we'll see if this was caused by the upgrade process or due to still existing issue.
  9. The Device Identifier has the doubling as well. We have a hourly rename task. It ran 15 minutes prior to the above screenshot. Rename is based on Computer FQDN. Active Directory sync runs hourly as well. We are going to try uninstalling Agent and Endpoint Security and reinstalling to see if it will resolve. We found that when we deleted the computer from the console, it reconnected with the same GUID. The trace.log showed that no data needed updating after it saw the deleted machine had the same GUID so the computer name still was doubled.
  10. Several Macs have the \266\128\153 in the name. Appears to be a single quote. U+2019 RIGHT SINGLE QUOTATION MARK, 0xE2 0x80 0x99 in hexadecimal, or 226 128 153 in decimal. So that explains what that part is, but not why it's displaying that way.
  11. We upgraded from Server 6.4 to 6.5 and started seeing about 5% of the Macs with their names displaying doubled, eg. hostname hostname. Some seem to have strange path names in the computer name. Not all Macs have been updated to 6.5 Agent and 6.5 Endpoint Security. There are both upgraded and not upgraded Macs with the doubling issue. I've tried deleting a Mac from the Console and when it reports again, it has it's name doubled again. Server 6.5.522.0 Web Console 6.5.388.0 EES for macOS 6.5.600.1/6.5.376.0 Remote Agent 6.5.376.0/ Below are Macs that show the name doub
  12. Also seeing Windows notifications as well. Shortly after this displays and checking the GUI, there are no issues showing. But, there is a reboot required showing in the console, so I'm guessing this is being displayed due to the reboot requirement. I'm going to guess that none of our polices are applying immediately after the upgrade occurs.
  13. Just noticed on another system after the upgrade, in addition to the splash displaying, an "all moduled updated" notification displayed despite a policy not to display such notifications.
  14. We are deploying Endpoint Security 6.6.2072.2 for Windows (from 6.4.2014.0) with a policy to not display the splash screen. After the upgrade occurs and EES is launched for the first time, the splash screen is displayed even though there is a policy to not display the splash screen. It does not display if you log off and back in again, or on reboot.
  15. The post says 6.6.2072.2 did you mean that or is there another 6.6.2072.3?
  • Create New...