Wilders Security Forums  

Go Back   Wilders Security Forums > Official ESET Support Forum > ESET Home Users Products Forum > ESET NOD32 Antivirus
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
 
Thread Tools Search this Thread
  #1  
Old November 25th, 2010, 07:08 AM
hungabunga hungabunga is offline
Infrequent Poster
 
Join Date: Nov 2010
Posts: 1
Default Remote Admin change Real Time scan settings

We have just installed Nod anti-virus with remote admin and we have a slight problem which we know is linked to the real time scanning feature. When accessing Sage Accounts with data on a network location the real time scanner is scanning the network and causes Sage to run very slow. If we disable real time scanning on the network it works fine.
What I need to know is how can I firstly disable real time network scanning via the remote admin console for all machines?
Is there a better method where I can retain real time network scanning but exclude the network drive/folders so it does not affect Sage and other database apps, this also needs to be done via the remote admin console.


Thanks in advance

Sohail
  #2  
Old November 29th, 2010, 05:04 PM
ramirez1 ramirez1 is offline
Infrequent Poster
 
Join Date: Sep 2010
Posts: 30
Default Re: Remote Admin change Real Time scan settings

1. From the remote admin console double click on one of the clients.
2. Click the Configuration tab then click on New Task then click Edit
3. Under Eset Smart Security, ESET NOD32 Antivirus click the + next to File-system filter
4. Click on Scan network disk and change the value to NO
5. Save your changes and deploy the new configuration


You can also see the the recommended settings for ESET NOD32 Antivirus installed on a server

http://kb.eset.com/esetkb/index?page...=1291068178822
  #3  
Old November 30th, 2010, 02:27 AM
jimwillsher jimwillsher is offline
Frequent Poster
 
Join Date: Mar 2009
Posts: 668
Default Re: Remote Admin change Real Time scan settings

NOD absolutely cripples Sage to an unusable state. These are the Sage-specific exclusions we have (Sage is located on the T: drive, \\SLFSRV\Accounts):

<NODE NAME="FullPath" TYPE="STRING" VALUE="T:\*.*" />
<NODE NAME="FullPath" TYPE="STRING" VALUE="C:\Documents and Settings\All Users\Application Data\*.*" />
<NODE NAME="FullPath" TYPE="STRING" VALUE="C:\Program Files\Common Files\Sage Line50\*.*" />
<NODE NAME="FullPath" TYPE="STRING" VALUE="C:\Program Files\Common Files\Sage SBD\*.*" />
<NODE NAME="FullPath" TYPE="STRING" VALUE="C:\Program Files\Common Files\Sage Shared\*.*" />
<NODE NAME="FullPath" TYPE="STRING" VALUE="C:\Program Files\Sage\*.*" />
<NODE NAME="FullPath" TYPE="STRING" VALUE="\\SLFSRV\Accounts\ACCDATA\*.*" />

These are in our config file that gets pushed to the clients.



Jim
 

Wilders Security Forums > Official ESET Support Forum > ESET Home Users Products Forum > ESET NOD32 Antivirus « Previous Thread | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -4. The time now is 12:03 AM.


Powered by vBulletin® Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums