Installation and Setup Guide

7 Double-click a remote desktop or application to connect.
If you are connecting to a session-based remote desktop, which is hosted on a Microsoft RDS host,
and if the desktop is already set to use a different display protocol, you will not be able to connect
immediately. You will be prompted to either use the protocol that is currently set or have the system
log you off of the remote operating system so that a connection can be made with the protocol you
selected.
After you are connected, the client window appears.
If authentication to View Connection Server fails or if the client cannot connect to the remote desktop or
application, perform the following tasks:
n
Determine whether View Connection Server is configured not to use SSL. The client software
requires SSL connections. Check whether the global setting in View 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 configured to make an HTTP connection to View
Connection Server.
n
Verify that the security certificate for View Connection Server is working properly. If it is not, in View
Administrator, you might also see that the View Agent on desktops is unreachable. These are
symptoms of additional connection problems caused by certificate problems.
n
Verify that the tags set on the View Connection Server instance allow connections from this user. See
the View Administration document.
n
Verify that the user is entitled to access this desktop or application. See the Setting Up Published
Desktops and Applications in Horizon 7 document.
n
If you are using the RDP display protocol to connect to a remote desktop, verify that the remote
operating system allows remote desktop connections.
Connect to Published Applications Using Unauthenticated
Access
You can connect to published applications using an unauthenticated access account with Horizon Client.
Before you have end users access their published applications using unauthenticated access, test that
you can connect to the published applications from a client device using an unauthenticated access user
account.
Prerequisites
n
Verify that Horizon 7 version 7.1 or later Connection Server is configured for unauthenticated access.
n
Verify that your unauthenticated access users are created in Horizon Administrator. If the default
unauthenticated user is the only unauthenticated access user, the Horizon Client connects to the
Connection Server with the default user.
VMware Horizon Client for Linux Installation and Setup Guide
VMware, Inc. 59