kingoftheworld

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.

I seriously don't understand why these settings cannot be the same between platforms. There are those that prefer to use the simple password protect settings mechanism on macOS.

I know many are reporting widespread issues, but I have seen this exact error message when the HDD fills up.

I am interested in getting a copy! Is this product geared towards file servers, linux desktops, or both? Also, would I need to have ESMC 7 deployed to manage it? We are running 6.5 and planning our upgrade to 7 for later this year.

The way that I have gotten around this is to make a "Shared Permissions" static group. Then, give the permissions to both user groups that need to access the license.

Please include me!

It looks like you provided full access to only a select few Static Groups and the license it probably in the top-level (All) access group which this account doesn't have access to. You will either need to provide access to the static group that the license is at, or move the license to a static group that this account has access to.

Any ETA on a fix for this issue? Yesterday, I experienced this popup no less than five times throughout the day without any interacting with the ESET GUI.

Not necessarily related to ERA, but for the enterprise A/V products Description: Consistent handling of update profiles between Windows and macOSDetail: I would think that two products that are essentially branded the same should operate the same between platforms, ESET Endpoint A/V 6.* for Windows and macOS. When configuring update profiles to pull from an internal mirror on a PC, you essentially have to go in an update the the task for the update to use your internal mirror first, then use ESET's servers second. However, when you manually trigger the update now using the GUI, this fai