To set up TLS server certificates for VMware Horizon servers, you must perform several high-level tasks.

In a pod of replicated Connection Server instances, you must perform these tasks on all instances in the pod.

The procedures for carrying out these tasks are described in the topics that follow this overview.

  1. Determine if you need to obtain a new signed TLS certificate from a CA.

    If your organization already has a valid TLS server certificate, you can use that certificate to replace the default TLS server certificate provided with Connection Server. To use an existing certificate, you also need the accompanying private key.

    Starting Place Action
    Your organization provided you with a valid TLS server certificate. Go directly to step 2.
    You do not have an TLS server certificate. Obtain a signed TLS server certificate from a CA.
  2. Import the TLS certificate into the Windows local computer certificate store on the VMware Horizon server host.
  3. For Connection Server instances modify the certificate Friendly name to vdm.

    Assign the Friendly name vdm to only one certificate on each VMware Horizon server host.

  4. On Connection Server computers, if the root certificate is not trusted by the Windows Server host, import the root certificate into the Windows local computer certificate store.

    In addition, if the Connection Server instances do not trust the root certificates of the TLS server certificates configured for vCenter Server hosts, you also must import those root certificates. Take these steps for Connection Server instances only. You do not have to import the root certificate to vCenter Server hosts.

  5. If your server certificate was signed by an intermediate CA, import the intermediate certificates into the Windows local computer certificate store.

    To simplify client configuration, import the entire certificate chain into the Windows local computer certificate store. If intermediate certificates are missing from the VMware Horizon server, they must be configured for clients and computers that launch Horizon Console.

  6. If your CA is not well known, configure clients to trust the root and intermediate certificates.

    Also ensure that the computers on which you launch Horizon Console trust the root and intermediate certificates.

  7. Determine whether to reconfigure certificate revocation checking.

    Connection Server performs certificate revocation checking on VMware Horizon servers and vCenter Server. Most certificates signed by a CA include certificate revocation information. If your CA does not include this information, you can configure the server not to check certificates for revocation.

    If a SAML authenticator is configured for use with a Connection Server instance, Connection Server also performs certificate revocation checking on the SAML server certificate.