To access local applications, you must enable the Local App Access feature, which is not enabled by default in the hosting and client environment.
Enable this feature by following the procedures in To enable Local App Access using policy settings and To enable Local App in Receiver.
After completing these procedures, the Local App Access feature is enabled and all the client's shortcuts appear in the desktop on the VDA.
Use this procedure if you want to provide access to only Published Applications.
For example, by default, Microsoft Word associates the Word-related extensions (such as .doc, .docx, .rtf). Selecting Get the file types from user’s computer at run time specifies FTA as all extensions. However, if you want to limit the file types associated with the application (For example, only .doc), then select Set the files types explicitly to make those specifications
Follow the procedures in Enable Local App Access on client machines running Receiver to complete the Local App Access feature configuration.
When set to Disabled, both administrator-published apps and Local App Access shortcuts do not work for the VDA.
This policy applies to the entire machine as well as for the URL redirection policy. For more information, see Local App Access policy settings.
Configure the URL Redirection feature
You can optionally use policy settings instead of the Windows Registry to set up the URL Redirection feature by configuring the multi strings lists URL White List and URL Black List policies in Studio. For detailed URL redirection configuration procedures, see Use URL Redirection to launch local applications.
For more information about this using policies, see Local App Access policy settings.
You can configure the expected behavior of local applications when a user logs off or disconnects from their virtual desktop.