Confused of NOD32 server versions

Hi,

I am about to set up NOD32 on a Small Business 2003 server. I did once set up NOD32 v2.7 on a similar server, and it works, though I have to admit that I don't fully understand how and why...

Anyway, now with NOD32 v3 Business available and all, I decided to do a test install to learn this thing properly.

But, under the Download section, I only find Remote Administration Server & Console and the NOD32 Antivirus Business client as new versions.

What about LAN Update Server and the Exchange scanner? Are these still only available as v2.7? Should I mix the v2.7 LAN Update and Exchange clients with Remote Admin Server/Console 2.0.110 or stick to v1.0.15?

In short, what is the recommended setup for a Small Business Server 2003; that is, which modules should I install? If I just know what to install, I should have a good chance to figure out how to configure things afterwards.

I really would like to see some completely updated documentation about this, as the server setups are complicated enough as it is.

Thanks a lot for any help!

 

There is no Exchange scanner (NOD32 v3 for Microsoft Exchange) - available for the public . However , there is NOD32 v2.7 XMON component for Exchange .

The so called "Lan Update server" is integrated in both Business edition and in the ESET Remote Administrator Server.

You'll be more than fine if you install NOD32 v2.7 + XMON on the MS Exchange + ESET RA v2.0.110

With the new version of ERA one can administrate both NOD32 v2 and v3 . It also supports updating/mirroring for NOD32 v2 , EAV v3 and ESS v3.

If you are going to use the Exchange , you have no choice but :

- Install NOD32 v2.70.39 on the server
- Install NOD32 XMON v2.70.39 on the server
- Install ESET Remote Administrator Console v2.0.110 on the server

Protect the workstations with either NOD32 v2 or better with NOD32 v3 or ESS v3. Make them update from the Mirror created by ERA v2.0.110


Note ! On the server you must have IMON completely disabled / not installed!!! You must open AMON and configure its exclusions so that it have a few directories excluded :

%ProgramFiles%\Exchsrvr\MDBData\
%ProgramFiles%\Exchsrvr\Mtadata\
%ProgramFiles%\Exchsrvr\Server_Name.log
%ProgramFiles%\Exchsrvr\Mailroot
%ProgramFiles%\Exchsrvr\Srsdata
%SystemRoot%\System32\Inetsrv
%ProgramFiles%\Exchsrvr\IMCData


To exclude these fle and directories in AMON module, follow these steps:
• Click on the Setup button in AMON module
• Click on the "Exclusions" tab and then on the Add button
• In displayed window click on the Folder or File button (depends on what you want to exclude) and browse for required items.

https://www.wilderssecurity.com/attachment.php?attachmentid=186152&stc=1&d=1166749496


Also :
https://www.wilderssecurity.com/showpost.php?p=1262716&postcount=2

Review the manuals here:
http://www.eset.com/download/manuals.php

 

Thank you very much for your answer, it did give me some info to get started!

Time to install, test and learn...

 

You are welcome !

Just one more note about updating NOD32 v2 from ERA v2
https://www.wilderssecurity.com/showthread.php?t=210530

 

Yes, I actually found that out while installing ERAS v2. I have set up ERAS v2, NOD32 v2.7 with XMON and a few v2 and v3 clients pointing correctly to the v2 mirror, and lo and behold! it works!

I might add for those interested: When installing ERAS on a 2008 Server, you must configure an exception in its firewall. Add a new Allow Incoming rule that allows traffic on TCP ports 2221-2224. If not, ERAS cannot communicate with the clients, neither while installing nor while updating.

 

Hello!

This is valid for all Servers/Workstations/Firewalls , not only MS Windows Server 2008 .