User manual

Remote applications are available on Horizon 6.0 with View and later
servers.
Display protocol for
View
n
PCoIP
n
VMware Blast (requires Horizon Agent 7.0 or later)
Preparing Connection Server for Horizon Client
Administrators must perform specific tasks to enable end users to connect to remote desktops and
applications.
Before end users can connect to Connection Server or a security server and access a remote desktop or
application, you must configure certain pool settings and security settings:
n
If you plan to use Access Point, which is available with Horizon 6 version 6.2 or later, configure
Connection Server to work with Access Point. See Deploying and Configuring Access Point. Access Point
appliances fulfill the same role that was previously played by only security servers.
n
If you are using a security server, verify that you are using the latest maintenance releases of
Connection Server 5.3.x and Security Server 5.3.x or later releases. See the View Installation document.
n
If you plan to use a secure tunnel connection for client devices and if the secure connection is
configured with a DNS host name for Connection Server or a security server, verify that the client
device can resolve this DNS name.
To enable or disable the secure tunnel, in View Administrator, go to the Edit View Connection Server
Settings dialog box and use the check box called Use secure tunnel connection to desktop.
n
Verify that a desktop or application pool has been created and that the user account that you plan to use
is entitled to access the pool. For Connection Server 5.3.x, see the topics about creating desktop pools in
the View Administration document. For Connection Server 6.0 and later, see the topics about creating
desktop and application pools in the Setting Up Desktop and Application Pools in View document.
n
To use two-factor authentication with Horizon Client, such as RSA SecurID or RADIUS authentication,
you must enable this feature on Connection Server. For more information, see the topics about two-
factor authentication in the View Administration document.
Using Embedded RSA SecurID Software Tokens
If you create and distribute RSA SecurID software tokens to end users, they need enter only their PIN, rather
than PIN and token code, to authenticate.
Setup Requirements
You can use Compressed Token Format (CTF) or dynamic seed provisioning, which is also called CT-KIP
(Cryptographic Token Key Initialization Protocol), to set up an easy-to-use RSA authentication system. With
this system, you generate a URL to send to end users. To install the token, end users paste this URL directly
into Horizon Client on their client devices. The dialog box for pasting this URL appears when end users
connect to Connection Server with Horizon Client.
After the software token is installed, end users enter a PIN to authenticate. With external RSA tokens, end
users must enter a PIN and the token code generated by a hardware or software authentication token.
The following URL prefixes are supported if end users will be copying and pasting the URL into
Horizon Client when Horizon Client is connected to an RSA-enabled Connection Server instance:
n
viewclient-securid://
n
http://127.0.0.1/securid/
Using VMware Horizon Client for Chrome OS
8 VMware, Inc.