ESET NOD32 Business Editon 4.2.76 on Windows Terminial Server 2008 RD2

I've installed ESET NOD32 Business Editon 4.2.76 on four Windows Terminial Server 2008 RD2 that are being used by a total 100 users. (25 per TS).

The users are complaining that the TS are slower since i'v installed NOD32. Indeed, the ESET kernel is using a lot of CPU resource.

Is there special configuration available for Terminal Server ?? Or any tips??

Btw this the specifications of the TS servers:

Intel Xeon E5620 2,5 GHz
6GB RAM
Windows Server 2008 R2 Standard Editon

 

Does disabling real-time protection or http checking in the advanced setup make a difference?

 

Didn't try that yet. But i'm trying to keep the security as high as possible, so disableling the real-time proctection don't look safe to me.

 

It is necessary to narrow it down to a particular module, hence I was asking. Perhaps you could try it when users are not logged to TS to minimize the risk they would run something malicious.

 

One thing I do in TS environments is delete the registry startup key for egui.exe (under HKEY Current User), otherwise you have a separate egui process running for every user who logs on.

 

Deleting the registry startup key sounds good, so i'm gonnan try that.

1. I'm running a 4 server with 25 uers each, there no way that i'm gonna shutdown the real-time protection.

2. Why buy a virus a virusscanner if i'm realtime protection is'nt necessary??

 

The solution was not to permanently disable the security. It is only a way to figure out what part of the AV is slowing things down. Try to disable it for a few minutes, and see if it fixes the problem, and then report back here.

Also deleting that registry key might help. Or you can just add /terminal(look in the manual)

 

Ok true there!

If real-time protection is the source op problem, what would be the next step??

 

Have you followed the recommended settings for servers?

http://kb.eset.com/esetkb/index?pag...earch&viewlocale=en_US&searchid=1337609725981

 

If disabling real-time protection helps, generate a Procmon log and supply it to Customer care for perusal. You can also upload it somewhere and PM me the download link.