Installation

Value Description
1 Do not perform certificate revocation checking.
2 Check only the server certificate. Do not check any other certificates in the chain.
3 Check all certificates in the chain.
4 (Default) Check all certificates except the root certificate.
If this registry value is not set, or if the value set is not valid (that is, if the value is not 1, 2, 3, or 4), all
certificates are checked except the root certificate. Set this registry value on each server on which you intend
to modify revocation checking. You do not have to restart the system after you set this value.
NOTE If your organization uses proxy settings for Internet access, you might have to configure your View
Connection Server computers to use the proxy settings to ensure that certificate revocation checking can be
performed for security servers or View Connection Server instances that are used for secure client
connections. If a View Connection Server instance cannot access the Internet, certificate revocation checking
might fail, and the View Connection Server instance or paired security servers might show up as red on the
View Administrator dashboard. To resolve this issue, see "Troubleshooting Security Server Certificate
Revocation Checking" in the View Administration document.
Configure the PCoIP Secure Gateway to Use a New SSL Certificate
To comply with industry or jurisdiction security regulations, you can replace the default SSL certificate that
is generated by the PCoIP Secure Gateway (PSG) service with a certificate that is signed by a CA.
In View 5.2 or later releases, the PSG service creates a default, self-signed SSL certificate when the service
starts up. The PSG service presents the self-signed certificate to clients running Horizon Client 2.0 (or
Horizon Client 5.2 for Windows) or later releases that connect to the PSG.
The PSG also provides a default legacy SSL certificate that is presented to clients running older clients or
earlier releases that connect to the PSG.
The default certificates provide secure connections from client endpoints to the PSG and do not require
further configuration in View Administrator. However, configuring the PSG service to use a CA-signed
certificate is highly recommended, particularly for deployments that require you to use security scanners to
pass compliance testing.
Although it is not required, you are most likely to configure new CA-signed SSL certificates for your servers
before you replace the default PSG certificate with a CA-signed certificate. The procedures that follow
assume that you already imported a CA-signed certificate into the Windows certificate store for the server
on which the PSG is running.
NOTE If you are using a security scanner for compliance testing, you might want to start by setting the PSG
to use the same certificate as the server and scan the View port before the PSG port. You can resolve trust or
validation issues that occur during the scan of the View port to ensure that these issues do not invalidate
your test of the PSG port and certificate. Next, you can configure a unique certificate for the PSG and do
another scan.
Procedure
1 Verify That the Server Name Matches the PSG Certificate Subject Name on page 84
When a View Connection Server instance or security server is installed, the installer creates a registry
setting with a value that contains the FQDN of the computer. You must verify that this value matches
the server name part of the URL that security scanners use to reach the PSG port. The server name also
must match the subject name or a subject alternate name (SAN) of the SSL certificate that you intend to
use for the PSG.
Chapter 7 Configuring SSL Certificates for View Servers
VMware, Inc. 83