NOD32 and Windows 2003 Server

Greetings, I', currently evaluating nod32 as a solution for a windows 2003 server we use for web hosting with the plesk 7.5.6 control panel.

I just installed nod32 trial to get rid of some viruses and backdoors i had on the server, we used the nod32 on demand scanner for this, and it worked very well.

After doing this i'm thinking about leaving nod32 enabled on the server as a real time file system scanner, nod32 looks like a desktop aplication though.

I was wondering, does nod32 run as a windows 2003 service (without an user logged into my machine), does its engine update by itself in the same way (without an user logged in)? is there any documentation available on windows 2003 server intallations?

Thanks in Advance

Andres

 

Great news to hear . Welcome to Wilders !

Yes , NOD32 updates itselft automatically. No , there are no special documentation for Win 2003 server because there is nothing special for it about servers . It is recommended , however , to keep IMON off when NOD32 is installed on servers

And about this question , please wait for an answer from a moderator
I was wondering, does nod32 run as a windows 2003 service (without an user logged into my machine)

 

yes (NOD32 Kernel Service)

yes

 

No , because IMON works on early level - winsock , there can be system failure becuase of the speed and high work of that level . See this :

https://www.wilderssecurity.com/showpost.php?p=772546&postcount=3

 

Or to put it another way, most servers have a high volume of network traffic. IMON inserts itself at the Winsock level of the Windows networking stack. For the amount of network traffic that goes through a typical desktop computer, this is OK.

However, for a server, which often has heavy network traffic, this can pose a problem, because the sheer volume of network traffic may be too large for IMON to handle. This may not necessarily cause total system failure, but it may cause network applications to stop functioning properly. A non-functioning program is certainly *not* something you would want from a server.

Now, if you have a low volume server (like my company does), you may be able to get away with running IMON without having any problems. However, the official recommendation is to leave IMON disabled (to minimize the chance of programs crashing), and let AMON do all the realtime virus scanning (at the file level).

By the way, if you are running Microsoft Exchange, Eset has a separate module (XMON) to handle that.

 

It's the same installer for 2K/2Kp/XPh/XPp/2K3

It will automatically detect, upon installation, that you're installing on a server OS..and disable IMON by itself during setup.

 

TY all for the quick responses, i got it up and running, I will let you guys know if i encounter any problems:

for the record, I got this reply via email for mthe nod32 people via email: