I am trying to setup a new AV installation at work, replaceing trend officescan with Eset NOD32 V4.

I have installed the Remote admin console, and the Remote Admin Server so that the clients can get their updates from the server rather than clog up our internet connection.

The problem I am having is building a client package that gets its updates from the central server. The install guide is pants TBH and difiicult to follow, so I am looking for help really.

The Admin server was installed using default settings, and I have managed to get the admin server downloading updates from Eset.

What I cant get working is a client configuration that will pull down the updates from lets say ServerX.

I'm afraid this post is going to be of no real use to you.

Here at work I've always used the Symantec Corporate AV solution.

It "just works" and is an excellent piece of software, really cannot fault it.

Unlike the consumer Symantec products, the corporate one never really became bloated at all.

When the licenses were up for renewal we looked into NOD32.

I use it at home and love it - tiny platform size, really quick etc.

We too wanted a fully managed central system that all of the client machines would communicate with for updates etc.

We just couldn't get it up and running correctly.

We spent our whole trial time backwards and forwards with NOD32 techs and online forums and got nowhere.

In the end we had to abandon that and we went back to using Symantec products and rolled "EndPoint Protection 11" out to everyone instead.

Once again this just works out of the box and is a great centrally controlled system.

I managed to get it all working today, it took a while though.

I have deployed the updates to the test clients, and they are all now communicating with and updating from the central server on our lan.

From the admin software, I can see the status of all the machines, run reports and all kinds of stuff relating to the desktop clients.

Nod support forums are over at Wilders Security Forums - Powered by vBulletin

There were some issues with V4 and servers, which are due to be sorted..apparently.