MarkR

will there be a similar update to ESET Endpoint Antivirus for macOS?

Is there a newer build of 10 coming soon with the email processing optimizations?

thanks Marcos!

I see that ESET Server Security 9.0.12017.0 has the specific update for this issue: IMPROVED: Protected antimalware service will not time out any longer during boot when Windows updates keep the file-system busy But does version 10 of Server Security experience this issue? I don't see a similar improved item on the latest changelog notes of 10 (10.0.12010.0) thanks

@Marcos does that last post mean there are still known issues with the Outlook plugin that comes with endpoint antivirus v10.0.2045.0 ?

@Marcos did you see my question above? posted March 15

When you say why are you using an old version V6, that's confusing. In my Protect server, when I look at the status of a Mac system, it says "ESET Endpoint Antivirus 6.11.606.0 Up-to-date version" so that looks like we are on the latest version. Are you suggesting we upgrade to version 7 on Macs? Every time I've called into support and asked them about version 7, they say that most people are not using it and to stay on 6. Is that not the case? Also, when updating to version 7 you mention uninstalling 6 first and then installing 7 - is that the recommended procedure we are supposed to use versus installing 7 over 6 (in place upgrade)? thanks

this is really frustrating...some machines appear to be able to check in after a wakeup call just fine and others are not

now the wakeup calls aren't working for some machines

I will repeat in that this never happened until we started upgrading to version 9. And this should be more clearly specified by ESET if we are not supposed to deploy Endpoint with one method (like GPO or Ivanti) and then continue to maintain is via ESET Server via upgrade tasks..how the heck are customers supposed to know that??

no the Agent upgrades are going fine. Endpoint is failing when upgrading via software install task. This only started happening with version 9

We are transitioning to SCCM so we will probably start deploying ESET to new machines using SCCM soon instead of Ivanti - we don't use GPO to deploy

we upgraded the previous Agent (which was version 8 ) by using a Component Upgrade task from the PROTECT server. The agents have been upgrading fine to version 9. The problem is upgrading Endpoint Antivirus from version 7.3.x or 8.1 to version 9. Most of the upgrades I have been doing have been from the machine details using the Installed Applications -> Update ESET Products and then choosing the latest version from the selection list. Another colleague of mine has been upgrading groups of machines using a software install task from PROTECT. Initially, ESET was most likely installed using Ivanti task - which is our asset management software via the Ivanti agent which is on all PCs. We use the all-in-one installer for that so it installs both Agent and Endpoint. Now we are scared to upgrade any systems.

ha - so all of a sudden today the Wake Up call is working fine - we didn't make any changes on our end. working perfectly now

I am experiencing the same thing here as JCUA. Most upgrades from 7.3.x or 8.1 to version 9 are going fine, but we have had several fail, and leave the machine with NO antivirus protection at all. Another one failed this morning (sent an upgrade task to update 8.1 to 9 and it failed - and has so far taken me over two hours to troubleshoot with the user. Seems I am not alone with these issues. This is causing a HUGE problem for us as everyone is working remotely and the only way to resolve it is to literally work with the user to get them to restart in Safe Mode and run the esetuninstaller tool and remove whatever it finds, then reboot and install from scratch. This process comes with many challenges including the user has no local admin rights, system won't boot into Safe mode with Networking so we have no remote access or ability to screenshare, and now machines are even getting caught in a Safe Mode reboot loop as they can't change the setting in msconfig to boot into normal mode. This is a complete mess and I am afraid to upgrade anyone else to version 9. To be clear we had had ESET since version 5, and this has never happened to us, these upgrades only started happening to us with upgrading endpoints to version 9. Looks like it's not ready for prime time.

we are experiencing this as well when upgrading endpoints to version 9. This is EXREMELY frustrating. We never had this problem with upgrading from 7.x to 8.x. Two weeks ago we upgraded our PROTECT server to version 9, and then we upgraded the Agent across the endpoints. Now we are upgrading endpoints to version 9 (most are on 7.3.2044.0 but many are on 8.1) and several of them are failing, and when the machine checks back in, there is NO antivirus installed at all - only the Agent. After working with a support tech they instructed me that we have to reboot the machine in Safe Mode and then run the esetuninstaller command line tool, and remove both the Agent and the leftover BS from Endpoint Antivirus, and then reboot, and then reinstall ESET all over again. Now because everyone is working remotely this is actually BRICKING some machines, as now we are running into situations where the user goes into Safe Mode (even though we try Safe Mode with Networking it's not able to connect to Internet) and now they are stuck in Safe Mode loops as msconfig cannot save the setting to go back into normal mode -so they literally cannot use their machine anymore. I just spent the last hour troubleshooting this with a user and we are having to have her drive her laptop in since her machine is unusable now. Luckily she isn't far from our HQ but if this happens to people working in remote offices we are screwed since this effectively leaves the machines totally unprotected. This never happened to us when we upgraded machines from 7.x to 8.1 - this only started happening with upgrading to version 9. This is a total disaster to deal with since users don't even have local admin rights, so we have to either connect to them first and reset the local admin password to something we can tell them, or elevate their rights to local admin, but then we still are experiencing the Safe Mode loop since Windows 10 can't seem to figure out how to boot into Safe Mode with Networking. And of course we have to talk through explaining to non-technical users how to find the esetuninstaller tool and run it, since we have no remote access or screen sharing in Safe Mode. This situation has left me scared and not wanting to upgrade any more machines to version 9 which is not a good place to be in. I love ESET but this stuff is killing it for us and makes it hard to remain a customer. The amount of time it's taking us to troubleshoot these issues is too much. If everyone were onsite it would not be nearly the challenge that it is with everyone being remote, and it these upgrades fail for VP or C level people and we have to walk them through having them log into Safe Mode it will be a disaster. Maybe version 9 isn't ready yet??

I've even tried running a Wakeup Call to the PROTECT Server itself, locally, and even that doesn't update the Last Connected timestamp

confirmed that communication works

We recently upgraded to PROTECT version 9, and mass upgraded endpoints Network Agent versions to 9 as well. Last week whenever I sent a Wake Up Call to an endpoint and hit refresh the timestamp of when the machine checked in would update to that time immediately as it always has in the past. However, today whenever I send a Wake Up call to a client and hit refresh it does NOT check in, and the last connected timestamp remains the same. I now have to wait until the Agent policy check in time for the Last Connected timestamp to change. Anyone else experiencing this?