Garrett Brown

No new Mac Agent?

We desperately need a workable Mac Agent. I've been testing the new 9 beta and there is the same Mac agent. Any ideas when we can see a new usable Mac agent? -Garrett

John Watson

said
about 3 years ago

Thank you for the post. Unfortunately we have not been given any time for when a new Mac agent will be available at this time.

If something is not working correctly for you please contact support so we can assist you in finding out why it is not working.

G

Garrett Brown

said
about 3 years ago

OK, thanks for the info. The current Mac client only performs scheduled scans, scans very slowly (completes in days), significantly affects machine performance and can create log files as large as 100Gig (Yes, you read this right). We have to create an extensive list of exclusions to keep them running at all or they just run forever and create these enormous log files. We are running the latest version across our hundreds of Macs 3.2.19. I'm not so interested in contacting support as it is the same routine every time and ultimately its due to a very imperfect piece of software which can really only be addressed if there is any development in a new client.

Garrett

John Watson

said
about 3 years ago

The log file issue should not be occurring with the current 3.2.19 agent. That was an issue caused by the older agent version not rolling over the logs. If that is still happening on your machines, I'd like to know why. I haven't been able to reproduce anything like that on any of my current test machines, but occasionally we do get a report from client still running the older version and after upgrading and clearing the logs it doesn't come back.

We are always looking for ways to improve the performance and features in the Mac agent. I do know that the developers are working on it, I just don't have any dates that I could give you at the moment.

G

Garrett Brown

said
about 3 years ago

Well its definitely occurring on the 3.2.19 client and I specifically traced this issue down to machines running Outlook 2011 with large email DBs. In these situations the scan frequently doesn't ever complete (Seems like some circular event) and generates enormous log files (20-100Gig).I've been able to avoid this issue and shorten the scan times but creating exclusions for the Outlook Data directories. It may be occurring on Outlook 2016 too but I wasn't able to definitively document this but I have added exclusions for those directories too.