Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Centralized Exception Syntax - Example needed.

Created: 18 Jan 2008 • Updated: 22 May 2010 | 3 comments
This issue has been solved. See solution.
In the Centralized Exception Policy UI, when setting Security Risk by File/Folder or Tamper Protection Exceptions you can use Prefix Variables (environmental variables) to set a path to the target.  I'm having a little problem getting the syntax correct on this and I'm not finding any examples in the admin manual or in the KB.
Let's say for example I needed an exception for c:\program files\someprogram\file.exe.
Now for Prefix Variable I would choose [PROGRAM_FILES].  Now what do I put into File (include full path)?
\someprogram\file.exe  or
Don't know if the whack between the variable and the child directory is assumed or not.  Or do I need to put the path with [PROGRAM_FILES] (Symantec way) or %programfiles% (windows way)?
This is just a bit confusing without documented examples to work from and would probably be a good candidate for a KB article.

Message Edited by Scott Klassen on 01-18-2008 11:02 AM

Comments 3 CommentsJump to latest comment

SKlassen's picture
Update, I did find one example is the kb, at .  The only problem is that it doesn't match what's actually in the program.  In the article it show the syntax for the Prefix Variable as %[SYSTEM]%, but in the SEPM console the syntax is [SYSTEM].  Uuugghh.
Paul Murgatroyd's picture
if you use our prefixes, you will actually get %[PROGRAM_FILES]% added to the GUI, which is fine.
As far as adding the next "\" goes - it will work either way.

Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: