Tomasz Trynkowski

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)

Now, that would be a shame, since due to legacy app dependencies upgrading those workstations from windows 7 up is not an option. Especially seeing as 9.1.2063 version seems to be working fine on them so far. I understand from your post that this version will also be artificially disabled after December 7?

As you can see the only 9.1 version available is the 2066 one. This version does not install on windows 7 - you cannot upgrade past 9.1.2063. And 9.1.2063 has been removed from repository, as technically it is not the newest 9.1 version anymore. I'd rather not have to actually downgrade Eset products in the future, as that would be counterintuitive.

"Computer with outdated operating system" is a completely different issue. It doesn't tell you if there are updates to be installed on that computer. It tells you that you are using an old operating system version (i.e. Windows 7). Those warnings indeed seem to have been disabled (and good riddance, tbh), but the ones for updates in the queue (the ones you want) are still there.

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.

There's also another reason for why only some of the managed workstations get updated - the reboot issue. Basically, the autoupdate "queues" the update process, but the actual update doesn't seem to take until a system reboot happens. And the automatic update process (unlike a scheduled update from Protect) does not cause a reboot by itself. So, if you have workstations which never get turned off by themselves, they may never get an automatic update until it's force-pushed on them.

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.

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.