Command Prompt .LNK files do not behave properly when stored within AFS

These issues are the result of the Console Window Host process (conhost.exe) running outside the logon session's authentication group. While conhost.exe impersonates the Windows user, it does not impersonate a logon session process. As a result, it has no tokens and cannot access the LNK file.

It is not possible to execute an application out of AFS under the following conditions:

Workaround: use SUBST instead of NET USE to assign drive letters to UNC paths.

The Windows File System Volume Query Quota Interface is not implemented. As a result, AFS quota information is not available to application processes or end users via Windows dialogs.

The Windows Volume Shadow Copy Service is not implemented. As a result, AFS backup volumes are not accessible via the Explorer Shell.

There is no support for storing DOS attributes such as Hidden, System, or Archive.

There is no support for Alternate Data Streams as required by Windows User Account Control to store Zone Identity data.

There is no support for Extended Attributes.

There is no support for Access Based Enumeration.

There is no support for Windows Management Instrumentation

There is no support for Distributed Link Tracking and Object Identifiers

There is no support for storing Windows Access Control Lists. Only the AFS ACLs are enforced.