Product Documentation

Configure Receiver for HTML5 1.3

Nov 01, 2017

A StoreFront store with a Receiver for Web site is required to make desktops and applications provided by XenDesktop and XenApp available for Receiver for HTML5 users. If you have not already done so, deploy StoreFront and create a store aggregating the resources you want to make available to your users. A Receiver for Web site is created automatically for the new store. For more information about creating and configuring stores and Receiver for Web sites, see the StoreFront documentation.

Ensure that you configure remote access through Access Gateway when you create the store. Users must connect to Receiver for Web sites through Access Gateway to access desktops provided by XenDesktop, web and SaaS applications provided by AppController, and applications provided by most supported versions of XenApp. For more information, see System requirements for Receiver for HTML5 1.3.
Important: If you are using SecureICA to encrypt communications between users' devices and your XenDesktop or XenApp servers, note that Receiver for HTML5 supports Basic encryption only. For more information about configuring SecureICA for XenDesktop and XenApp, see To secure desktop groups and To set a policy for ICA encryption, respectively.

To configure XenApp 6.5 Feature Pack 1 for local user access

If you plan to enable local access through Receiver for HTML5 to applications provided by XenApp 6.5 Feature Pack 1 without routing connections through Access Gateway, you must configure the ICA WebSockets Connections policy on the XenApp server. For more information about configuring XenApp policies, see Manage Citrix policies.
  1. On your XenApp 6.5 server, install the latest XenApp 6.5 Hotfix Rollup Pack and Hotfix XA650R01W2K8R2X64051 (available at http://support.citrix.com/article/CTX138537). Then, restart the server.
  2. Install the Group Policy Updates included with XenApp 6.5 Feature Pack 1 and restart the server.
  3. Using either the Citrix AppCenter or the Microsoft Group Policy Management Editor, set the ICA WebSockets Connections policy on the XenApp server to Allowed.
  4. To restrict access to the XenApp server, specify a comma-separated list of trusted Receiver for Web URLs for the WebSockets Trusted Origin Server List setting.

    By default, the policy is set to trust all Receiver for Web URLs.

  5. From a command prompt, type the following command to apply the policy.
    gpupdate /force
  6. Restart the Citrix Independent Management Architecture (IMA) service, wait for ten seconds, and then restart the Citrix XTE Server service.

To configure Receiver for HTML5 to use a different port

By default, Receiver for HTML5 uses port 8008 for direct connections to XenDesktop. You may want to use a different port, however, in the case of firewall or other restrictions in the network infrastructure. To configure Receiver for HTML5 to use a different port, you edit the site configuration file.
Important: In multiple server deployments, use only one server at a time to make changes to the configuration of the server group. Ensure that the Citrix StoreFront management console is not running on any of the other servers in the deployment. When you are done with edits to the site configuration file, propagate your configuration changes to the server group in order to update the other servers in the deployment.
  1. On Desktop Delivery controller, change the websocket port number to a new port.
  2. Use a text editor to open the web.config file for the Receiver for Web site. The file is typically located at C:\inetpub\wwwroot\Citrix\storenameWeb\ directory, where storename is the name specified for the store when it was created.
  3. Locate the following element in the file: <html5 ... preferences ="" />
  4. Set the value of the preferences attribute to wsPort:8011; to allow Receiver for HTML5 to use the new port. Note that this port needs to be the same port that you configured in Step 1.
Propagate your configuration changes to the server group so that the other servers in the deployment are updated.
Note: When using port 8008, verify that the port is not blocked by firewalls and that no applications are using the port, and ensure that the port is not redirecting to other ports.