I am trying to add an exclusion for a folder on our network attached storage.  Unfortunately the DNS name is nas1 so the path is \\nas1\folder\folder2.

However when manually adding a centralized exclusion the 'n' gets upper cased so the path reads \\Nas1\folder1\folder2 and thus (I think!) the exclusion is not honoured.

I have tried adding the exclusion via the logs but the n is still upper cased.  Note that the logs report a lower case n

Removing the leading slash results in the n staying lower case but effectively the path is now incorrect so the exclusion does not work.

I have tried to use other letters i.e. the letter 'a' for example resulting in the path \\aas1\folder1\folder2 these alternative letters are NOT upper cased it only affects the letter 'n'.

I have tried a wildcard (*) in place of the 'n' which does not work.

Server 11.0.5002.333
Client 11.0.5002.333

I upgraded specifically to get around this issue...from the RU5 release notes.

Centralized Exceptions does not function in exceptional situations
Fix ID: 1179354
Symptom: When creating a centralized exception for a directory that starts with a lower case n in the directory name, the exclusion does not work properly. This behavior also effects file exclusions and Tamper Protection exclusions. Garbage characters replace the "\n" and placing an infected file in the folder causes an alert to trigger even though that folder is supposed to be excluded.
Solution: Exceptions handle "\n" so that garbage characters are not created and exceptions work as expected.

Can anyone point me in the right direction?

Thanks,

Jim