‘Had my client running the Buisness Ed. of ESET’s NOD32 but it was v2.x (cobwebs compared to their latest, but still did a great job of protection on the XP PRO workstations) and a problem came up with the auto-distribution of the updates.
I got on the telly with their support and they fiddled around a bit, but they’re up on v4.x nowadays so they didn’t even remember where the updates were configured in the v2 server, so they kindly gave me a full upgrade to their v4 suite. Here’s how it went down: Beautifully.
1. I had to uninstall everyone’s v2 client manually. Thankfully we don’t have hundreds of workstations, so I was able to run this individually on each machine. The uninstall of v2 was very clean and fast. Needed a reboot on each, tho. :-/
2. Installed the NOD32 server component/service on my Win2k3 server. (Smooth, and some options to navigate through during the install. Not bad.)
3. Installed the NOD32 RA (Remote Administration) client on my Win2k3 server to monitor all the clients and control the server. OKay, once again, even smoother – no real options here, since this is just the server’s control center for all operations.
4. Using the RA Console, I created an initial install “package” that contained the NOD32 Biz Edition install package. Then went thru all the configuration options that are to be pushed down to each client after the software is installed. Like making a “group policy”, you set up the options once, and they’re used for each push-install. This took the most time, just making sure all the settings were exactly as I wanted them. For the most part, ESET did a good job of setting things appropriate for a business environment. I cranked up a few things, and turned off a few notifications for the end user, so it just “did it” rather than asked first. (Oh, don’t forget to turn off the email signatures on all in/out email. Only if the email is/was infected is a much better setting). Overall, working in this configuration editor is pleasent and quick. There’s just a lot of options, so grab a coffee. Many areas you can skim over.. and don’t be fooled by the major branches/options at the bottom of the tree. The last couple major branches are meant for pushing this config out to another NOD32 server/service.. not clients.
5. Saved the config with the install package (binary) and then went to Push-Install them on the machines on the LAN. After supplying the administrator pwd for the domain just once, it ran through the whole list of workstations and it sucessfully pushed, installed, set config, and started up each one.
No reboots necessary, each workstation was now running the latest and pulling updates from the HTTP client that the server component has built in. I opted not to go with the mirror folder, since the HTTP connect from client to server works just fine.
The only change I had to do was the port number for the clients connecting to the HTTP server. The ports used to be 8082 in v2.x but now the default is 2221 so the syntax changed from http://server:8082 to http://server:2221
Much love to ESET. I even set up the whole enterprise suite (clients and server) to email my admin address whenever anything happens (client can’t update, virus found, submission back to ESET, etc).
/m