Tomasz Trynkowski

In that case what we need is an option to filter out that information on the PROTECT side. Or a filter for alerts in general. Having to wait several years for OSes to change is not a solution.

Anyone else that has any experience on the issue? I have still a significant number of Windows 7 machines managed by the Protect and thus so far i am not eager to update it to 11 without knowing the answer.
Specifically, i am interested not only about the status of the already managed machines, but also about whther it would be possible to add new ones (or reinstall/reattach Endpoint installations whose Agents stopped responding for one reason or another, which seems to be not so infrequent issue with 10.1 agent line)
 

Thanks for the confirm. so it seems works. but ESET may refuse to support this kind of configuration if I understand the release notes sentence correctly: "REMOVED: Windows 7/8/8.1 support".
It's strange ESET forum administrators won't answer questions like these which need to clarify  support status. maybe I needs to create ticket.

In that case what we need is an option to filter out that information on the PROTECT side. Or a filter for alerts in general. Having to wait several years for OSes to change is not a solution.

Like mentioned above, it's not an Endpoint issue (as we can already disable this notifications on clients). It is a Protect issue, because even if the notification gets disabled clientside, Protect still shows it.
There's no need to update old Endpoint clients to not send this notification. What is needed is a Protect setting to not show it.
And yes, it should work for systems older than Windows 10 too.

Like mentioned above, it's not an Endpoint issue (as we can already disable this notifications on clients). It is a Protect issue, because even if the notification gets disabled clientside, Protect still shows it.
There's no need to update old Endpoint clients to not send this notification. What is needed is a Protect setting to not show it.
And yes, it should work for systems older than Windows 10 too.

Description: Disable Warning "Your operating system is outdated" in ESET Protect
Details: On the clients we can disable this warning, need options to hide on ESET Protect too.

ESET PROTECT console: Products should not be marked as outdated until the next product's auto-upgrade is released.
Let's refer to this existing post:
 
My ESET PROTECT console dashboard's Component Version Status is lit up in red (Legacy) despite being properly configured for automatic upgrades/updates and all of the clients being on EEA v9.0/9.1. The endpoints' status should remain in a blue "Waiting" status for any supported versions until the auto-upgrade is released.
 

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.

There's also one more peculiar issue tied to this that i have noticed. There is actually a setting that (on surface) seems it should do exactly what was asked for in this thread. It's in agent policies (advanced settings/operating system block). And it even works! It disables the system out of date notification! Except, it works on the notification that is shown locally, in Eset Endpoint Security. It does not prevent the agent from pushing the very same notification to Eset Protect. 
Which is the exact opposite of what i'd expect. Personally, i'd think that notification settings for each local Eset Endpoint program instance would be in Eset Endpoint policy (hint: they're not present there), and the Agent policies would be tied to Protect notifications only. Instead, it seems to work sort of backwards, completely counterintuitively.
I'd suggest moving the local notification to the notification settings in Endpoint policies, and switch the already existing Agent setting to work on Protect client status reporting instead.

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.

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.

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.