After you import a server certificate into the Windows local computer certificate store, you must take additional steps to allow a View server to use the certificate.

1

Verify that the server certificate was imported successfully.

2

Change the certificate Friendly name to vdm.

vdm must be lower case. Any other certificates with the Friendly name vdm must be renamed, or you must remove the Friendly name from those certificates.

You do not have to modify the Friendly name of certificates that are used by View Composer.

3

Install the root CA certificate and intermediate CA certificate in the Windows certificate store.

4

Restart the View Connection Server service, security server service, or View Composer service to allow the service to start using the new certificates.

5

If you use HTML Access in VMware Horizon View 5.2 or later, restart the VMware View Blast Secure Gateway service.

6

If you are setting up a certificate on a View Composer server, you might have to take another step.

If you set up the new certificate after you install View Composer, you must run the SviConfig ReplaceCertificate utility to replace the certificate that is bound to the port used by View Composer.

If you set up the new certificate before you install View Composer, you do not have to run the SviConfig ReplaceCertificate utility. When you run the View Composer installer, you can select the new certificate that is signed by a CA instead of the default, self-signed certificate.

For more information, see "Bind a New SSL Certificate to the port Used by View Composer" in the View Installation document.

To perform the tasks in this procedure, see the following topics:

Modify the Certificate Friendly Name

Import the Root and Intermediate Certificates into the Windows Certificate Store

For more information, see "Configure View Connection Server, Security Server, or View Composer to Use a New SSL Certificate" in the View Installation document.

Note

The View Installation topic "Import a Signed Server Certificate into a Windows Certificate Store" is not listed here because you already imported the server certificate by using the certreq utility. You should not use the Certificate Import wizard in the MMC Snap-in to import the server certificate again.

However, you can use the Certificate Import wizard to import the root CA certificate and intermediate CA certificate into the Windows certificate store.