Centralised Exceptions, Environment Variables and Customisable "Prefix Variables"
When setting a centralised exception in SEP it is possible to use pre-defined "Prefix Variables" instead of the Windows environment variables. I’m gathering this is because the Windows environment variables don’t store very well in the database considering a ‘%’ character is a wildcard in SQL. This aside, in my experience (and by the looks of a large number of forum topics) entering a Windows environment variable into a centralised exception does not work.
My request here has three parts:
1. Make "user" based environment variables work !!
No matter how much I read on the forum and thus how much your “trusted advisors” and “Symantec employees” say otherwise, “user” based environment variables such as %user%, %userprofile%, %temp% and alike do not work when setting a centralised exception.
2. Add the ability to create personalised/customised "Prefix Variables"
Many companies have environment variables included in their build which point to customised locations on their systems. If you allow the administrators the ability to define their own "Prefix Variables" within the SEP console, you will make their jobs easier.
3. If you don't want to allow us to create "Prefix Variables" ourselves, make Windows environment variables work properly ... because right now ( in SEP 11 RU6a MP2 ) they don't !!
Even if they have to be typed out in a very specific way to make them work, please tell us how to do this. I can’t explain to you how frustrating it is trying to explain to users, vendors and the system, database and application admins that SEP just can’t translate an environment variable.