In SEP SBE (using the cloud console), I need to enter an exception for a ClickToRun application which puts the executable in the user's profile (ie: c:\documents and settings\username\local settings\apps\2.0\5wpbzxtp.p65\xp83eny0.e29\barc..tion_b2411e7e0651364c_0001.0001_59d80887428d51d4\application.exe ). One of the features of a ClickToRun app is it will automatically update itself if the source location (usually a URL or UNC Path) is newer, which will then change the obfuscated portion of the path on the device running it. Currently the only way to handle this exception is to make a file entry of the full path for each user's profile. And if the app is updated, all the exceptions would need to be updated as well since the path would change.
I'm making a feature request to add the option of allowing wildcards in the path of a file (or folder) exception. So in the above example, the file exclusion path would be c:\documents and settings\*\local settings\apps\2.0\*\*\*\application.exe. So only two entries would be needed to handle the exception (one for each user profile path). To allow for flexibility I would like to see wildcards for a single character (?), multicharacters (*) within a single folder path element (between \'s), global or spanning multicharacter (** or some other character) to include any number of path elements.
Also, having additional macro paths for the user profile paths (USERPROFILE, USERNAME, LOCALAPPDATA, APPDATA for example) would be handy, and could cut the above exception down to one entry.
Another option would be similar to the existing file extension exclusion option, but would exclude a specific file (application.exe) regardless of the path. If the above wildcard option request was implemented so the wildcard could span any number of folders, **\application.exe could accomplish the same thing. Thanks!
Galen Van Maanen