Setting Exceptions, wildcards and system variables.

Discussion in 'ESET NOD32 Antivirus' started by enotsIT, Apr 16, 2012.

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

    enotsIT Registered Member

    Joined:
    Dec 30, 2010
    Posts:
    15
    Location:
    Eugene, OR USA
    I need to add some exceptions for ESET and am wondering what variables and wildcards I can use. The documentation talks about * and ?? briefly, but doesn't mention if it can use system variables.

    Actual Path I need to exclude
    C:\Users\USERNAME\AppData\Local\Temp\Acowin\

    Could I use:
    C:\Users\%username%\AppData\Local\Temp\Acowin\*

    If not would this work:
    C:\Users\*\AppData\Local\Temp\Acowin\*
    Or will ESET see the first wildcard and exempt everything after C:\Users\ ?

    Any help would be appreciated.
     
  2. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
  3. xxJackxx

    xxJackxx Registered Member

    Joined:
    Oct 23, 2008
    Posts:
    3,586
    Location:
    USA
    For your example I would use:
    %UserProfile%\AppData\Local\Temp\Acowin\*

    -Nevermind the % doesn't work...
     
  4. enotsIT

    enotsIT Registered Member

    Joined:
    Dec 30, 2010
    Posts:
    15
    Location:
    Eugene, OR USA
    So it looks like I would have to add exceptions for each user since I can't use system variables and based on what is mentioned here http://www.wilderssecurity.com/showthread.php?t=300086 it sounds like the C:\Users\*\AppData\Local\Temp\Acowin\* Would indeed exempt everything after C:\Users\.

    Wow, this is going to get complicated as I will have to create exceptions every time a new employee is hired. Any chance this has been changed in v5? Or is there a better way to handle this that I am missing?
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,330
    You can use system variables but not user ones because they cannot be resolved under the local system account.
     
  6. enotsIT

    enotsIT Registered Member

    Joined:
    Dec 30, 2010
    Posts:
    15
    Location:
    Eugene, OR USA
    I asked ESET's tech support the same question and here is part of their reply.

    Thank you for contacting ESET Customer Care.
    Unfortunately environment variables are not supported in ESET 4.x or below products. ESET version 5 products will be supporting Environment variables. Currently the only variables ESET recognises are "*" and "?" without the "".


    So it looks like v5 will be able to handle this. For now I manually added the exceptions for each staff member (20), but once v5 is available this should be easier to configure properly.

    Thanks to everyone for your help.
     
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,330
    I reckon v4.2 supports exclusions in the same way as v5. Definitely user variables cannot be resolved due to the way Windows is designed.
     
  8. oliverm

    oliverm Registered Member

    Joined:
    Nov 13, 2007
    Posts:
    16
    I'm not sure that v5 supported system variables either. I can't get it to work at all.
     
Thread Status:
Not open for further replies.