This document supports the version of each product listed and
supports all subsequent versions until the document is
replaced by a new edition. To check for more recent editions of
this document, see http://www.vmware.com/support/pubs.
EN-002505-00
Using VMware Horizon Client for Android
You can find the most up-to-date technical documentation on the VMware Web site at:
hp://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
Using VMware Horizon Client for Android5
Setup and Installation7
1
System Requirements 8
System Requirements for Thin Clients 8
System Requirements for Chromebooks 9
System Requirements for Real-Time Audio-Video 9
Smart Card Authentication Requirements 10
Congure Smart Card Authentication 11
Fingerprint Authentication Requirements 12
Supported Desktop Operating Systems 13
Preparing Connection Server for Horizon Client 13
Install or Upgrade Horizon Client 14
Congure Horizon Client in Thin Client Mode 15
Using Horizon Client on a Thin Client 15
Using Embedded RSA SecurID Software Tokens 16
Congure Advanced TLS/SSL Options 17
Congure VMware Blast Options 17
Congure the Horizon Client Default View 18
Congure AirWatch to Deliver Horizon Client to Android Devices 19
Congure AirWatch to Deliver Horizon Client to Android for Work Devices 20
Horizon Client Data Collected by VMware 22
Using URIs to Congure Horizon Client25
2
Syntax for Creating vmware-view URIs 25
Examples of vmware-view URIs 28
VMware, Inc.
Managing Remote Desktop and Application Connections31
3
Seing the Certicate Checking Mode for Horizon Client 31
Connect to a Remote Desktop or Application 32
Use Unauthenticated Access to Connect to Remote Applications 35
Share Access to Local Storage 36
Add a Desktop or Application Shortcut to the Android Home Screen 37
Manage Server Shortcuts 37
Select a Favorite Remote Desktop or Application 38
Disconnecting From a Remote Desktop or Application 38
Log O From a Remote Desktop 39
Manage Desktop and Application Shortcuts 39
Using Android 7.0 Nougat Multi-Window Modes with Horizon Client 40
Using Horizon Client with Samsung DeX 40
Enable the DeX Mode Auto Launch Feature 40
3
Using VMware Horizon Client for Android
Using a Microsoft Windows Desktop or Application41
4
Feature Support Matrix for Android 41
Input Devices, Keyboards, and Keyboard Seings 44
Enable the Japanese 106/109 Keyboard Layout 44
Using the Real-Time Audio-Video Feature for Microphones 45
Using Native Operating System Gestures with Touch Redirection 45
Using the Unity Touch Sidebar with a Remote Desktop 45
Using the Unity Touch Sidebar with a Remote Application 48
Horizon Client Tools on a Mobile Device 49
Gestures 52
Multitasking 53
Copying and Pasting Text and Images 53
Saving Documents in a Remote Application 54
Screen Resolutions and Using External Displays 54
PCoIP Client-Side Image Cache 55
Internationalization and International Keyboards 56
Troubleshooting Horizon Client57
5
Collecting and Sending Logging Information 57
Enable Horizon Client Log Collection 57
Manually Retrieve and Send Horizon Client Log Files 58
Disable Horizon Client Log Collection 59
Restart a Remote Desktop 59
Reset a Remote Desktop or Remote Applications 60
Uninstall Horizon Client 60
Horizon Client Stops Responding or the Remote Desktop Freezes 61
Problem Establishing a Connection When Using a Proxy 61
Connecting to a Server in Workspace ONE Mode 61
Index63
4 VMware, Inc.
Using VMware Horizon Client for Android
This guide, Using VMware Horizon Client for Android, provides information about installing and using
VMware Horizon® Client™ software on an Android device to connect to a remote desktop or application in
the datacenter.
The information in this document includes system requirements and instructions for installing
Horizon Client for Android. This document also provides tips for improving the user experience of
navigating and using Windows desktop elements on an Android device.
This information is intended for administrators who must set up a Horizon deployment that includes
Android client devices. The information is wrien for experienced system administrators who are familiar
with virtual machine technology and datacenter operations.
VMware, Inc.
5
Using VMware Horizon Client for Android
6 VMware, Inc.
Setup and Installation1
Seing up a Horizon deployment for Android clients involves using certain Connection Server
conguration seings, meeting the system requirements for View servers and Android device clients, and
installing the Horizon Client app.
This chapter includes the following topics:
“System Requirements,” on page 8
n
“System Requirements for Thin Clients,” on page 8
n
“System Requirements for Chromebooks,” on page 9
n
“System Requirements for Real-Time Audio-Video,” on page 9
n
“Smart Card Authentication Requirements,” on page 10
n
“Congure Smart Card Authentication,” on page 11
n
“Fingerprint Authentication Requirements,” on page 12
n
“Supported Desktop Operating Systems,” on page 13
n
“Preparing Connection Server for Horizon Client,” on page 13
n
“Install or Upgrade Horizon Client,” on page 14
n
VMware, Inc.
“Congure Horizon Client in Thin Client Mode,” on page 15
n
“Using Embedded RSA SecurID Software Tokens,” on page 16
n
“Congure Advanced TLS/SSL Options,” on page 17
n
“Congure VMware Blast Options,” on page 17
n
“Congure the Horizon Client Default View,” on page 18
n
“Congure AirWatch to Deliver Horizon Client to Android Devices,” on page 19
n
“Congure AirWatch to Deliver Horizon Client to Android for Work Devices,” on page 20
n
“Horizon Client Data Collected by VMware,” on page 22
n
7
Using VMware Horizon Client for Android
System Requirements
You can install Horizon Client on Android devices.
The Android device on which you install Horizon Client, and the peripherals it uses, must meet the
following system requirements.
Android operating
systems
CPU architecture
External keyboards
Smart cards
Connection Server,
Security Server, and
View Agent or
Horizon Agent
Display protocols
Android 4.0 Ice Cream Sandwich
n
Android 4.1, 4.2, and 4.3 Jelly Bean
n
Android 4.4 KitKat
n
Android 5.0 Lollipop
n
Android 6.0 Marshmallow
n
Android 7.0 and 7.1 Nougat
n
ARM
n
x86
n
(Optional) Bluetooth and docked keyboard devices. For information about
the external devices that your specic device supports, see the
documentation from the device manufacturer.
See “Smart Card Authentication Requirements,” on page 10.
Latest maintenance release of View 6.x and later releases.
VMware recommends that you use a security server or
Unied Access Gateway appliance so that your device does not require a
VPN connection.
PCoIP
n
VMware Blast (requires Horizon Agent 7.0 or later)
n
You can also install Horizon Client for Android on certain thin clients and Chromebooks. See “System
Requirements for Thin Clients,” on page 8 and “System Requirements for Chromebooks,” on page 9.
System Requirements for Thin Clients
You can install Horizon Client for Android on certain thin clients.
The thin client on which you install Horizon Client for Android, and the external input devices it uses, must
meet certain system requirements.
Thin client models and
Android operating
systems
Remix Mini with Android 5.1 (RemixOS 2.0.205 or later)
n
NVIDIA SHIELD Android TV with Android 6.0
n
8 VMware, Inc.
Amazon Fire TV (1st Generation) with Android 5.1
n
Chapter 1 Setup and Installation
External input devices
Horizon Client generally works with any external input device, including
keyboards and controllers, that works with your thin client. For information
about the devices that your specic thin client supports, see the
documentation from the device manufacturer.
Horizon Client
requirements
Enable the Thin Client modeseing in Horizon Client. See “Congure
Horizon Client in Thin Client Mode,” on page 15.
System Requirements for Chromebooks
You can install Horizon Client for Android on certain Chromebook models. You can install Horizon Client
for Android on a Chromebook from Google Play. Not all features are supported on a Chromebook.
Chromebook models
that support Android
apps
Feature limitations
ASUS Chromebook Flip
n
Acer Chromebook R11 C738T
n
Google Chromebook Pixel (2015)
n
Google is continuing to evaluate more devices. For the latest information, go
to hps://sites.google.com/a/chromium.org/dev/chromium-os/chrome-os-
The following features are not supported when you install Horizon Client for
Android on a Chromebook.
AirWatch integration
n
Fingerprint authentication
n
Smart card authentication
n
Rich text copy and paste
n
Multiple monitors
n
System Requirements for Real-Time Audio-Video
Real-Time Audio-Video works with standard audio devices and with standard conferencing applications
such as Skype, WebEx, and Google Hangouts. To support Real-Time Audio-Video, your Horizon
deployment must meet certain software and hardware requirements.
I Only the audio-in feature is supported. The video feature is not supported.
Remote desktops
The desktops must have View Agent 5.3 or later installed. For View Agent
5.3 desktops, the desktops must also have the corresponding Remote
Experience Agent installed. For example, if View Agent 5.3 is installed, you
must also install the Remote Experience Agent from View 5.3 Feature Pack 1.
See the View Feature Pack Installation and Administration document. If you have
View Agent 6.0 or later, or Horizon Agent 7.0 or later, no feature pack is
required.
VMware, Inc. 9
Using VMware Horizon Client for Android
To use Real-Time Audio-Video with RDS desktops and remote applications,
you must have Horizon Agent 7.0.2 or later.
Client access device
Real-Time Audio Video is supported on all Android devices that run
Horizon Client for Android. For more information, see “System
Requirements,” on page 8.
Smart Card Authentication Requirements
Client systems that use a smart card for user authentication must meet certain requirements.
VMware recommends that you use an Android 4.0 or later operating system. The CPU architecture may be
ARM or x86. VMware tested the baiMobile 3000MP Bluetooth Smart Card reader, baiMobile 301MP USB
Smart Card reader, and baiMobile 301MP_LT Smart Card reader.
Each client system that uses a smart card for user authentication must have the following software and
hardware:
Horizon Client
n
A compatible smart card reader
n
Smart card middleware
n
The Android device app must support your baiMobile smart card reader. For example, one such app is
baiMobile PCSC-Lite (Android device tile name baiMobile PC/SC). Horizon Client for Android contains
support for both the baiMobile 3000MP Bluetooth and baiMobile 301MP USB smart card readers.
Without such an app, you can pair the Bluetooth card reader with the Android device, but you cannot
connect it. The app sends a connection request to the reader and you tap the OKbuon on the reader to
establish the Bluetooth connection.
Product-specic application drivers
n
You must also install product-specic application drivers on the remote desktops or Microsoft RDS host.
VMware tested the ActiveClient6.2.0.50, ActivClient_7.0.1, Gemalto.MiniDriver.NET.inf, and Charismathics
CSTC PIV 5.2.2 drivers.
Users that authenticate with smart cards must have a smart card and each smart card must contain a user
certicate.
In addition to meeting these requirements for Horizon Client systems, other Horizon components must
meet certain conguration requirements to support smart cards:
For information about conguring Connection Server to support smart card use, see the View
n
Administration document.
You must add all applicable Certicate Authority (CA) certicates for all trusted user certicates to a
server truststore le on the Connection Server host or security server host. These certicates include
root certicates and must include intermediate certicates if the user's smart card certicate was issued
by an intermediate certicate authority.
For information about tasks you might need to perform in Active Directory to implement smart card
n
authentication, see the View Administration document.
Enabling the Username Hint Field in Horizon Client
In some environments, smart card users can use a single smart card certicate to authenticate to multiple
user accounts. Users enter their user name in the Username hinteld during smart card sign-in.
10 VMware, Inc.
To make the Username hinteld appear on the Horizon Client login dialog box, you must enable the smart
card user name hints feature for the Connection Server instance in Horizon Administrator. The smart card
user name hints feature is supported only with Horizon 7 version 7.0.2 and later servers and agents. For
information about enabling the smart card user name hints feature, see the View Administration document.
If your environment uses an Unied Access Gateway appliance rather than a security server for secure
external access, you must congure the Unied Access Gateway appliance to support the smart card user
name hints feature. The smart card user name hints feature is supported only with Unied Access Gateway
2.7.2 and later. For information about enabling the smart card user name hints feature in
Unied Access Gateway, see the Deploying and ConguringUnied Access Gateway document.
N Horizon Client still supports single-account smart card certicates when the smart card user name
hints feature is enabled.
Configure Smart Card Authentication
Conguration tasks include connecting and pairing the card reader with the device and seing the smart
card removal policy.
Prerequisites
Verify that you are using the correct version of the client, desktop agent, server, operating system, smart
n
card reader, and smart card. See “Smart Card Authentication Requirements,” on page 10.
Chapter 1 Setup and Installation
Verify that smart card middleware is installed on the Android device.
n
If you have not already done so, perform the tasks described in "Prepare Active Directory for Smart
n
Card Authentication," in the View Installation document.
Congure Horizon servers to support smart card use. See the topic "Congure Smart Card
n
Authentication," in the View Administration document.
Procedure
1Install the smart card middleware app on the device.
2Pair the device with the smart card reader, according to the documentation provided by the
manufacturer of the reader.
If you are using a Bluetooth smart card reader, a randomly generated number is displayed on both
devices during this process. When you conrm that the numbers match, you establish secure Bluetooth
communication.
VMware, Inc. 11
Using VMware Horizon Client for Android
3Congure the smart card removal policy.
OptionDescription
Set the policy on the server
Set the policy on the desktop
If you use Horizon Administrator to set a policy, the choices are to
disconnect users from Connection Server when they remove their smart
cards or to keep users connected to Connection Server when they remove
their smart cards and let them start new desktop or application sessions
without reauthenticating.
aIn Horizon Administrator, select View > Servers.
b On the Connection Servers tab, select the Connection Server instance
and click Edit.
cOn the Authentication tab, select or deselect the Disconnect user
sessions on smart card removal check box to congure the smart card
removal policy.
d Click OK to save your changes.
e Restart the Connection Server service to make your changes take eect.
If you select the Disconnect user sessions on smart card removal check
box, Horizon Client returns to the Recent tab when users remove their
smart cards.
If you use the Group Policy Editor (gpedit.msc), you have the following
possible seings: no action, lock workstation, force log o, or Disconnect if
a Remote Desktop Services session.
After you open gpedit.msc in the desktop operating system, go to
Windows > Security > Local policies > Security options >
Interactive logon: smart card removal behavior. Run the
gpupdate /force command after you change the conguration to force a
group policy refresh.
Fingerprint Authentication Requirements
To use ngerprint authentication in Horizon Client, the Android device on which you install Horizon Client
must meet certain requirements.
Android device models
Operating system
requirements
Connection Server
requirements
Horizon Client
requirements
Any Android device model that has a ngerprint sensor and native
ngerprint reader functionality.
Android 6 (Marshmallow) and later
n
The Fingerprint Authentication option must be enabled and at least one
n
ngerprint must be enrolled.
Horizon 6 version 6.2 or a later release.
n
Enable biometric authentication in Connection Server. For information,
n
see "Congure Biometric Authentication" in the View Administration
document.
The Connection Server instance must present a valid root-signed
n
certicate to Horizon Client.
Set the certicate checking mode to Never connect to untrusted servers
n
or Warn before connecting to untrusted servers. For information aboutseing the certicate checking mode, see “Seing the Certicate
Checking Mode for Horizon Client,” on page 31.
12 VMware, Inc.
Enable ngerprint authentication by tapping Enable Fingerprint on the
n
server login window. After you successfully log in, your Active
Directory credentials are stored securely in your Android device. The
Enable Fingerprint option is shown the rst time you log in and does
not appear after ngerprint authentication is enabled.
You can use ngerprint authentication with smart card authentication and as part of two-factor
authentication with RSA SecurID and RADIUS authentication. If you use ngerprint authentication with
smart card authentication, Horizon Client connects to the server after you enter your PIN and the
ngerprint authentication window does not appear.
Supported Desktop Operating Systems
Administrators create virtual machines with a guest operating system and install agent software in the guest
operating system. End users can log in to these virtual machines from a client device.
For a list of the supported Windows guest operating systems, see the View Installation document.
Some Linux guest operating systems are also supported if you have View Agent 6.1.1 or later, or
Horizon Agent 7.0 or later. For information about system requirements, conguring Linux virtual machines
for use in Horizon, and a list of supported features, see Seing Up Horizon 6 for Linux Desktops or Seing UpHorizon 7 for Linux Desktops.
Chapter 1 Setup and Installation
Preparing Connection Server for Horizon Client
Administrators must perform specic 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 congure certain pool seings and security seings:
If you plan to use Unied Access Gateway, congure Connection Server to work with
n
Unied Access Gateway. See the Deploying and ConguringUnied Access Gateway document.
Unied Access Gateway appliances fulll the same role that was previously played by only security
servers.
If you are using a security server, verify that you are using the latest maintenance releases of
n
Connection Server 5.3.x and Security Server 5.3.x or later releases. For more information, see the View
Installation document.
If you plan to use a secure tunnel connection for client devices and if the secure connection is
n
congured 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 Horizon Administrator, go to the Edit Horizon Connection
Server Seings dialog box and use the check box called Use secure tunnel connection to desktop.
Verify that a desktop or application pool has been created and that the user account that you plan to use
n
is entitled to access the pool. For information, see the Seing Up Virtual Desktops in Horizon 7 or Seing
Up Published Desktops and Applications in Horizon 7 document.
To use two-factor authentication with Horizon Client, such as RSA SecurID or RADIUS authentication,
n
you must enable this feature on Connection Server. For more information, see the topics about twofactor authentication in the View Administration document.
To hide security information in Horizon Client, including server URL information and the Domain
n
drop-down menu, enable the Hide server information in client user interface and Hide domain list in
client user interface seings in Horizon Administrator. These global seings are available in Horizon 7
version 7.1 and later. For information about conguring global seings, see the View Administration
document.
VMware, Inc. 13
Using VMware Horizon Client for Android
To authenticate when the Domain drop-down menu is hidden, users must provide domain information
by entering their user name in the format domain\username or username@domain in the User name text
box.
I If you enable the Hide server information in client user interface and Hide domain list
in client user interface seings and select two-factor authentication (RSA SecureID or RADIUS) for the
Connection Server instance, do not enforce Windows user name matching. Enforcing Windows user
name matching will prevent users from being able to enter domain information in the user name text
box and login will always fail. For more information, see the topics about two-factor authentication in
the View Administration document.
To enable end users to save their passwords with Horizon Client, so that they do not always need to
n
supply credentials when connecting to a Connection Server instance, congure Horizon LDAP for this
feature on the Connection Server host.
Users can save their passwords if Horizon LDAP is congured to allow it, if the Horizon Client
certicateverication mode is set to Warn before connecting to untrusted servers or Never connect to
untrusted servers, and if Horizon Client can fully verify the server certicate that Connection Server
presents. For instructions, see the View Administration document.
Verify that the desktop or application pool is set to use the VMware Blast display protocol or the PCoIP
n
display protocol. For information, see the Seing Up Virtual Desktops in Horizon 7 and Seing Up
Published Desktops and Applications in Horizon 7 documents.
To provide users unauthenticated access to published applications in Horizon Client, you must enable
n
this feature in Connection Server. For more information, see the topics about unauthenticated access in
the View Administration document.
Install or Upgrade Horizon Client
Horizon Client for Android is an Android app, and you install it just as you do other Android apps.
Prerequisites
If you have not already set up the device, do so. See the manufacturer's user's guide for your device.
n
Verify that you have the URL for a download page that contains the Horizon Client installer. This URL
n
might be the VMware Downloads page at hp://www.vmware.com/go/viewclients.
Become familiar with your device's procedure for installing apps.
n
Devices from dierent manufacturers use dierent methods for installing Android apps. See the
manufacturer's user's guide for your device. Depending on the device, you might have to perform the
following tasks before you can install an app:
Install a particular driver.
n
Install a le browser.
n
Procedure
1Browse to the URL for downloading the Horizon Client app, or search for the Horizon Client app in the
Google Play Store or Amazon Appstore for Android.
For some devices, you download the le to the device. For others, you download the le to a PC or a
USB device.
2If necessary, copy the app (.apkle) to your device.
3Install the app according to your device's customary procedure for installing apps.
For example, on some devices, you must tap the le to install it.
14 VMware, Inc.
What to do next
To determine that installation succeeded, verify that the Horizon app icon appears on the Apps tab on your
Android device.
The rst time you launch Horizon Client on Android 6.0 Marshmallow, the app prompts you to allow
Horizon Client to make and manage phone calls, access photos, media, and les, and record audio on your
device.
If you installed Horizon Client on a thin client, see “Congure Horizon Client in Thin Client Mode,” on
page 15.
Configure Horizon Client in Thin Client Mode
You congure Horizon Client to work on a thin client by enabling the Thin Client modeseing.
Prerequisites
Install Horizon Client on your thin client. For thin client requirements, see “System Requirements for Thin
Clients,” on page 8.
Procedure
1Start Horizon Client on your thin client.
Chapter 1 Setup and Installation
2Tap the (gear) icon in the upper-right corner of the Horizon Client window.
3Tap Thin Client mode and select the Thin Client mode check box.
What to do next
See “Using Horizon Client on a Thin Client,” on page 15.
Using Horizon Client on a Thin Client
Some features are dierent or unavailable when you use Horizon Client in thin client mode.
The Horizon Client window resolution is set to by default. The auto-t resolution is the same
n
as your thin client's HDMI output. For example, if your thin client supports HDMI 4K output, the autot resolution is 4K. If your thin client supports HDMI 1080p output, the auto-t resolution is 1920x1080.
You can downscale the resolution by modifying the Horizon Client Resolutionseing.
The Horizon Client Presentation Mode and Stay Awake display seings are not available.
n
You cannot modify the Horizon Client Keyboardseings.
n
The Horizon Client Tools radial menu is not available in remote desktops and applications.
n
In general, the gestures you use in Horizon Client depend on your thin client model and the type of
n
external input device that you use with your thin client. For example, you might have a keyboard,
mouse, remote control, or game controller. See the documentation for your external input device for
more information.
The Unity Touch sidebar contains Keyboard, , and Disconnect icons. For more information, see
n
“Using the Unity Touch Sidebar with a Remote Desktop,” on page 45 and “Using the Unity Touch
Sidebar with a Remote Application,” on page 48.
The Unity Touch sidebar is supported on Remix Mini and NVIDIA SHIELD Android TV devices. The
n
Unity Touch sidebar is not supported on Amazon Fire TV.
If you are connected to a remote desktop or application from an Amazon Fire TV device, you must use
n
a pop-up menu to display Horizon Client Seings and to disconnect from the remote desktop or
application. On a remote control or external keyboard, press the Menubuon to display the pop-up
menu.
VMware, Inc. 15
Using VMware Horizon Client for Android
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.
Horizon Client also supports le-based provisioning. When a le-based software token is issued to a user,
the authentication server generates an XML-format token le, which is called an SDTID le for its .sdtid
extension. Horizon Client can import the SDTID le directly. Users can also launch Horizon Client by
tapping the SDTID le in a le browser.
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 prexes 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:
viewclient-securid://
n
http://127.0.0.1/securid/
n
End users can install the token by tapping the URL. Both prexesviewclient-securid:// and
http://127.0.0.1/securid/ are supported. Note that not all browsers support hyperlinks that begin with
http://127.0.0.1. Also some le browsers, such as the File Manager app on the ASUS Transformer Pad,
cannot link the SDTID le with Horizon Client.
For information about using dynamic seed provisioning or le-based (CTF) provisioning, see the Web page
RSA SecurID Software Token for iPhone Devices at hp://www.rsa.com/node.aspx?id=3652 or RSA SecurID
Software Token for Android at hp://www.rsa.com/node.aspx?id=3832.
Instructions to End Users
When you create a CTFString URL or CT-KIP URL to send to end users, you can generate a URL with or
without a password or activation code. You send this URL to end users in an email that must include the
following information:
Instructions for navigating to the Install Software Token dialog box.
n
Tell end users to tap External Token in the Horizon Client dialog box that prompts them for RSA
SecurID credentials when they connect to a Connection Server instance.
CTFString URL or CT-KIP URL in plain text.
n
If the URL has formaing on it, end users will get an error message when they try to use it in
Horizon Client.
Activation code, if the CT-KIP URL that you create does not already include the activation code.
n
End users must enter this activation code in a text eld of the dialog box.
If the CT-KIP URL includes an activation code, tell end users that they need not enter anything in the
n
Password or Activation Code text box in the Install Software Token dialog box.
16 VMware, Inc.
Configure Advanced TLS/SSL Options
You can select the security protocols and cryptographic algorithms that are used to encrypt communications
between Horizon Client and Horizon servers and between Horizon Client and the agent in the remote
desktop.
By default, TLSv1.0, TLSv1.1, and TLSv1.2 are enabled. SSL v2.0 and 3.0 are not supported. The default
cipher control string is "!aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH
+AES:RSA+AES".
If you congure a security protocol for Horizon Client that is not enabled on the Horizon server to which the
client connects, a TLS/SSL error occurs and the connection fails.
For information about conguring the security protocols that are accepted by Connection Server instances,
see the View Security document.
Procedure
1Open and tap Security options.
If you are connected to a remote desktop or application in full-screen mode, tap the Horizon Client
Tools radial menu icon and tap the gear icon to access . If you are not using full-screen mode,
is in the menu in the upper right corner of the Horizon Client toolbar. If you are not connected
to a remote desktop or application, tap the gear icon in the upper right corner of the Horizon Client
window.
Chapter 1 Setup and Installation
2Tap Advanced SSL Options.
3Make sure that Use Default is unchecked.
4To enable or disable a security protocol, tap the check box next to the security protocol name.
5To change the cipher control string, replace the default string.
6(Optional) If you need to revert to the default seings, tap to select the Use Default option.
7Tap OK to save your changes.
Your changes take eect the next time you connect to the server.
Configure VMware Blast Options
You can congure H.264 decoding and network condition options for remote desktop and application
sessions that use the VMware Blast display protocol.
You cannot congure VMware Blast seings after you log in to a server.
JPG/PNG encoding is always used in multi-monitor mode, even when H.264 decoding is enabled.
Prerequisites
This feature requires Horizon Agent 7.0 or later.
Procedure
1Before you log in to a server, tap the (gear) icon in the upper-right corner of the Horizon Client
window and tap VMware Blast.
You cannot congure VMware Blast seings after you log in to a server.
VMware, Inc. 17
Using VMware Horizon Client for Android
2Congure the decoding and network condition options.
OptionAction
H.264
Network Condition
Congure this option, before or after connecting to Connection Server, to
allow H.264 decoding in Horizon Client.
When this option is selected (the default seing), Horizon Client uses H.
264 decoding if the agent supports H.264 software or hardware encoding.
If the agent does not support H.264 software or hardware encoding,
Horizon Client uses JPG/PNG decoding.
Deselect this option to use JPG/PNG decoding.
You can only congure this option before connecting to Connection Server.
Select one of the following network condition options:
Excellent - Horizon Client uses only TCP networking. This option is
n
ideal for a LAN environment.
Typical (default) - Horizon Client works in mixed mode. In mixed
n
mode, Horizon Client uses TCP networking when connecting to the
server and uses Blast Extreme Adaptive Transport (BEAT) if the agent
and Blast Security Gateway (if enabled) support BEAT connectivity.
This option is the default seing.
Poor - Horizon Client uses only BEAT networking if the BEAT Tunnel
n
Server is enabled on the server, otherwise it switches to mixed mode.
N In Horizon 7 version 7.1 and earlier, Connection Server and
Security Server instances do not support the BEAT Tunnel Server.
Unied Access Gateway 2.9 and later supports the BEAT Tunnel Server.
Blast Security Gateway for Connection Server and Security Server
instances do not support BEAT networking.
Configure the Horizon Client Default View
You can congure whether recently used desktops and applications or server shortcuts appear when you
launch Horizon Client.
Procedure
1Open and tap Display.
If you are connected to a remote desktop or application in full-screen mode, tap the Horizon Client
Tools radial menu icon and tap the gear icon to access . If you are not using full-screen mode,
is in the menu in the upper right corner of the Horizon Client toolbar. If you are not connected
to a remote desktop or application, tap the gear icon in the upper right corner of the Horizon Client
window.
2Tap Default launch view.
3Tap an option to select the default view.
OptionDescription
Recent
Servers
The default view you selected takes eect immediately.
The Recent tab appears when you launch Horizon Client. The Recent tab
contains shortcuts to recently used desktops and applications. This is the
default seing.
The Servers tab appears when you launch Horizon Client. The Servers tab
contains shortcuts to the servers that you added to Horizon Client.
18 VMware, Inc.
Chapter 1 Setup and Installation
Configure AirWatch to Deliver Horizon Client to Android Devices
You can congure AirWatch to deliver Horizon Client to Android device users. You can optionally specify a
default list of Connection Server instances. The Connection Server instances that you specify appear as
shortcuts in Horizon Client.
If your environment is set up for Android for Work, do not follow this procedure. Instead, see “Congure
AirWatch to Deliver Horizon Client to Android for Work Devices,” on page 20.
Prerequisites
Install and deploy AirWatch. See hp://www.air-watch.com.
n
Download the Horizon Client app from the VMware Downloads page at
n
hp://www.vmware.com/go/viewclients or from the Google Play Store or Amazon Appstore for
Android.
Become familiar with the AirWatch console. This procedure assumes you know how to use the
n
AirWatch console. For more information, see the AirWatch documentation or online help.
Decide which version of Horizon Client to deploy with the AirWatch console. The AirWatch console
n
cannot deploy both the ARM and the x86 version at the same time.
Procedure
1Log in to the AirWatch console as an administrator.
2Select Accounts > Users > List View, click Add, select Add User, and add user accounts for the users
who will run Horizon Client on their Android devices.
3Select Accounts > Users > User Groups > List View, click Add, select Add User Group, and create a
user group for the user accounts that you created.
4Create an application prole for Horizon Client in AirWatch.
The server property species the IP address or host name of a server, the username and domain
properties specify the name and domain of a user that is entitled to use the server, and the
description property species a description of the server.
VMware, Inc. 19
Using VMware Horizon Client for Android
5Upload and add the Horizon Client application to AirWatch.
aSelect Apps & Books > Applications > List View and click Add Application on the Internal tab.
bBrowse to the Horizon Client app that you downloaded and click Save to upload the application to
AirWatch.
cOn the Info tab, type an application name and specify the supported mobile device models.
dOn the Assignment tab, assign the Horizon Client application to the user group that you created.
eOn the Deployment tab, set Application uses AirWatch SDK to Yes and select the SDK prole that
you created from the SDK drop-down menu.
fPublish the Horizon Client application.
6Install and set up the AirWatch Agent on each device.
You can download the AirWatch Agent from the Google Play Store or Amazon Appstore for Android.
7Use the AirWatch console to install the Horizon Client application on the devices.
You cannot install the Horizon Client application before the eective date on the Deployment tab.
AirWatch delivers Horizon Client to the devices in the user group that you associated with the
Horizon Client application.
When a user launches Horizon Client, Horizon Client communicates with the AirWatch Agent on the
device. If you congured a default list of Connection Server instances, AirWatch pushes the server
information to the AirWatch Agent on the device and shortcuts for those servers appear in Horizon Client.
What to do next
You can use the AirWatch console to edit the Horizon Client application and push those changes to devices.
For example, you can add a default Connection Server instance to the server list for the Horizon Client
application.
Configure AirWatch to Deliver Horizon Client to Android for Work
Devices
You can congure AirWatch to deliver Horizon Client to Android for Work device users.
Use this procedure only if your environment is set up for Android for Work. If your environment is not set
up for Android for Work, see “Congure AirWatch to Deliver Horizon Client to Android Devices,” on
page 19.
Prerequisites
Verify that your AirWatch environment is integrated with Android for Work. See the AirWatch
n
documentation or online help.
Install and deploy AirWatch. You must install AirWatch Server v8.0 FP02 or later and AirWatch Agent
n
v4.2 or later. See hp://www.air-watch.com. You can download AirWatch Agent from Google Play Store
or Amazon Appstore for Android.
Become familiar with the AirWatch console. This procedure assumes that you know how to use the
n
AirWatch console. See the AirWatch documentation or online help.
Verify that you have a corporate Google account. You must have a corporate Google account to enroll
n
Android for Work devices. For information about the enrollment process, see the AirWatch
documentation or online help.
20 VMware, Inc.
Loading...
+ 44 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.