ESET VERSION 4 SAGE LINE 50 Exclusions

Discussion in 'ESET NOD32 Antivirus' started by wmaxted, Dec 8, 2009.

Thread Status:
Not open for further replies.
  1. wmaxted

    wmaxted Registered Member

    Joined:
    Dec 8, 2009
    Posts:
    1
    Hi One and All

    We currently have several clients that experience poor network performance when using sage line 50 in conjunction with Nod32 . Ive done the usual and removed network drives ive also excluded the local path to the sage folder.

    Does anyone have any other suggestions?
     
  2. jimwillsher

    jimwillsher Registered Member

    Joined:
    Mar 4, 2009
    Posts:
    668
    Which version of Sage?

    Sadly ESET doesn't allow exclusions by process name, which is what we used with our previous AV solution and it was brilliant and speeding up Sage. So instead we have to put loads of paths as exclusions.

    We're using these exclusions:


    C:\Documents and Settings\All Users\Application Data\*.*"
    C:\Program Files\Common Files\Sage Line50\*.*"
    C:\Program Files\Common Files\Sage SBD\*.*"
    C:\Program Files\Common Files\Sage Shared\*.*"
    C:\Program Files\Sage\*.*"
    \\OurServerShare\Accounts\ACCDATA\*.*"

    and performance is fine.

    Jim
     
Thread Status:
Not open for further replies.