Product Documentation

Configuring Content Redirection

Aug 03, 2015

The capability to redirect application and content launching from server to client or client to server is referred to as content redirection.

Content redirection allows you to control whether users access information with applications published on servers or with applications running locally on client devices.

Note: For your users to access content published with a specified universal naming convention (UNC) path and through the Web Interface, you must publish and configure an application for content redirection so it is associated with the file type of the published content.

To enable content redirection from server to client

When you enable server to client content redirection, embedded URLs are intercepted on the XenApp server and sent to the client device and the Web browser or multimedia players on the client device open these URLs. This feature frees servers from processing these types of requests by redirecting application launching for supported URLs from the server to the local client device. The browser locally installed on the client device is used to navigate to the URL. Users cannot disable this feature. Accessing published content with local client desktops does not use XenApp resources or licenses because local viewer applications do not use XenApp sessions to display the published content.

For example, users may frequently access Web and multimedia URLs they encounter when running an email program published on a server. If you do not enable content redirection from server to client, users open these URLs with Web browsers or multimedia players present on servers running XenApp.

Note: If the client device fails to connect to a URL, the URL is redirected back to the server.

Complete the following configurations:

  1. Locate the Citrix policy setting for User > ICA > File Redirection. Add and enable Host to client redirection to allow file type associations for URLs and some media content to be opened on the user device (disabled by default). When disabled, content opens on the server.
  2. From the XenApp console, publish the content file and select the users or groups that can access it.
The following URL types are opened locally through user devices for Windows and Linux when this type of content redirection is enabled:
  • HTTP (Hypertext Transfer Protocol)
  • HTTPS (Secure Hypertext Transfer Protocol)
  • RTSP (Real Player and QuickTime)
  • RTSPU (Real Player and QuickTime)
  • PNM (Legacy Real Player)
  • MMS (Microsoft Media Format)

If content redirection from server to client is not working for some of the HTTPS links, verify that the user device has an appropriate certificate installed. If the appropriate certificate is not installed, the HTTP ping from the client device to the URL fails and the URL is redirected back to the server. For legacy plug-ins, content redirection from server to client requires Internet Explorer Version 5.5 with Service Pack 2 on systems running Windows 98 or higher.  For more information on server to client redirection failure see,

To configure content redirection from client to server

Configure content redirection from client to server by associating published applications with file types and then assigning them to the users you want to be affected. When you configure client to server content redirection, users running the online plug-in open all files of the associated type with applications published on the server. Content redirection from client to server is available only for users connecting with the online plug-in.

For example, if you have users who run applications such as email programs locally, use the content redirection capability with XenApp to redirect application launching from the user device to the server. When users double-click attachments encountered in an email application running locally, the attachment opens in an application that is published on the server, associated with the corresponding file type, and assigned to the user.

Complete the following configurations:

  1. On your XenApp Services site, enable content redirection for users to connect to published applications with Citrix Receiver (formerly the Online Plug-in). If you do not already have a XenApp Services site, you can create one in the XenApp console or Web Interface console (depending on the version of XenApp you have installed). The option is located under PNAgent settings > Server Farms > Manage Server Farms > Advanced.
  2. In the Delivery Services Console, as you publish the application, associate it with file types and select the users or groups that can connect to it. When users launch the application, the file type association is changed to reference the published application in the Windows registry on the user device.

    For example, if you publish a Microsoft Word document, make sure to also publish Microsoft Word on a XenApp server so that the .doc file can open in Word.

    Note: When you associate a file type with a published application, several file extensions can be affected. For example, when you associate the Word document file type, file extensions in addition to the .doc extension are associated with the published application.
  3. Verify that the Client drive redirection User policy setting is enabled, either for the entire farm, for specific servers, or for specific users or groups.

When you configure content redirection from client to server, context menu commands available from within Windows Explorer function differently than on user devices that do not use this feature. For example, if you right-click a file in Windows Explorer on a user device with content redirection from client to server enabled for the file type, the Open command opens the file with the remote application on XenApp. For a streamed application, the file could be opened either on the user device or on the XenApp server, depending on the delivery configuration.

Most commands on the Windows Explorer context menu are unaffected because they are not configured under keys modified by XenApp. Context menu items are generally defined by each application when installed.