Update to v 2.50.25

We are currently running NOD32 RA Server downloading from ESET.
We have 3 servers replicating and downloading from the first server.
We have 1 final server updating from one of the above servers, using replication.
There are PCs updating from each of these servers.

We have configured all servers and PCs to automatically install all Virus updates and Program updates.

When the latest version was released each server updated and then sat there waiting for a reboot.
Until a reboot is completed, no virus updates are downloaded.

This meant that when the two updates came out today no PCs or servers were up to date.

Is there a way of getting around this problem or is it due to be changed in following updates?

 

When any PCU is released it is necessary to reboot the machine once it's been applied.

Personally I always set servers to not upgrade unless required for proper virus database functioning, you can then plan the downtime and do the upgrade when convenient.

 

Thanks for your reply Rolfy.

We had previously thought of doing that, but with the number of servers we have, we were hoping for less labour intensive updating.

Does this also mean that the mirrors will not be updated until downtime is arranged?

Right, Off to the pub tonight.

Thanks for your help

 

Hi Jersi, mirrors will still be updated with the new version so the clients updating from these will get updated no problem.

If you wish to manage the whole process of when clients/servers upgrade so you get no surprises of new versions automatically installing you should use the setting under the mirror of require permission for PCU, you can then control whether the new PCU goes into the mirror.