kingoftheworld

I am aware of MSFT's offering for this, but I think this requires MS Defender to be deployed and running on the endpoint. I expect that would cause issues running ESET side by side.

While I know this isn't a current feature, this is something that I think would be a great addition to the product. Something that monitors a key set of 3rd party apps and specific OS patches that are missing reporting back to the console.

If you are simply changing the IP, you could do an DNS record, edit your policy to use the DNS name, then change the DNS record to your new IP.

When is this next service release due out?

Any update on the release after 8.1?

Since ESET Protect 8.1 was just released, Is the next service release coming in the near future? I have the upgrade scheduled and planned but determining if I need to delay pending this next service release.

Can you provide documentation on how to approve the EULA via the console? I searched through the KB and couldn't find anything to show me where to look or what to do.

I would download a fresh copy of the WAR file from ESET's website, move the era.bak and era.new folders to a 2nd location as a backup, then restart the Tomcat service. That should re-create the ERA folders and restore access. This should get you operational again unless you have a special distributed setup.

Yes, I can confirm this behavior on at least macOS Big Sur devices. I opened a ticket with support and was essentially told that ESET support for Big Sur is not fully available even though their public facing support page says it is fully supported minus the firewall and device control. I was told full support is coming in March with a new version that I hope fixes this. It is rather annoying to have to uninstall ESET to install critical OS patches.

I already have, and they pretty much gave me the option of hiding the GUI entirely or upgrading. I just hope the feedback received makes the decision makers behind these decisions re-think this next time.

This is not accurate. The current notification causes a Windows notification and alert sound upon logging into the machine which draws attention to the GUI.

You are assuming that I plan to deploy 21H1 in the near future. The users in my environment will actually never have access to 21H1.

At least for me, the issue with the notification is causing me to receive un-necessary support tickets from my end-users thinking there is an issue with their computer when in fact there is nothing wrong.

That's not the point. This was not well executed by ESET. This message should have been displayed to the admins in the console and not on all endpoints without the ability to control it.

On a similar note, can I ask why there isn't a way to hide this message on the client via policy? There is an option to disable every other alert message on the client but this one. In my environment, the end-users need to not worry about the agent/product being out of date as that is handled by IT. We are actively working on it and don't need users calling and telling us.