User manual

If Horizon Client cannot connect to the remote desktop, perform the following tasks:
n
Determine whether Connection Server is congured not to use SSL. Horizon Client requires SSL
connections. Check whether the global seing in Horizon Administrator for the Use SSL for client
connections check box is deselected. If so, you must either select the check box, so that SSL is used, or
set up your environment so that clients can connect to an HTTPS enabled load balancer or other
intermediate device that is congured to make an HTTP connection to Connection Server.
n
Verify that the security certicate for Connection Server is working properly. If it is not, in Horizon
Administrator, you might also see that the agent on desktops is unreachable.
n
Verify that the tags set on the Connection Server instance allow connections from this user. See the View
Administration document.
n
Verify that the user is entitled to access the desktop or application. See the Seing Up Virtual Desktops in
Horizon 7 or Seing Up Published Desktops and Applications in Horizon 7 document.
Setting the Certificate Checking Mode for Horizon Client
Administrators and sometimes end users can congure whether client connections are rejected if any or
some server certicate checks fail.
Certicate checking occurs for SSL connections between Connection Server and Horizon Client. Certicate
verication includes the following checks:
n
Is the certicate intended for a purpose other than verifying the identity of the sender and encrypting
server communications? That is, is it the correct type of certicate?
n
Has the certicate expired, or is it valid only in the future? That is, is the certicate valid according to
the computer clock?
n
Does the common name on the certicate match the host name of the server that sends it? A mismatch
can occur if a load balancer redirects Horizon Client to a server that has a certicate that does not match
the host name entered in Horizon Client. Another reason a mismatch can occur is if you enter an IP
address rather than a host name in the client.
n
Is the certicate signed by an unknown or untrusted certicate authority (CA)? Self-signed certicates
are one type of untrusted CA.
To pass this check, the certicate's chain of trust must be rooted in the device's local certicate store.
N For information about distributing a self-signed root certicate that users can install on their Chrome
OS devices, as well as instructions for installing a certicate on a Chrome OS device, see the documentation
on the Google Web site.
To set the security mode, tap the  (gear) icon in the upper-right corner of the Horizon Client screen,
tap Security options, and tap Security mode. You have three choices:
n
Never connect to untrusted servers. If any of the certicate checks fails, the client cannot connect to the
server. An error message lists the checks that failed.
n
Warn before connecting to untrusted servers. If a certicate check fails because the server uses a self-
signed certicate, you can click Continue to ignore the warning. For self-signed certicates, the
certicate name is not required to match the server name you entered in Horizon Client.
n
Do not verify server identity . This seing means that no certicate checking occurs.
If the certicate checking mode is set to Warn, you can still connect to a Connection Server instance that uses
a self-signed certicate.
Chapter 2 Managing Remote Desktop and Application Connections
VMware, Inc. 17