Exclusions of Folders where the location is not known?

Discussion in 'ESET NOD32 Antivirus' started by sammyc53, Mar 17, 2008.

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

    sammyc53 Registered Member

    Joined:
    Jan 31, 2008
    Posts:
    39
    I know that I can exclude files and folders if I KNOW where the complete absolute path is, but what if I don't know that information because it will:

    1. Be in a windows directory in which the name is unknown? (eg, Windows, WINNT, Windows1, etc)
    2. Exists in a user's profile, eg c:\docs and settings\Sam\Folder1, but of course that folder will be different for each user...
    3. You do not know which drive the file or folder will be on.

    Exclusions are a very important part of AV file scanners especially on servers, I need to make sure I get these properly configured before so.

    Thanks,

    Sam

    Nod32 3.0 Business Edition.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Try using wildcards, such as "C:\Documents and Settings\*\My Documents\"
     
  3. Manu7204

    Manu7204 Registered Member

    Joined:
    Jan 15, 2008
    Posts:
    46
    i wonder if NOD32 can use system variables in exclusions:
    %windir% - windows instalation folder - default is c:\windows for windows xp / 2003 / vista and c:\winnt for windows nt and windows 2000
    %userprofile% - user profile folder, usually c:\documents and settings\username
     
  4. sammyc53

    sammyc53 Registered Member

    Joined:
    Jan 31, 2008
    Posts:
    39
    I've tried these suggestions, but they don't populate in the client config panel, so I figured they did not get pushed to the client correctly due to syntax.

    I have also tested locations that I thought I might have excluded with the EICAR test file, and nope, it didn't work.
     
  5. guest

    guest Guest

    Actually pushing exclusions doesn't work. It's reported to be fixed in the lastest version of the RAS/RAC but I have not tested it yet. That may have been your problem.
     
  6. sammyc53

    sammyc53 Registered Member

    Joined:
    Jan 31, 2008
    Posts:
    39
    Well, I have not noticed that. It seems to work for me, with the exceptions of variables, etc... things that Eset does not seem to like.
     
  7. sammyc53

    sammyc53 Registered Member

    Joined:
    Jan 31, 2008
    Posts:
    39
  8. Eryan

    Eryan Eset Staff Account

    Joined:
    Jan 17, 2008
    Posts:
    181
    Hi sammyc53, following the exclusion example in that KB article definitely works--I want to make sure you're not excluding from the real-time scanner and then running an On-demand scan.

    To exclude certain file types from the On-demand scanner, make sure you're referencing this article:

    http://www.eset.com/support/kb.php?option=com_kb&Itemid=29&page=articles&articleid=139

    (This link is also at the bottom of the real-time scanner article you referenced)

    Let us know if something is still not working.
     
  9. sammyc53

    sammyc53 Registered Member

    Joined:
    Jan 31, 2008
    Posts:
    39
    Bingo! I forgot to exclude it from the 'Context menu' scan! It's a little confusing that there are 6 places or so that I have to define extensions exclusions...

    Thanks!
     
  10. sammyc53

    sammyc53 Registered Member

    Joined:
    Jan 31, 2008
    Posts:
    39
    PS: It would be nice is something like this worked;

    ?:\Pagefile.sys


    or *\*\mdbdata\*.* (If you always want to exclude mdbdata, no matter where it is on the disk. Currently, it seems you have to know the path...


    C:\Documents and Settings\*\My Documents\ Does work. Thanks goodness.
     
  11. agblugano

    agblugano Registered Member

    Joined:
    Mar 27, 2008
    Posts:
    2
    Hi,

    actually this is exactly what i was told by my support reference in ESET regarding the exclusion list in version 3:

    ?:\whatever*\*.* should always work as well as *\whatever\*

    but it seems that this is not the case, because i've tested exclusions thoroughly and all paths specified as above where scanned nonetheless... i'm talking about real time scan of course.

    Could someone please shed some light on wildcards support in EAV BE version 3 ?? Is the drive letter wildcard supported?? is the wildcard as prefix supported?

    I really need these capabilities in the exclusion list to work for a truckload of reasons... they've been there in competitors's software for years now...


    Albe
     
Thread Status:
Not open for further replies.