Installation

3 On the General tab, delete the Friendly name text and type vdm.
4 Click Apply and click OK.
5 Verify that no other server certicates in the Personal >  folder have a Friendly name of vdm.
a Locate any other server certicate, right-click the certicate, and click Properties.
b If the certicate has a Friendly name of vdm, delete the name, click Apply, and click OK.
What to do next
Import the root certicate and intermediate certicates into the Windows local computer certicate store.
After all certicates in the chain are imported, you must restart the View Connection Server service or
Security Server service to make your changes take eect.
Import a Root Certificate and Intermediate Certificates into a Windows
Certificate Store
If the Windows Server host on which View Connection Server is installed does not trust the root certicate
for the signed SSL server certicate, you must import the root certicate into the Windows local computer
certicate store. In addition, if the View Connection Server host does not trust the root certicates of the SSL
server certicates congured for security server, View Composer, and vCenter Server hosts, you also must
import those root certicates.
If the View Connection Server, security server, View Composer, and vCenter Server certicates are signed by
a root CA that is known and trusted by the View Connection Server host, and there are no intermediate
certicates in your certicate chains, you can skip this task. Commonly used Certicate Authorities are
likely to be trusted by the host.
You must import untrusted root certicates on all replicated View Connection Server instances in a pod.
N You do not have to import the root certicate into View Composer, vCenter Server, or security server
hosts.
If a server certicate is signed by an intermediate CA, you also must import each intermediate certicate in
the certicate chain. To simplify client conguration, import the entire intermediate chain to security server,
View Composer, and vCenter Server hosts as well as View Connection Server hosts. If intermediate
certicates are missing from a View Connection Server or security server host, they must be congured for
clients and computers that launch View Administrator. If intermediate certicates are missing from a View
Composer or vCenter Server host, they must be congured for each View Connection Server instance.
If you already veried that the entire certicate chain is imported into the Windows local computer
certicate store, you can skip this task.
N If a SAML authenticator is congured for use by a View Connection Server instance, the same
guidelines apply to the SAML 2.0 authenticator. If the View Connection Server host does not trust the root
certicate congured for a SAML authenticator, or if the SAML server certicate is signed by an
intermediate CA, you must ensure that the certicate chain is imported into the Windows local computer
certicate store.
Procedure
1 In the MMC console on the Windows Server host, expand the  (Local Computer) node and
go to the Trusted Root  Authorities >  folder.
n
If your root certicate is in this folder, and there are no intermediate certicates in your certicate
chain, skip to step 7.
n
If your root certicate is not in this folder, proceed to step 2.
View Installation
86 VMware, Inc.