Server Patching

[Mr.Gains 4]

ESET Agent : 9.0.2141.0

ESET PROTECT: 9.0.2144.0

ESET Server Security: 8.0.12011.0

We setup tasks to trigger patching, what I've noticed is that the task are shown finished but aren't. For example we had a server complete the updates 4am in ESET console but it didn't finish applying the updates until around 8am. I'm guessing the task is marked finish after the server checks in after the reboot even though it's applying updates? Information isn't useful especially in our production environment where we need the services running. Advanced throttling is default, target local time is unchecked.

[Mr.Gains 4]

Could I get an update before the next patching window? I noticed this in two different consoles/domains.

[Mr.Gains 4]

Does ESET do any validation to ensure the update finished applying?

[MichalJ 434]

Hello, per my understanding, the task is "finished" when it was handed over to local "WMI" Provider, that triggers the operating system update by the system. But the status "finished" from the console perspective, is not triggered by any crosschecking mechanism that the update has really been applied. That would be achieved only when the "operating system is not up to date" warning disappears (if checking enabled).