To enable users to access resources hosted on XenDesktop and XenApp in their browsers, you must create a StoreFront store and enable Citrix Receiver for HTML5. You must also enable WebSocket connections on NetScaler Gateway, XenApp, and XenDesktop, as required. Additionally, you can enhance the user experience by installing optional components on the machines providing the desktops and applications.
Note: Citrix recommends you to back up the configuration.js file before making any changes to it.
Note: Administrator level credentials are required to edit the configuration.js file.
By default, selectiveH264 is set to true.
The configuration.js file is located under C:\program Files\Citrix\Receiver Storefront\HTML5Client. Edit this file and change selectiveH264 to false as shown below.
Citrix Receiver for HTML5 uses the WebSocket protocol to access virtual desktops and hosted applications. By default, WebSocket connections are prohibited on XenDesktop and XenApp. If you plan to enable users to access desktops and applications from the local network without connecting through NetScaler Gateway, allow WebSocket connections on XenApp and XenDesktop.
WebSocket connections are also disabled by default on NetScaler Gateway. For remote users accessing their desktops and applications through NetScaler Gateway, you must create an HTTP profile with WebSocket connections enabled and either bind this to the NetScaler Gateway virtual server or apply the profile globally. For more information about creating HTTP profiles, see HTTP Configurations.
Caution: Editing the registry incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
If you plan to deploy provisioned (non-persistent) machines using Provisioning Services, create the machine catalog and delivery group for which you want to enable Citrix Receiver for HTML5 connections. Ensure that the WebSocket policies you configured apply to your machine catalog.
Machines must be restarted to apply the WebSocket policies. For Provisioning Services-based machines configured to use persistent write cache files and machines deployed using MCS (which have separate identity disks), the policies are persisted when the machines restart. However, for Provisioning Services-based machine catalogs configured to use temporary write cache files, these policies must be applied to the vDisk or they will not be implemented successfully on target devices.
Complete the following steps to ensure that the policies are correctly applied to the vDisk.
For details, see Managing Target Devices. You must use a target device that is part of the machine catalog and delivery group or the policies will not be applied.
For details, see Manually Updating a vDisk Image.
If you do not use vDisk versioning, you can apply the policies to your base vDisk image by shutting down all the target devices that use the vDisk, placing the vDisk in Private Image mode, and then starting the target device to update the image.
Two optional components are available that enhance the experience for Citrix Receiver for HTML5 users by increasing integration with XenDesktop and XenApp.
App Switcher is configured to run automatically in the background when users establish a session.
For more information about configuring XenDesktop and XenApp policies, see Citrix policies.
You must enable Citrix Receiver for HTML5 on the Receiver for Web site for the StoreFront store that provides the desktops and applications you want to make available to Citrix Receiver for HTML5 users.
A Receiver for Web site is created automatically for new stores. For more information about creating StoreFront stores, see Create a store.
<html5 ... preferences="" ... />
With session reliability, the session remains active on the server. To indicate that connectivity is lost, the user’s display freezes until connectivity resumes on the other side of the tunnel. The user continues to access the display during the interruption and can resume interacting with the application when the network connection is restored. Session reliability reconnects users without reauthentication prompts.
Citrix Receiver for HTML5 users cannot override the server setting.
You can use session reliability with Transport Layer Security (TLS).
TLS encrypts only the data sent between the user device and NetScaler Gateway.
Using session reliability policies
The session reliability connections policy setting allows or prevents session reliability.
The session reliability time-out policy setting has a default value of 180 seconds, or three minutes. Though you can extend the amount of time session reliability keeps a session open, this feature is designed to be convenient to the user and it does not, therefore, disconnect the session.
Incoming session reliability connections use port 2598, unless you change the port number defined in the session reliability port number policy setting.
As you extend the amount of time a session is kept open, chances increase that a user might get distracted and walk away from the user device, potentially leaving the session accessible to unauthorized users.
By default, session reliability is enabled.
To disable session reliability:
By default, the session reliability time-out is set to 180 seconds.
Note: Session reliability time-out policy can be configured only with XenApp/XenDesktop 7.11 or later.
To modify the session reliability time-out:
The Session User Interface is displayed during session reliability reconnect attempts. The transparency level of the user interface can be modified using a Citrix Studio policy.
By default, the Reconnect user interface transparency is set to 80%.
To modify the Reconnect user interface transparency level:
How session reliability works
When session reliability is enabled, consider the following:
You can alter the grayscale level used for an inactive session using Desktop Studio. By default, this value is set to 80. The maximum value cannot exceed 100 (indicates a transparent window) and the minimum value can be set to 0 (a fully blacked out screen).