Endpoint Protection

i have created a list of SEP centralised exceptions, and have tested a few of them using eicar.com.
When I used syntax such as \\server\d$\folder  the exception did appear in the registry as a centralised exception, but the test virus in that folder  was picked up, when it should have been excluded from the scanning.
Are unc paths not valid? Do I have to either use d:\folder (and have that apply to all servers) or use d:\folder on the server itself?

Have you tried to map the folder to a drive then exclude it via centralized exclusions, check whether it works. Try it the server ip address

Wildcard variables such as * and ? are not supported.

For File and Folder-based exclusions, the Full Path to the file must be specified, unless a "Prefix Variable" is selected. If a "Prefix Variable" is selected, the path specified should be relative to the selected "Prefix Variable" 

Yes that does appear to work. However as there are quite a few servers and not many drive letters it might not be feasible.
Is it definitely the case that unc paths are not supported?
If so, are there any plans to remedy this in the future?
It would have been good if the documentation had mentioned this, as I have now wasted a lot of time typing in exceptions that won't work!

Which is the SEP version you are using?

If you are using an old version upgrade to RU6a and try.There is some fixes are present in recent versions related to centralized exceptions...

The version is 11.0.5002.333 which I believe is RU5

Are the fixes in the versions after this one? 

No..

Disable Network Drive Scanning:
Click the Policies Tab.
Click Antivirus and Antispyware.
Click the policy you would like to modify and then click Edit the Policy.
Click File System Auto-Protect.
Under Network Settings, uncheck Network.
Click OK.
Assign the policy by clicking Assign the Policy, then check each group to which the policy should apply.
Click Assign, then click Yes.

Network is not currently checked.

I have worked around this issue by putting exceptions for S:\software\etc......\dfsprivate and P:\software\etc...\dfsprivate instead of the server name, and as these folders are on either P: or S: on the various servers this will work ok.
Thanks for your suggestions.

Is there possibility to configure folder exclusion in this way that will be valid for all connected drives on computer? For example I have some SAP servers with SAN attached disks. Drive letters are different from server to server. I have to exclude SAP\data folder on the root of drive. Now I have exclusion rule c:\SAP\data, d:\sap\data, e:\sap\data,…..In prefix options there is not options for root. Is there any option to write exclusion in way root\sap\data or something like that, that exclusion will be valid for same folder structure regardless on which drive letter exists?

I hear your pain Rajha, I too have a number of servers with common folders on different drives and sometimes different parent paths. Apparently the Linux version has an executable that will import an exclusion list - Why isn't this available in the Windows Version?

Has anyone heard if wildcards will be implemented in the Centralized Exceptions? Or if there is any easy way to export the list for documentation/review purposes? It would be useful if the 'Prefix Variable' were configureable as well.

One saving grace is that at least the list doesn't have to be entered on the server needing the exclusion.....