Replace the Default HTTP Ports or NICs for Omnissa Horizon Connection Server Instances

You can replace the default HTTP ports or NICs for a Horizon Connection Server instance by editing the locked.properties file on the server computer. Your organization might require you to perform these tasks to comply with organization policies or to avoid contention. Configuration Properties for Horizon Connection Server Instances provides a summary of the configuration properties you can set in the locked.properties file.

The default SSL port is 443. The default non-SSL port is 80. The default management port follows the SSL port.

The port that is specified in the secure tunnel External URL does not change as a result of changes that you make to ports in this procedure. Depending on your network configuration, you might have to change the secure tunnel External URL port as well.

If the server computer has multiple NICs, the computer listens on all NICs by default. You can select one NIC to listen on the configured port by specifying the IP address that is bound to that NIC.

During installation, Omnissa Horizon 8 configures the Windows firewall to open the required default ports. If you change a port number or the NIC on which it listens, you must manually reconfigure your Windows firewall to open the updated ports so that client devices can connect to the server.

If you change the SSL port number and you need HTTP redirection to continue working, you must also change the port number for HTTP redirection. See Change the Port Number for HTTP Redirection to Horizon Connection Server.

Prerequisites

Verify that the port that is specified in the External URL for this Horizon Connection Server instance will continue to be valid after you change ports in this procedure.

Procedure

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

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

   The properties in the locked.properties file are case sensitive.

2. Add the serverPort, serverPortNonSsl, or serverPortAdmin property, as required, to the locked.properties file. For example:

   serverPort=4443
   serverPortNonSsl=8080
   serverPortAdmin=9443
   

3. If the server computer has multiple NICs, choose one for each of the configured ports.

   For example:

   serverHost=10.20.30.40
   serverHostNonSsl=10.20.30.40
   serverHostAdmin=30.40.50.60
   

   Typically, both the SSL and non-SSL listeners are configured to use the same NIC. However, if you use the serverProtocol=http property to off-load SSL for client connections, you can set the serverHost property to a separate NIC to provide SSL connections to systems that need access to the management port. In all cases, it is possible to have the management port on the same NIC as the SSL port, or on a different NIC, as shown in the example. If not specified, the management port follows the SSL port. If you do not specify a NIC, or you specify NICs to be the same, different port numbers are needed for each entry.

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

Configuration Properties for Horizon Connection Server Instances

Note: Starting with 2412, you can configure a custom port and/or interface for the Horizon Console and management APIs that is different from the SSL port, to separate management traffic from client traffic.

Property	Default value	Other values	Notes
serverProtocol	https	http	Use http if SSL is terminated elsewhere
serverPort	443	Any port number
serverHost	all interfaces	IP address
serverPortAdmin	as serverPort	Any port number	Set 9443 or another port number to separate management traffic from client traffic
serverHostAdmin	as serverHost	IP address	Ignored if serverPortAdmin is not set
disableRedirection	false	true	Always true if serverPort or serverPortAdmin is "80"
serverPortNonSsl	80	Any port number	Ignored if disableRedirection is true
serverHostNonSsl	all interfaces	IP address	ignored if disableRedirection is true

What to do next

If necessary, manually configure your Windows firewall to open the updated ports.