Skip to main content

August 24, 2026

Upgrade Requirements for Omnissa Horizon Connection Server

The Horizon Connection Server upgrade process has specific requirements and limitations.

  • Horizon Connection Server requires a valid license for this latest release. If you have a perpetual license, you will need to download the new key specific for Omnissa Horizon 8 2006 or later releases. If you have a subscription license, no additional action is required.

  • The domain user account that you use to install the new version of Horizon Connection Server must have administrative privileges on the Horizon Connection Server host. The Horizon Connection Server administrator must have administrative credentials for vCenter Server.

  • When you run the installer, you authorize an Administrators account. You can specify the local Administrators group or a domain user or group account. Horizon 8 assigns full Horizon Administration rights, including the right to install replicated Horizon Connection Server instances, to this account only. If you specify a domain user or group, you must create the account in Active Directory before you run the installer.

  • When you back up Horizon Connection Server, the Horizon Directory configuration is exported as encrypted LDIF data. To restore the encrypted backup Horizon 8 configuration, you must provide the data recovery password. The password must contain between 1 and 128 characters.

  • Horizon Connection Server requires a TLS certificate that is signed by a CA (certificate authority) and that your clients can validate. Although a default self-signed certificate is generated in the absence of a CA-signed certificate when you install Horizon Connection Server, you must replace the default self-signed certificate as soon as possible. Self-signed certificates are shown as invalid in Omnissa Horizon Console.

    Also, updated clients expect information about the server's certificate to be communicated as part of the TLS handshake between client and server. Often updated clients do not trust self-signed certificates.

    For complete information about security certificate requirements, see "Configuring TLS Certificates for Horizon Servers" in the Horizon 8 Installation and Upgrade guide.

    Note: If your original servers already have TLS certificates signed by a CA, during the upgrade, Horizon 8 imports your existing CA-signed certificate into the Windows Server certificate store.

  • Certificates for vCenter Server and Horizon 8 servers must include certificate revocation lists (CRLs). For more information, see "Configuring Certificate Revocation Checking on Server Certificates" in the Horizon 8 Installation and Upgrade document.

    Important: If your company uses proxy settings for Internet access, you might have to configure your Horizon Connection Server hosts to use the proxy. This step ensures that servers can access certificate revocation checking sites on the Internet. You can use Microsoft Netshell commands to import the proxy settings to Horizon Connection Server. For more information, see "Troubleshooting Horizon Server Certificate Revocation Checking" in the Horizon 8 Installation and Upgrade document.

  • You might need to make security protocol configuration changes to continue to be compatible with vSphere. If possible, apply patches to ESXi and vCenter Server to support TLSv1.1, TLSv1.2 and TLSv1.3 before upgrading Horizon Connection Server.

If you plan to perform fresh installations of Horizon Connection Server instances on additional physical or virtual machines, see the complete list of installation requirements in the Horizon 8 Installation and Upgrade document.

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…