rpremuz
May 15th, 2005, 03:53 AM
Hi!
In NOD32 v.2 Control Center you can set the type of update of program components to automatic.
Although the option is enabled it seems that NOD32 v.2 is not updated to v.2.5 automatically. It must be done manually, right?
Somebody said that NOD32 uses "set and forget" philosophy ;)
I administer NOD32 in corporate network environments using NOD32 Remote Administration Console. What is the best procedure for updating NOD32 to v.2.5 in that case?
What about the following procedure:
1. update the NOD32 administrator to v.2.5
2. update the NOD32 mirror to v.2.5
3. create new configuration files for client computers (.xml) with new options specific to v.2.5
4. create new installation packages for NOD32 v.2.5 and include new configuration files
5. install the new packages to client computers
BTW, it would be nice that ESET releases some documentation (in PDF) for NOD32 v.2.5.
-- rpr. /Robert Premuž/
In NOD32 v.2 Control Center you can set the type of update of program components to automatic.
Although the option is enabled it seems that NOD32 v.2 is not updated to v.2.5 automatically. It must be done manually, right?
Somebody said that NOD32 uses "set and forget" philosophy ;)
I administer NOD32 in corporate network environments using NOD32 Remote Administration Console. What is the best procedure for updating NOD32 to v.2.5 in that case?
What about the following procedure:
1. update the NOD32 administrator to v.2.5
2. update the NOD32 mirror to v.2.5
3. create new configuration files for client computers (.xml) with new options specific to v.2.5
4. create new installation packages for NOD32 v.2.5 and include new configuration files
5. install the new packages to client computers
BTW, it would be nice that ESET releases some documentation (in PDF) for NOD32 v.2.5.
-- rpr. /Robert Premuž/