Some Windows Servers not auto updating ESET after last weeks windows updates

[OllyOrc 1]

Everything working fine on all servers (2012 R2 & 2016) except for some that received windows updates last week and were rebooted but show their last update was over 3 days ago (9 days ago that ties in when they were windows updated and rebooted). However they all show they have communicated every day, including today and have no problem being manually updated, so my question is why they haven't been able to auto update and is there something I can do to make them auto update, please? 

 

Many thanks and kind regards

 

ESET Security Management Center (Server), Version 7.1 (7.1.503.0)
ESET Security Management Center (Web Console), Version 7.1 (7.1.393.0)
Copyright (c) 1992-2019 ESET, spol. s r.o. All Rights Reserved.

CentOS (64-bit), Version 7.7.1908

 

Update module	1074.1 (20190925)
Translation support module	1775 (20191107)
SysInspector module	1274 (20180918)
SSL module	1041B (20190913)
Push Notification Service module	1055 (20191107)
Configuration module	1822.1 (20191028)

Database info:

DB Version: MySQL 5.6.40

 

[MartinK 384]

In case you are using corporate or ESET HTTP proxy for updates, please verify it is working correctly. Manual update might help as in that case also user's proxy is used, which might have different configuration.

[OllyOrc 1]

Thanks for the fast reply but no proxy being used and all of our other windows servers are communicating automatically, just not these 12 that had their windows updates last week.  

[Marcos 5,462]

Does EFSW update if you right-click the regular automatic update task in Scheduler and select Run now?

Does the time of the last task execution change when modules are not updated automatically?

[OllyOrc 1]

Hi Marcos, 

thanks for the reply and I right clicked on the client's regular automatic update task in Tools -> Scheduler but the time didn't change for the last execution and the windows server still appears in the Security Management Center Dashboard Last Update > 3 days.  

Kind regards

Edited December 13, 2019 by OllyOrc

[Marcos 5,462]

It appears that you have update tasks doubled. Did you apply a policy with scheduler settings and the option to prepend or append the settings? Would it be possible to try a clean installation with default settings and with the ESMC Agent service temporarily stopped to prevent policies from being applied?

[OllyOrc 1]

Thanks Marcos,  I will investigate why the update tasks are doubled but can't reboot the servers until next month's patch Tuesday. 

 

** I examined the custom policy on the Security Management Center and edited the Tools -> Scheduler -> and unticked Regular Automatic Update. Then left that to propagate around to the clients and then reticked it again and that appears to removed the duplicate tasks. So the affected clients now only have the tasks set by that custom policy. 

However, there was one server that I had to manually remove the duplicated task for Regular automatic update, on its clients Scheduler settings. 

Therefore I think the policy had got a bit confused and just required reinstating but will have to see how next month's patch Tuesday affects the servers. 

Edited December 16, 2019 by OllyOrc