Installation and Setup Guide

n
Does the common name on the certicate match the host name of the server that sends it? A mismatch
can occur if a load balancer redirects Horizon Client to a server that has a certicate that does not match
the host name entered in Horizon Client. Another reason a mismatch can occur is if you enter an IP
address rather than a host name in the client.
n
Is the certicate signed by an unknown or untrusted certicate authority (CA)? Self-signed certicates
are one type of untrusted CA.
To pass this check, the certicate's chain of trust must be rooted in the device's local certicate store.
I For information about distributing a self-signed root certicate that users can install on their
Android devices, as well as instructions for installing a certicate on an Android device, see the
documentation on the Google Web site, such as the Android 3.0 User's Guide.
To set the certicate checking mode, start Horizon Client and open . In , tap Security
options and tap Security mode. You have three choices:
n
Never connect to untrusted servers. If any of the certicate checks fails, the client cannot connect to the
server. An error message lists the checks that failed.
n
Warn before connecting to untrusted servers. If a certicate check fails because the server uses a self-
signed certicate, you can click Continue to ignore the warning. For self-signed certicates, the
certicate name is not required to match the server name you entered in Horizon Client.
n
Do not verify server identity . This seing means that no certicate checking occurs.
If the certicate checking mode is set to Warn, you can still connect to a server that uses a self-signed
certicate.
If an administrator later installs a security certicate from a trusted certicate authority, so that all certicate
checks pass when you connect, this trusted connection is remembered for that specic server. In the future,
if that server ever presents a self-signed certicate again, the connection fails. After a particular server
presents a fully veriable certicate, it must always do so.
Connect to a Remote Desktop or Application
To connect to a remote desktop or application, you must provide the name of a server and supply
credentials for your user account.
Before you have end users access their remote desktops and applications, test that you can connect to a
remote desktop or application from a client device. You might need to specify a server and supply
credentials for your user account.
Prerequisites
n
Obtain login credentials, such as a user name and password, RSA SecurID user name and passcode,
RADIUS authentication user name and passcode, or smart card personal identication number (PIN).
n
Obtain the NETBIOS domain name for logging in. For example, you might use mycompany rather than
mycompany.com.
n
Perform the administrative tasks described in “Preparing Connection Server for Horizon Client,” on
page 12.
n
If you are outside the corporate network and require a VPN connection to access remote desktops and
applications, verify that the client device is set up to use a VPN connection and turn on that connection.
n
Verify that you have the fully qualied domain name (FQDN) of the server that provides access to the
remote desktop or application. Underscores (_) are not supported in server names. If the port is not 443,
you also need the port number.
VMware Horizon Client for Android Installation and Setup Guide
34 VMware, Inc.