User manual

8 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 dierent 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 o 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 congured not to use SSL. The client software requires
SSL connections. Check whether the global seing 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 congured to make an HTTP connection to View Connection Server.
n
Verify that the security certicate 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 certicate 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 Seing Up Desktop and
Application Pools in View 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 unuauthenticated 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 Connection Server is congured 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.
Procedure
1 Either open a terminal window and enter vmware-view or search the applications for VMware Horizon
Client, and double-click the icon.
2 In the Horizon Client home screen, select File > Log in anonymously using Unauthenticated Access
from the menu bar, if it is not already selected.
3 Connect to the Connection Server that is congured for unauthenticated access.
n
If the server that you need has not yet been added, double-click the + Add Server buon if no
servers have yet been added or click the + New Server buon in the menu bar to add a new one,
and enter the name of the Connection Server or a security server, and click Connect.
n
If the server that you need is displayed in the Horizon Client home screen, right-click the icon for
the server and select Connect from the context menu.
You might see a message that you must conrm before the login dialog box appears.
Chapter 3 Managing Remote Desktop and Application Connections
VMware, Inc. 51