How to Enable Server-Side Content Fetching in HDX MediaStream for Flash

How to Enable Server-Side Content Fetching in HDX MediaStream for Flash

book

Article ID: CTX126529

calendar_today

Updated On:

Description

This article describes how to deploy, configure, and confirm functionality of Server-Side Content Fetching (SSCF) in HDX MediaStream for Flash.

Requirements

Server Side

Adobe Flash Player 10 or later
Internet Explorer 7 or later
HDX Capable Virtual Desktop Agent 4 or later, or XenApp Server (HDX MediaStream for Flash 1.1.0+)

Client Side 

Adobe Flash Player 10 or later
Internet Explorer 7 or later
Citrix Receiver 3.x or later

Background

HDX MediaStream for Flash provides the ability to fetch and render Flash content on the endpoint, thereby reducing server load, and optimizing the end-user experience. There are some cases when the default client-side content fetching is not desirable, or functional. For example, the content might be referenced by the Flash Player using a network address that is internal to an organization (for example: http://mycorporation/video.swf).
Such a URL can only be resolved on the server, and server-side content fetching must be used. Perhaps the most common use case requiring HDX MediaStream for Flash server-side content fetching is an organization that restricts the network connectivity of their ICA client devices so that they can communicate only with their XenApp or XenDesktop servers. Such an organization would configure HDX MediaStream for Flash to use server-side content fetching for all web sites.
Server-side content fetching is the exception and can be configured on a per-URL basis using a server-side configuration setting. In addition, you must enable server-side content fetching on the client.


Instructions

Server-Side Configuration

On a compatible XenApp Server, or XenDesktop Virtual Desktop Agent, add sites to the server-side content fetching list. Consider the following when configuring the server-side content fetching list setting:

  • Add the URL of the Flash application; not the top-level .html page that instantiates the Flash Player to the list.

  • Use an asterisk (*) character at the beginning or end of the URL as a wildcard to expand your list.

  • Use a trailing wildcard to allow all child URLs (for example http://www.sitetoallow.com/*).

  • The prefixes http:// or https:// is used when present, but they are not required.

  1. In AppCenter or Desktop Studio select the Policies node > User tab > select the existing filter > Edit

  2. Select the Settings tab > Flash Redirection node.

  3. Click Add for Flash server-side content fetching URL list, click New and specify the URL(s).

  4. Click OK twice.

  5. Run gpupdate/force or restart for the changes to take effect.

Client-Side Configuration

On a compatible client, enable server-side content fetching using the HDX ADM template included with Citrix Receiver installation. 
Complete the following steps to enable SSCF on the client:

  1. On the Group Policy Object Editor, expand either the Computer Configuration or the User Configuration node.

  2. Expand the Administrative Templates and Classic Administrative Templates (ADM) nodes and select HDX MediaStream for Flash - Client.

  3. From the Setting list, select Enable server-side content fetching and edit the policy settings.

  4. Select Enabled.

  5. For the policy to take effect:

  • Computer Configuration: Changes are reflected as computers in the organizational unit restart.

  • User Configuration: Users in the organizational unit must log off and then log on to the network.

Issue/Introduction

This article describes how to deploy, configure, and confirm functionality of Server-Side Content Fetching (SSCF) in HDX MediaStream for Flash.

Additional Information

To confirm that SSCF is being used, first ensure that the content is being rendered by verifying that PseudoContainer2.exe is running on the client. If the client is rendering the content, verify that the client is not fetching the content directly by watching the HTTP traffic (using Fiddler or similar trace tool).

If SSCF is working, there should not be any direct HTTP traffic from the client, only from the server or Virtual Desktop Agent.

If you observe traffic from the client to the content, and PseudoContainer2.exe is running, check your server-side content fetching list syntax, and test with a single * entry to enable SSCF for all content.

If PseudoContainer2.exe is not running on the client, use the HDX Monitor to confirm that HDX Flash prerequisites have been met.