Product Documentation

Provide access to local applications

Jun 11, 2013

To access local applications, you must enable the Local App Access feature, which is not enabled by default in the hosting and client environment.

Provide access to all local applications

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.

Provide access to Published Applications

Use this procedure if you want to provide access to only Published Applications.

  1. On the machine running Studio, open the Registry Editor and browse to the following path: HKLM\Software\Wow6432Node\Citrix\DesktopStudio .
  2. Add the following registry entry (of type REG_DWORD): ClientHostedAppsEnabled and add a value of 1 to enable Local App Access. (Using 0 disables Local App Access).
  3. Restart the machine, and then restart Studio to implement the changes.
  4. Publish the Local App Access applications as described in To publish local applications in Studio.
  5. Enable Local App Access in Receiver as described in To enable Local App Access in Receiver.
  6. Set the Allow Local App access policy to Enabled as described in To enable Local App Access using policy settings.

To publish local applications in Studio

  1. In Studio, select the Delivery Groups node in the left pane, then the Applications tab in the main pane. Click Create Client-hosted application in the Actions pane. The Create Client-hosted application wizard appears.
  2. On the Delivery Groups page, select the Delivery Groups to access the local application.
    Note: Local App Access is only available for desktop Delivery Groups. It is not available for application Delivery Groups.
  3. On the Location page, enter the full executable path of the application as present on the user’s local machine in the Program Executable field.
    Note: Make sure that this path is correct. Otherwise, the application is not visible to users.
  4. On the Users page, add the users who access the local application being published.
    Note: Choose either individual users or a group from your Active Directory configuration.
  5. On the Shortcut page, select whether the shortcut to the local application on the virtual desktop is visible on the Start menu, the desktop, or both.
  6. On the Content redirection page, specify the File Type Association (FTA) of the application. By default, all the file types associated with the application can be used by selecting Get the file types from user’s computer at run time or file types can be provided explicitly by choosing Set the file types explicitly and then adding specific extensions.

    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

  7. On the Name page, accept the default values.
  8. On the Summary page, review the settings and click Finish.

To enable Local App Access in Receiver

Follow the procedures in Enable Local App Access on client machines running Receiver to complete the Local App Access feature configuration.

To enable Local App Access using policy settings

Use Local App Access policy for delivery groups by setting the policy to Enabled. With this setting, the VDA lets the client decide whether administrator-published apps and Local App Access shortcuts are enabled in the session.

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.

To configure Local App Access behavior on Logoff and Disconnect

You can configure the expected behavior of local applications when a user logs off or disconnects from their virtual desktop.

  1. On the hosted desktop, open the Registry Editor and browse to the path: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Client Hosted Apps\Policies\Session State.
  2. Add the registry entry Terminate of type REG_DWORD, and set the value as follows:
    • 1 — Local applications continue to run when a user logs off or disconnects from the virtual desktop.
    • 3 — Local applications close when a user logs off or disconnects from the virtual desktop.
    Note: If the value is set to 1, the local applications are reintegrated from the disconnected session upon reconnect to the virtual desktop if they are still available in the local environment.