Environmental Variables.

Discussion in 'ESET NOD32 Antivirus' started by aluminex, Oct 26, 2011.

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

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    I have read some post in the past about environmental variables in exclusions and there wasn't any support.

    Today is there any support for this? And if not do we have this on the list for improvements?
     
  2. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    I see this has been approved for configuration task pushes... What about policies?
     
  3. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
  4. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    Will the following : ?:\*\NTUser.pol

    Work to exclude : %allusersprofile%\NTUser.pol
     
  5. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    bumpccc
     
  6. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    can anyone confirm that ? works for any drive letter?
     
  7. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    FYI for anyone else wanting to know... I have been doing some testing and you cannot use a wildcard for a drive letter.....

    Simply lovely - now I have to hardcode exclusions for absolute paths for different drive letters across 100+ servers

    enterprise solution? not so much
     
  8. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    *update*

    You can't mass exclude any files of a specific extension either...

    Example if I want to exclude all MDF files one would assume *.mdf would work but *.mdf adds the following entries:

    c:\*.mdf and d:\*.mdf and any other drive letters you might have.

    It doesn't exclude the files for all sub-folders - and while I understand that mass excluding certain extentions in any location probably isn't best practice, it is tempting due to the other exlusdion limitations.

    So I ask for advice. I have probably 40 or more DB servers without a standard location for the mdf / ldf / ndf files - I don't want to scan these files. I also have another 60 or more servers that I will want to exclude various files based on OS and Application.


    What would you do?
     
  9. dmaasland

    dmaasland Registered Member

    Joined:
    Nov 10, 2010
    Posts:
    468
    I'd add *.mdf to the list of extensions it shouldn't scan
     
  10. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    Do I need to add these settings to all scanners? startup scanner / file-system filter / computer scanner? any other place?
     
Thread Status:
Not open for further replies.