Eset nod32 has surprised me with its simplicity and lightness.
After working with Symantec for many years and getting used to the thick and resource demanding SEP (Symantec endpoint protection) the nod32 seems to work without bothering the end user and does what it suppose to.
After implementing it on several networks I have realized I cant upgrade the client installed AV when a new version came out without central distribution software like Microsoft SMS or System center configuration manager.
The main problem I had, was to determine the current version of the AV installed on the client’s pc and compare it to the new published version I wanted to install so it wont be installed every time the user logs on to the network.
The solution I implemented eventually was in a form of another script. Because I already installed the nod32 through the login script, I’ve added to the installation script another script to extract the installed version from the registry, compared it to a preconfigured/new version and installed it as if its an older version.
Here is a sample script: For the script to work you need to change the NewVer to the nod32 version number you want to install and download it to the shared ESET directory and EsetSrv is the server holding the shared ESET directory.
rem Check installed version and upgrade if necassaey
endpoint security definition endpoint security consoleTAGS
CATEGORIES