To set up TLS server certificates for Horizon 7 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, security server, or View Composer. 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 Horizon 7 server host.
  3. For Connection Server instances and security servers, modify the certificate Friendly name to vdm.

    Assign the Friendly name vdm to only one certificate on each Horizon 7 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 security server, View Composer, and 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 View Composer, vCenter Server, or security 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 Horizon 7 server, they must be configured for clients and computers that launch Horizon Administrator.

  6. For View Composer instances, take one of these steps:
    • If you import the certificate into the Windows local computer certificate store before you install View Composer, you can select your certificate during the View Composer installation.
    • If you intend to replace an existing certificate or the default, self-signed certificate with a new certificate after you install View Composer, run the SviConfig ReplaceCertificate utility to bind the new certificate to the port used by View Composer.
  7. 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 Administrator trust the root and intermediate certificates.

  8. Determine whether to reconfigure certificate revocation checking.

    Connection Server performs certificate revocation checking on Horizon 7 servers, View Composer, 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.