This article is intended for Citrix administrators and technical teams only.
Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.
This article contains Frequently Asked Questions on configuring local access using Citrix Receiver for HTML5 1.0.
A: Local access using Receiver for HTML5 1.0 is only supported with XenApp 6.5 Feature Pack 1 and StoreFront 1.2. Access to desktops provided by XenDesktop, Web and SaaS applications provided by AppController, and applications provided by previous versions of XenApp must connect through Access Gateway 10.
A: To verify that the downloaded file is not corrupted, check the MD5 checksum and compare it with the MD5 checksum that Citrix provides. The MD5 checksum can be verified with the md5sum tool for Windows.
Click here to go to the download page of md5sum tool.
Click md5sum.exe link to download the tool.
Open command prompt and browse to the directory where md5sum.exe is located.
Run md5 sum.exe followed by the path to the GroupPolicyManagement zip file. For example:
md5sum.exe C:\Users\johnwhite\Desktop\GroupPolicyManagement1.7.zip.
Verify if the md5 checksum value is equal to what Citrix posted. If the checksum value does not match, the download might be corrupted, and you should re-download the zip file and re-verify the md5 checksum value.
A: On your StoreFront server, change the pluginAssistant enable="true" to pluginAssistant enable="false", on line 38 in the file located at: C:\inetpub\wwwroot\Citrix\<storename>Web\web.config where <storename> is the name specified for the store when it was created.
Refer to Citrix eDocs - Configuring Receiver for Web Using the Configuration Files for more information.
A: The workstation might not have access to the WebSockets port (default TCP 8008) on the XenApp server. Adding a rule to the Windows Firewall on the XenApp server might be needed. This can be done by running the following command at the command prompt on your XenApp server:
netsh advfirewall firewall add rule name="Receiver for HTML5" dir=in action=allow protocol=TCP localport=8008
In Firefox "about:config", change the value for network.websocket.allowInsecureFromHTTPS from “false” to “true”. Refer to CTX134123 - Unable to Launch Application by Using HTTPS URL with Citrix Receiver for HTML5 on Firefox Web Browser.
A: No. You can install and set the unfiltered computer policy on one server in your farm, and all servers will be enabled.
A: SSL Relay support requires connections through Access Gateway 10.
A: Receiver for HTML5 1.0 supports basic encryption only.
A: Stores must be accessed through Receiver for web sites. Receiver for HTML5 does not support direct access to StoreFront stores, either by connecting to the store or by using the XenApp Services URL (legacy support).
A: When users run Chrome OS to log on to a Receiver for web site, Receiver for HTML5 is always used to provide access to their desktops and applications. If you want to prevent HTML5 1.0 from being used on Chrome OS, you must disable the client deployment feature in the "web.config" file on your StoreFront server. On your StoreFront server, change the html5 enabled="true" to html5 enabled="false" on line 41 in the file located at: C:\inetpub\wwwroot\Citrix\<storename>Web\web.config where <storename> is the name specified for the store when it is created. Refer to Citrix eDocs - Configuring Receiver for Web Using the Configuration Files for more information.
A: TCP 8008 by default. If you change the WebSockets port number setting in the XenApp policy, ensure to make the corresponding change when configuring the StoreFront server.
A: 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.