Marco Maes

Tnx for the responses and tips. I opened a ticket as you suggested en we are working on it. Will let you know when the problem is fixed and how it was fixed. Till then, let's try your ideas by turning everything off and slowly turning things on...

Hello, This week, we started to use ESET Endpoint Security Advanced for Mac. Here is some information about our implementation. We use ESET Remote Administrator: ESET Remote Administrator (Server), Version 6.4.304.0 ESET Remote Administrator (Web Console), Version 6.4.281.0 At the time of posting this topic, we have 32 Clients using ESET Endpoint Security Advanced for Mac version 6.3.85.1 and all are deployed using the EraAgentInstaller generated by the ERA Server. The clients all have different OS versions. The oldest is 10.10.5 and the most recent is 10.12.1. We applied the policy that was build in: Antivirus - Maximum security. Then we also applied a custom policy to exclude TimeMachines from being scanned as everybody is connected to a TimeMachine on our NAS (Synology). The policy defines the following folders from being excluded in Real Time Scanning: /Volumes/*/*.sparsebundle/*.* /Volumes/*/Backups.backupdb/*.* /Volumes/Time Capsule/*.* /Volumes/Time Machine/*.* /Volumes/Time Machine Backups/*.* Since everybody is using this configuration, everybody is complaining about performance issues. Here are some of the complaints: A spinning "beachball" E-mail extremely slow (seconds to switch between two e-mails (using secure IMAP) Laptops that cannot reboot without a hard reset Complete random freezes for a few seconds Webpages sometimes won't load For now we lowered the policy from Antivirus - Maximum security to Antivirus - Balanced to see what happens. But I cannot believe that a good protection provided by ESET has this much impact that systems our barely usable anymore. Can someone help? Maybe there are more people with the same problems... Or better, maybe someone knows a solutions.

Thank you Grettir for your post. I have exactly the same problem and couldn't described it better. I'll follow this topic to see when the bug is fixed.