FRP Location based protection for network folder

[404NotFound]

In a location based policy for FRP, can a network location be described as a mapped network drive?  IF the FRP users all access a sub-folder folder named "secret" on drive X: (example X:\documents\secret where x is mapped to \\fileserver\documents.  Can the path in the location based policy be written as "X:\documents\secret" or does it have to be a UNC path?  If it is a UNC path, then how does it work if the folder is only ever accessed via the mapped drive letter?

[404NotFound · Accepted solution]

For the next poor lost soul that runs into this, if you want to encrypt a mapped network drive location with a Location based policy you must describe it with a UNC path.  This is not immediately evident in the documentation, and McAfee's on support staff do not seem to know this.   They kept insisting that the description had to be via UNC, but that the user would also have to access the folder by UNC.   Because end-users always type \\servername\sharename when they want to access a non-local resource.  Doesn't everyone?  This will also work within a Active Directory DFS structure so that \\domainname\sharename will encrypt.