Administration

Table Of Contents
Unauthenticated Access From Horizon Client
Log in to Horizon Client with unauthenticated access and start the published application.
To ensure greater security, the unauthenticated access user has a user alias that you can use to log in to
Horizon Client. When you select a user alias, you do not need to provide the AD credentials or UPN for
the user. After you log in to Horizon Client, you can click your published applications to start the
applications. For more information about installing and setting up Horizon Clients, see the Horizon Client
documentation at the VMware Horizon Clients documentation Web page .
Prerequisites
n
Verify that Horizon 7 version 7.1 Connection Server is configured for unauthenticated access.
n
Verify that the unauthenticated access users are created in Horizon Administrator. If the default
unauthenticated user is the only unauthenticated access user, Horizon Client connects to the
Connection Server instance with the default user.
Procedure
1 Start Horizon Client.
2 In Horizon Client, select Log in anonymously with Unauthenticated Access.
3 Connect to the Connection Server instance.
4 Select a user alias from the drop-down menu and click Login.
The default user has the "default" suffix.
5 Double-click a published application to start the application.
Using the Log In as Current User Feature Available with
Windows-Based Horizon Client
With Horizon Client for Windows, when users select the Log in as current user check box, the
credentials that they provided when logging in to the client system are used to authenticate to the Horizon
Connection Server instance and to the remote desktop. No further user authentication is required.
To support this feature, user credentials are stored on both the Connection Server instance and on the
client system.
n
On the Connection Server instance, user credentials are encrypted and stored in the user session
along with the username, domain, and optional UPN. The credentials are added when authentication
occurs and are purged when the session object is destroyed. The session object is destroyed when
the user logs out, the session times out, or authentication fails. The session object resides in volatile
memory and is not stored in Horizon LDAP or in a disk file.
View Administration
VMware, Inc. 82