Allow Omnissa Horizon Web Client Through a Gateway

Note: Omnissa Horizon Web Client is available with Horizon 8 versions 2412 and later. For Horizon 8 versions 2406 and earlier, Horizon Web Client is called "HTML Access." This documentation page uses the name "Horizon Web Client" to refer to both Horizon Web Client and HTML Access.

Omnissa Horizon Connection Server instances that are directly behind a gateway, such as Omnissa Unified Access Gateway, must know the address by which browsers will connect to the gateway when users use Horizon Web Client.

For Horizon Connection Server instances that are behind a load-balancer or load-balanced gateway, perform the procedure described in Allow Omnissa Horizon Web Client Through a Load Balancer.

You must perform this procedure for each Horizon Connection Server that is behind the gateway.

Procedure

1. Create or edit the locked.properties file in the gateway configuration folder on the Horizon Connection Server host.

   For example: install_directory\Omnissa\Horizon\Server\sslgateway\conf\locked.properties

2. Add the portalHost property and set it to the address of the gateway.

   For example, if https://horizon-gateway.example.com is the address that browsers use to access Omnissa Horizon 8 through the gateway, add portalHost=horizon-gateway.example.com to the locked.properties file.

   If the Horizon Connection Server instance is behind multiple gateways, you can specify each gateway by adding a number to the portalHost property, for example:

   portalHost.1=horizon-gateway-1.example.com
   portalHost.2=horizon-gateway-2.example.com
   

   You must also specify multiple portalHost properties if a single gateway machine is known by more than one name.

3. Save the locked.properties file.

4. Restart the Horizon Connection Server service to make your changes take effect.