Endpoint Protection

 View Only
  • 1.  Adding environment variable to exception list

    Posted Sep 30, 2016 12:44 PM

    Hi All,

    We have Endpoint Protection (AntiVirus) version is 12.1.6(12.1 RU6 MP5) build 70004 (12.1.7004.6500) and have an application that runs on windows 7 clients.

    I am trying to figure out a way to add environment variables to the exception list to prevent scanning a folder.

    Here is the variable:

    %appdata%\myapp\

     

    This is what it prints:

    C:\Users\JohnD>echo %appdata%\myapp\

    C:\Users\JohnD\AppData\Roaming\myapp\

     

    Since we don’t know which user account is login to Windows we have to use environment variable.

     

    Not sure SEP if support this.

     

    Any thoughts or workaounds?

     

    Thanks!

     

     

     



  • 2.  RE: Adding environment variable to exception list

    Posted Sep 30, 2016 12:53 PM

    SEP does not support user variables so this won't work. You'd need to add all the paths, a pain I know.



  • 3.  RE: Adding environment variable to exception list

    Posted Sep 30, 2016 01:27 PM

    Thanks Brian!



  • 4.  RE: Adding environment variable to exception list

    Posted Sep 30, 2016 01:31 PM

    You're welcome



  • 5.  RE: Adding environment variable to exception list

    Trusted Advisor
    Posted Oct 02, 2016 10:47 AM

    Hello,

    You're best bet is to enter the full path with no prefix.

    There were few idea's as below provided - 

    https://www.symantec.com/connect/idea/sepm-more-variables-avas-exclusions

    https://www.symantec.com/connect/idea/add-userprofile-variable-equivalent-centralized-exceptions-prefixes

    As Paul Murgatroyd, highlighted - "%USERPROFILE% is actually harder to implement than you would think, as it means every time the user logs on we would have to dynamically enumerate the user and create the exception.  Then, what happens when there is no user logged on, but scans and AV are still running?  This gets even more interesting when you understand that our drivers are kernel based, so we need user mode code to help us determine what %USERPROFILE% is.

    We believe the better route forward here is to use wildcards in pathnames.  So, for example, C:\Users\*\Temp would match any user profile on the server or client, whether they are logged in our out. "

    Regards,