![]() ![]() It there an protection, which disabling resolves the issue, or you have to uninstall the endpoint completely? Later in the steps you mentioned you pushed an agent and the Endpoint itself, so it means that the Endpoint was installed before in an non-managed environment? ![]() Would it be possible for you to send me an exported configuration from such machine? Or even better with the info_get script output as described here?: hxxp:///kb3404/can you please run it right after the issue occurred? You stated, that only real-time protection is enabled, right? It does not help, so it has to be that particular feature. We would like to reproduce it internally here, but I'm not sure about the exact steps -( Often esets_daemon freezes OS X completely for about one minute before a number of other issues occur, such as esets_proxy no longer functioning, module errors, and more. And previous bugs/fixes involving Web Access Protection sound suspiciously like what we're experiencing: Early testing with Web Access Protection and Email Client Protection both disabled shows a marked reduction in those symptoms. We were experiencing hard locks when connecting to wireless networks, random 1-2 minute system freezes w/beachballing, etc. Second, you might want to try disabling Web Access Protection and Email Client Protection, at least as a troubleshooting step. We've been battling almost identical issues here.įirst of all, keep in mind that managed Mac clients may be ignoring exclusions right now, and ESET + Time Machine can bring a system to its knees. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |