5.2

Table Of Contents
3 Examine the certificate thumbprint that was configured for the vCenter Server or View Composer
instance.
a On the vCenter Server or View Composer host, start the MMC snap-in and open the Windows
Certificate Store.
b Navigate to the vCenter Server or View Composer certificate.
c Click the Certificate Details tab to display the certificate thumbprint.
Similarly, examine the certificate thumbprint for a SAML 2.0 authenticator. If appropriate, take the
preceding steps on the SAML 2.0 authenticator host.
4 Verify that the thumbprint in the Certificate Information window matches the thumbprint for the
vCenter Server or View Composer instance.
Similarly, verify that the thumbprints match for a SAML 2.0 authenticator.
5 Determine whether to accept the certificate thumbprint.
Option Description
The thumbprints match.
Click Accept to use the default certificate.
The thumbprints do not match.
Click Reject.
Troubleshoot the mismatched certificates. For example, you might have
provided an incorrect IP address for vCenter Server or View Composer.
Configuring View Client Connections
View clients communicate with a View Connection Server or security server host over secure connections.
The initial View Client connection, which is used for user authentication and View desktop selection, is
created over HTTPS when a user provides a domain name to View Client. If firewall and load balancing
software are configured correctly in your network environment, this request reaches the View Connection
Server or security server host. With this connection, users are authenticated and a desktop is selected, but
users have not yet connected to View desktops.
When users connect to View desktops, by default View Client makes a second connection to the View
Connection Server or security server host. This connection is called the tunnel connection because it
provides a secure tunnel for carrying RDP and other data over HTTPS.
When users connect to View desktops with the PCoIP display protocol, View Client can make a further
connection to the PCoIP Secure Gateway on the View Connection Server or security server host. The PCoIP
Secure Gateway ensures that only authenticated users can communicate with View desktops over PCoIP.
When the secure tunnel or PCoIP Secure Gateway is disabled, View desktop sessions are established
directly between the client system and the View desktop virtual machine, bypassing the View Connection
Server or security server host. This type of connection is called a direct connection.
Desktop sessions that use direct connections remain connected even if View Connection Server is no longer
running.
Typically, to provide secure connections for external clients that connect to a security server or View
Connection Server host over a WAN, you enable both the secure tunnel and the PCoIP Secure Gateway. You
can disable the secure tunnel and the PCoIP Secure Gateway to allow internal, LAN-connected clients to
establish direct connections to View desktops.
Certain View Client endpoints, such as thin clients, do not support the tunnel connection and use direct
connections for RDP data, but do support the PCoIP Secure Gateway for PCoIP data.
Chapter 8 Configuring View for the First Time
VMware, Inc. 103