Centralized Exceptions - By Hash or Filename
My company learned the hard way that "home grown" applications can trigger false positives in SEP Enterprise Ed. Normally, this would be easily mitigated by adding a Centralized Exception in the SEP Management Console.
However, in Win2k3/Win2k8 environments that utilize roaming profiles, the path “C:\Documents and Settings\random user\Application Data\Microsoft\Installer\falsepositive.exe" is going to change for each user.
Since the SEP Management Console cannot utilize wildcard charters, I would like to suggest Symantec allows the use of a MD5/Sha/etc Hash based on whatever file, regardless of the location the Admin wishes to white-list to prevent major issues in his or her environment.