Campbell IT

I'm seeing the same thing... about 30% of the clients are showing the alert, and I haven't found a common thread.  They are spread across 9.0.x versions, network locations, and install dates.

We have decided to go ahead and update the clients to version 10, but we definitely feel like ESET has abused us as a customer.  It's not a good time for us to dedicate the resources with holiday out-of-office staff, year-end close outs, and a SOC2 audit on-going.

Absolutely! Most IT Admins know their environment well enough to know which machines are not up to date. I want my ESET product to tell me when there is a problem with ESET.

Absolutely! Most IT Admins know their environment well enough to know which machines are not up to date. I want my ESET product to tell me when there is a problem with ESET.

Absolutely! Most IT Admins know their environment well enough to know which machines are not up to date. I want my ESET product to tell me when there is a problem with ESET.

Will it become possible to remove this notification in the future? As it is, it's a problem that really needs a solution.
I am fully aware which OS which of the computers i manage are running, and this notification is not going to push me into making any changes to that state. All it does is hide other notifications (like OS having updates). As such, not being able to disable this notification turns it from help into actual hindrance.

I notice on all installs of ESMC that the message in Status Overview always comes up in RED!  "Notifications containing in accessible objects. " and has number. This is referencing the Notifications which do not have email address added to notification. Why is this the default especially if the customer is not using SMTP server settings to send out notifications?  It throws off reporting. Is there any way to resolve this outside of adding an email address to ever single notification which I usually highly recommend not doing as it creates to much noise for the customer getting the notifications. 

@TheMartin Thanks for the feedback / suggestion. I will contact our documentation team, and ask them to prepare the tutorial (video / documentation) with the topic "how to update my ESET environment on the latest version in the simplest way". I agree, it would be a helpful content, which should be more actively promoted in documentation and KB. 

Thanks Michal, I guess what would be nice at this point is a simple tutorial how to keep the agent and security product up to date on a group of systems.  So I have a server group I deal with manually, but for workstations I just tick the "do not reboot if required" box and let the user reboot when they see the message.  I'd just like to automate for all of them.  I have found the "outdated applications" panel so I've been using that for the week, which I guess is the simplest method at this point. 
Looking forward to micro PCU and auto agent updates in the future.