Installation

Table Of Contents
Configure Horizon Client for iOS to Trust Root and Intermediate Certificates
If a server certicate is signed by a CA that is not trusted by iPads and iPhones that run Horizon Client for
iOS, you can congure the the device to trust the root and intermediate certicates. You must distribute the
root certicate and all intermediate certicates in the trust chain to the devices
Procedure
1 Send the root certicate and intermediate certicates as email aachments to the iPad.
2 Open the email aachment for the root certicate and select Install.
The certicate displays the following message:
Unverifiable Profile. The authenticity of Certificate name cannot be verified. Installing
this profile will change settings on your iPad.
Root Certificate. Installing the certificate Certificate name will add it to the list of
trusted certificates on your iPad.
3 Select Install again.
4 Repeat steps 2 and 3 for all intermediate certicates in the trust chain.
Configuring Certificate Revocation Checking on Server Certificates
Each View Connection Server instance performs certicate revocation checking on its own certicate and on
those of the security servers paired to it. Each instance also checks the certicates of vCenter and View
Composer servers whenever it establishes a connection to them. By default, all certicates in the chain are
checked except the root certicate. You can, however, change this default.
If a SAML 2.0 authenticator is congured for use by a View Connection Server instance, View Connection
Server also performs certicate revocation checking on the SAML 2.0 server certicate.
View supports various means of certicate revocation checking, such as certicate revocation lists (CRLs)
and the Online Certicate Status Protocol (OCSP). A CRL is a list of revoked certicates published by the
CA that issued the certicates. OCSP is a certicate validation protocol that is used to get the revocation
status of an X.509 certicate.
With CRLs, the list of revoked certicates is downloaded from a certicate distribution point (DP) that is
often specied in the certicate. The server periodically goes to the CRL DP URL specied in the certicate,
downloads the list, and checks it to determine whether the server certicate has been revoked. With OCSP,
the server sends a request to an OCSP responder to determine the revocation status of the certicate.
When you obtain a server certicate from a third-party certicate authority (CA), the certicate includes one
or more means by which its revocation status can be determined, including, for example, a CRL DP URL or
the URL for an OCSP responder. If you have your own CA and generate a certicate but do not include
revocation information in the certicate, the certicate revocation check fails. An example of revocation
information for such a certicate could include, for example, a URL to a Web-based CRL DP on a server
where you host a CRL.
If you have your own CA but do not or cannot include certicate revocation information in your certicate,
you can choose not to check certicates for revocation or to check only certain certicates in a chain. On the
server, with the Windows Registry Editor, you can create the string (REG_SZ) value
, under HKLM\Software\VMware, Inc.\VMware VDM\Security, and set this
value to one of the following data values.
View Installation
90 VMware, Inc.