VMware Horizon Client 4.6 Installation Manual

VMware Horizon Client for iOS
Installation and Setup Guide
Modified on 21 SEP 2017
VMware Horizon Client for iOS 4.6
VMware Horizon Client for iOS Installation and Setup Guide
You can find the most up-to-date technical documentation on the VMware Web site at:
hps://docs.vmware.com/
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2010–2017 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com
2 VMware, Inc.

Contents

VMware Horizon Client for iOS Installation and Setup Guide 5
Setup and Installation 7
1
System Requirements 7
System Requirements for iOS Clients 7
System Requirements for Real-Time Audio-Video 8
Smart Card Authentication Requirements 8
Congure Smart Card Authentication 9
Touch ID Authentication Requirements 10
Supported Desktop Operating Systems 11
Preparing Connection Server for Horizon Client 11
Installing Horizon Client 12
Install or Upgrade Horizon Client on an iOS Device 12
Congure AirWatch to Deliver Horizon Client to iOS Devices 13
Using Embedded RSA SecurID Software Tokens 15
Congure Advanced TLS/SSL Options 16
Congure VMware Blast Options 16
Congure the Horizon Client Default View 17
Horizon Client Data Collected by VMware 18
Using URIs to Congure Horizon Client 21
2
Syntax for Creating vmware-view URIs 21
Examples of vmware-view URIs 23
VMware, Inc.
Managing Remote Desktop and Application Connections 27
3
Seing the Certicate Checking Mode in Horizon Client 27
Connect to a Remote Desktop or Application 28
Manage Saved Servers 30
Select a Favorite Remote Desktop or Application 31
Disconnecting From a Remote Desktop or Application 31
Log O From a Remote Desktop 32
Manage Desktop and Application Shortcuts 32
Using 3D Touch with Horizon Client 32
Using Spotlight Search with Horizon Client 33
Using Split View and Slide Over with Horizon Client 34
Using the iPad Split Keyboard with Horizon Client 34
Using the Horizon Client Widget 34
Using a Microsoft Windows Desktop or Application 35
4
Feature Support Matrix for iOS 36
Using the Unity Touch Sidebar with a Remote Desktop 38
3
VMware Horizon Client for iOS Installation and Setup Guide
Using the Unity Touch Sidebar with a Remote Application 40
Horizon Client Tools on a Mobile Device 41
Gestures 43
Using Native Operating System Gestures with Touch Redirection 44
Screen Resolutions and Using External Displays 45
External Keyboards and Input Devices 46
Enable the Japanese 106/109 Keyboard Layout 46
Enable a Swiftpoint GT Mouse in Horizon Client 47
Using the Real-Time Audio-Video Feature for Microphones 47
Congure Horizon Client to Support Reversed Mouse Buons 48
Copying and Pasting Text and Images 48
Saving Documents in a Remote Application 49
Multitasking 49
Suppress the Cellular Data Warning Message 49
PCoIP Client-Side Image Cache 49
Internationalization 50
Troubleshooting Horizon Client 51
5
Restart a Remote Desktop 51
Reset a Remote Desktop or Remote Applications 52
Collecting and Sending Logging Information to VMware 53
Enable Horizon Client Log Collection 53
Manually Retrieve and Send Horizon Client Log Files 53
Disable Horizon Client Log Collection 54
Report Horizon Client Crash Data to VMware 54
Horizon Client Stops Responding or the Remote Desktop Freezes 55
Problem Establishing a Connection When Using a Proxy 55
Connecting to a Server in Workspace ONE Mode 55
Index 57
4 VMware, Inc.

VMware Horizon Client for iOS Installation and Setup Guide

This document, VMware Horizon Client for iOS Installation and Setup Guide, provides information about installing, conguring, and using VMware Horizon® Client™ software on an iOS device.
This information is intended for administrators who need to set up a Horizon deployment that includes iOS client devices. The information is wrien for experienced system administrators who are familiar with virtual machine technology and datacenter operations.
VMware, Inc. 5
VMware Horizon Client for iOS Installation and Setup Guide
6 VMware, Inc.

Setup and Installation 1

Seing up a Horizon deployment for iOS clients involves using certain Connection Server conguration seings, meeting the system requirements for Horizon servers and iOS clients, and installing the app for
Horizon Client.
This chapter includes the following topics:
“System Requirements,” on page 7
n
“Preparing Connection Server for Horizon Client,” on page 11
n
“Installing Horizon Client,” on page 12
n
“Using Embedded RSA SecurID Software Tokens,” on page 15
n
“Congure Advanced TLS/SSL Options,” on page 16
n
“Congure VMware Blast Options,” on page 16
n
“Congure the Horizon Client Default View,” on page 17
n
“Horizon Client Data Collected by VMware,” on page 18
n

System Requirements

iOS devices that run Horizon Client must meet certain hardware and software requirements.

System Requirements for iOS Clients

The iOS device on which you install Horizon Client, and the peripherals it uses, must meet certain system requirements.
Operating systems
(Optional) External keyboards
Smart card authentication
Touch ID authentication
Connection Server, security server, and View Agent or Horizon Agent
VMware, Inc. 7
iOS 8.4.1 and later, including iOS 9.x and iOS 10.x.
iPad Keyboard Dock and Apple Wireless Keyboard (Bluetooth).
See “Smart Card Authentication Requirements,” on page 8.
See “Touch ID Authentication Requirements,” on page 10.
Latest maintenance release of Horizon 6 version 6.x and later releases.
VMware Horizon Client for iOS Installation and Setup Guide
VMware recommends that you use a security server or Unied Access Gateway appliance so that client devices do not require a VPN connection. If your company has an internal wireless network to provide routable access to remote desktops that devices can use, you do not have to set up a security server, Unied Access Gateway, or VPN connection.
Display protocols
Network protocols
PCoIP
n
VMware Blast (requires Horizon Agent 7.0 or later)
n
IPv4
n
IPv6 (requires iOS 9.2 or later)
n
For information about using Horizon in an IPv6 environment, see the View Installation document.

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 environment must meet certain software and hardware requirements.
I Only the audio-in feature is supported. The video feature is not supported.
Remote desktops and applications
Client access device
To use Real-Time Audio-Video with published desktops and remote applications, you must have Horizon Agent 7.0.2 or later.
Real-Time Audio-Video is supported on all iOS devices that run Horizon Client for iOS. For more information, see “System Requirements for
iOS Clients,” on page 7.

Smart Card Authentication Requirements

Client systems that use a smart card for user authentication must meet certain requirements.
Client Hardware and Software Requirements
An iOS 8.4.1 or later operating system is required.
Each client system that uses a smart card for user authentication must have the following hardware and software:
Horizon Client
n
A compatible smart card reader
n
Product-specic application drivers
n
Users that authenticate with smart cards must have a smart card and each smart card must contain a user
certicate.
Remote Desktop and Application Software Requirements
A Horizon administrator must install product-specic application drivers on the remote desktops or RDS host.
8 VMware, Inc.
Chapter 1 Setup and Installation
Horizon Client for iOS supports using smart cards with remote desktops that have Windows 7, Windows Vista, Windows XP, Windows 8.1, Windows 10, and Windows Server 2008 R2 guest operating systems. For published desktops and remote applications, the Windows Server 2008 R2 and Windows Server 2012 R2 operating systems are supported.
Enabling the Username Hint Field in Horizon Client
In some environments, smart card users can use a single smart card certicate to authenticate to multiple user accounts. Users enter their user name in the Username hint eld during smart card sign-in.
To make the Username hint eld 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 Unied Access Gateway appliance rather than a security server for secure external access, you must congure the Unied Access Gateway appliance to support the smart card user name hints feature. The smart card user name hints feature is supported only with Unied Access Gateway
2.7.2 and later. For information about enabling the smart card user name hints feature in Unied Access Gateway, see the Deploying and Conguring Unied Access Gateway document.
N Horizon Client still supports single-account smart card certicates when the smart card user name hints feature is enabled.
Additional Smart Card Authentication Requirements
In addition to meeting the smart card requirements for Horizon Client systems, other Horizon components must meet certain conguration requirements to support smart cards.
Connection Server and security server hosts
Active Directory
An administrator must add all applicable Certicate Authority (CA) certicates for all trusted user certicates to a server truststore le on the Connection Server host or security server host. These certicates include root certicates and must include intermediate certicates if the user's smart card certicate was issued by an intermediate certicate authority.
For information about conguring Connection Server to support smart card use, see the View Administration document.
For information about tasks that an administrator might need to perform in Active Directory to implement smart card authentication, see the View Administration document.

Configure Smart Card Authentication

Smart card conguration tasks include connecting and pairing the card reader with the device and seing the smart card removal policy.
Prerequisites
Verify that the client device, remote desktops, RDS hosts, Connection Server host, and other Horizon components meet the smart card authentication requirements. See “Smart Card Authentication
Requirements,” on page 8.
VMware, Inc. 9
VMware Horizon Client for iOS Installation and Setup Guide
Procedure
1 Pair the device with the smart card reader, according to the documentation provided by the
manufacturer of the reader.
If your iOS device has a 30-pin connector, you can plug the smart card reader into the connector. For iPad Air and iPhone 5S, which have Lightning interfaces, you must use a 30-pin adapter to plug the smart card reader into the device's 30-pin connector.
2 Congure the smart card removal policy.
Option Description
Set the policy on the Connection Server instance
Set the policy on the remote desktop
When you set the policy on the Connection Server instance, you can disconnect users from the Connection Server instance when they remove their smart cards, or keep users connected to Connection Server when they remove their smart cards and let them start new desktop or application sessions without reauthenticating.
a In Horizon Administrator, select View  > Servers.
b On the Connection Servers tab, select the Connection Server instance
and click Edit.
c On the Authentication tab, select or deselect the Disconnect user
sessions on smart card removal check box to congure the smart card removal policy.
d Click OK to save your changes.
e Restart the Connection Server service to make your changes take eect.
If you select the Disconnect user sessions on smart card removal check box, Horizon Client returns to the Recent window when users remove their smart cards.
When you set the policy on the remote desktop, you can use the Group Policy Editor (gpedit.msc) to congure one of the following seings: no action, lock workstation, force log o, or Disconnect if a Remote Desktop Services session.
a
Open gpedit.msc in the desktop operating system.
b Navigate to Windows  > Security  > Local policies >
Security options > Interactive logon: smart card removal behavior.
c
Run the gpupdate /force command after you change the conguration to force a group policy refresh.

Touch ID Authentication Requirements

To use Touch ID for user authentication in Horizon Client, you must meet certain requirements.
iPad and iPhone models
Operating system requirements
Connection Server requirements
10 VMware, Inc.
Any iPad or iPhone model that supports Touch ID, for example, iPad Air 2 and iPhone 6.
iOS 8 or later.
n
Add at least one ngerprint in the Touch ID & Passcode seing.
n
Horizon 6 version 6.2 or a later release.
n
Enable biometric authentication in Connection Server. For information,
n
see "Congure Biometric Authentication" in the View Administration document.
Chapter 1 Setup and Installation
The Connection Server instance must present a valid root-signed
n
certicate to Horizon Client.
Horizon Client requirements
Set the certicate checking mode to Never connect to untrusted servers
n
or Warn before connecting to untrusted servers. For information about seing the certicate checking mode, see “Seing the Certicate
Checking Mode in Horizon Client,” on page 27.
Enable Touch ID by tapping Enable Touch ID on the server login
n
window. After you successfully log in, your Active Directory credentials are stored securely in the iOS device's Keychain. The Enable Touch ID option is shown the rst time you log in and does not appear after Touch ID is enabled.
You can use Touch ID with smart card authentication and as part of two-factor authentication with RSA SecurID and RADIUS authentication. If you use Touch ID with smart card authentication, Horizon Client connects to the server after you enter your PIN and the Touch ID login window does not appear.

Supported Desktop Operating Systems

A Horizon administrator creates virtual machines that have a guest operating system and installs 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, conguring Linux virtual machines for use in Horizon, and a list of supported features, see Seing Up Horizon 6 for Linux Desktops or Seing Up Horizon 7 for Linux Desktops.

Preparing Connection Server for Horizon Client

A Horizon administrator must perform specic tasks to enable end users to connect to remote desktops and applications.
Before end users can connect to a Connection Server instance or a security server and access a remote desktop or application, a Horizon administrator must congure certain pool seings and security seings:
If you plan to use Unied Access Gateway, congure Connection Server to work with
n
Unied Access Gateway. See the Deploying and Conguring Unied Access Gateway document. Unied Access Gateway appliances fulll 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 6.x and Security Server 6.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
congured 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 Seings 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 Seing Up Virtual Desktops in Horizon 7 or Seing Up Published Desktops and Applications in Horizon 7 document.
VMware, Inc. 11
VMware Horizon Client for iOS Installation and Setup Guide
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 two­factor 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 seings in Horizon Administrator. These global seings are available in Horizon 7
version 7.1 and later. For information about conguring global seings, see the View Administration document.
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 seings 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 use Touch ID authentication, you must enable biometric authentication in Connection Server.
n
Biometric authentication is supported in Horizon 6 version 6.2 and later. For more information, see 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, congure Horizon LDAP for this feature on the Connection Server host.
Users can save their passwords if Horizon LDAP is congured to allow it, if the Horizon Client
certicate verication 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 certicate 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 Seing Up Virtual Desktops in Horizon 7 and Seing Up Published Desktops and Applications in Horizon 7 documents.

Installing Horizon Client

You can install Horizon Client the same way that you install other iOS apps. You can also congure AirWatch to deliver Horizon Client to end users.

Install or Upgrade Horizon Client on an iOS Device

You can install Horizon Client from the VMware Downloads page or from the App Store.
Prerequisites
If you have not already set up the iOS device, do so. For information, see the user guide from Apple.
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 hp://www.vmware.com/go/viewclients, or it might be the URL for a Connection Server instance.
Procedure
1 On the iOS device, Mac, or PC, browse to the URL for downloading the installer le, or search the App
Store for the Horizon Client app.
2 Download the app.
12 VMware, Inc.
Chapter 1 Setup and Installation
3 If you downloaded the app to a Mac or PC, connect the iOS device to the computer and follow the
onscreen instructions in iTunes.
4 To determine whether the installation succeeded, verify that the Horizon app icon appears on the iOS
device.

Configure AirWatch to Deliver Horizon Client to iOS Devices

You can congure AirWatch to deliver Horizon Client to iOS 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.
Prerequisites
Install and deploy AirWatch. See hp://www.air-watch.com.
n
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.
Procedure
1 Log in to the AirWatch console as an administrator.
2 Select Accounts > Users > List View, click Add User, and add user accounts for the users who will run
Horizon Client on their mobile devices.
3 Select Accounts > Users > User Groups, click Add, and create a user group for the user accounts that
you created.
4 Upload and add the Horizon Client application to AirWatch.
a Select Apps & Books > Applications > List View and click Add Application on the Public tab.
b Search for and select VMware Horizon Client for Apple iOS in the App Store.
c On the Info tab, type an application name and specify the supported iOS device models.
d On the Assignment tab, assign the Horizon Client application to the user group that you created.
VMware, Inc. 13
VMware Horizon Client for iOS Installation and Setup Guide
e (Optional) Congure one or more default servers.
The servers that you specify appear as shortcuts in VMware Horizon Client.
N This feature is supported only for iOS 7 and later devices. You cannot push a default Connection Server list to an iOS 6 device.
Option Description
Configure server, user name, and domain information
Configure server information only
f Publish the Horizon Client application.
On the Deployment tab, select a push mode, select the Send
Application  check box, enter broker_list in the  Key text box, select String from the Value Type drop- down menu, and enter a list of default servers in the 
Value text box in JSON format.
Use the server property to specify the IP address or host name of the server, the username and domain properties to specify the name and domain of a user that is entitled to the server, and the description property to specify a description of the server.
The following example species four default servers.
{"settings":{ "server-list":[ {"server":"123.456.1.1","description":"View server 1"}, {"server":"123.456.1.2","description":"View server 2"}, {"server":"123.456.1.3","description":"View server 3"}, {"server":"viewserver4.mydomain.com","description":"View server 4","username":"vmware","domain":"view"} ]}}
On the Deployment tab, select a push mode, select the Send Application  check box, enter servers in the
 Key text box, select String from the Value Type drop- down menu, and enter the IP address or host name of a server in the  Value text box. servers is case sensitive.
To specify a list of servers, enter multiple IP addresses or host names, separated by commas, in the  Value text box.
The following example species three default servers.
123.456.1.1, viewserver4.mydomain.com, 123.456.1.2
5 Install and set up the AirWatch MDM Agent on each iOS device.
You can download the AirWatch MDM Agent from iTunes.
6 Use the AirWatch console to install the Horizon Client application on the mobile devices.
You cannot install the Horizon Client application before the eective date on the Deployment tab.
AirWatch delivers Horizon Client to the iOS 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 MDM Agent on the device. If you congured a default list of Connection Server instances, AirWatch pushes the server information to the AirWatch MDM 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 iOS devices. For example, you can add a default Connection Server instance to the server list for the Horizon Client application.
14 VMware, Inc.

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 their PIN and a 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 a Connection Server instance 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 prexes are supported for end users that copy and paste the URL into Horizon Client when Horizon Client is connected to an RSA-enabled Connection Server instance:
viewclient-securid://
n
com.rsa.securid.iphone://
n
Chapter 1 Setup and Installation
com.rsa.securid://
n
For end users who will be installing the token by tapping the URL, only the viewclient-securid:// prex is supported.
For information about using dynamic seed provisioning or le-based (CTF) provisioning, see the Web page
RSA SecurID Software Token for iPhone Devices at hp://www.rsa.com/node.aspx?id=3652 or RSA SecurID Software Token for Android at hp://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 formaing 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.
VMware, Inc. 15
VMware Horizon Client for iOS Installation and Setup Guide

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 congure 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 conguring the security protocols that are accepted by Connection Server instances, see the View Security document.
Procedure
1 Tap  at the boom of the Horizon Client window.
2 Tap Advanced SSL Options.
3 Make sure that the Reset to Default  option is set to o.
4 To enable or disable a security protocol, tap the On or  toggle next to the security protocol name.
5 To change the cipher control string, replace the default string.
6 (Optional) If you need to revert to the default seings, tap Reset in the upper right corner of the
window.
Your changes take eect the next time you connect to the server.

Configure VMware Blast Options

You can congure H.264 decoding and network condition options for remote desktop and application sessions that use the VMware Blast display protocol.
You can congure H.264 decoding before or after you connect to a server.
You can change the network condition to any type before you connect to a server. After you connect to a server, you can switch the network condition between Typical and Excellent (you cannot select Poor), but only if Typical or Excellent was selected before you connected to the server. You cannot change the network condition after you connect to a server if Poor was selected before you connected.
After you connect to a server, the VMware Blast seing is visible only if VMware Blast is the preferred protocol.
Prerequisites
To use this feature, Horizon Agent 7.0 or later must be installed.
Procedure
1 Tap  at the boom of the Horizon Client window and tap VMware Blast.
If you are logged in to a server, the VMware Blast seing is visible only if VMware Blast is the preferred protocol.
16 VMware, Inc.
2 Congure the decoding and network condition options.
Option Action
H.264
Network Condition
Congure this option to allow H.264 decoding in Horizon Client.
When this option is selected (the default seing), 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.
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 seing.
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. Unied 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.
Chapter 1 Setup and Installation
Changes take eect the next time a user connects to a remote desktop or application and selects the VMware Blast display protocol. Your changes do not aect existing VMware Blast sessions.

Configure the Horizon Client Default View

You can congure whether recently used desktops and applications or server shortcuts appear when you launch Horizon Client.
Procedure
1 Tap  at the boom of the Horizon Client window.
2 Tap Default View.
3 Tap an option to select the default view.
Option Description
Recent
Servers
The default view you selected takes eect immediately.
The Recent window appears when you launch Horizon Client. The Recent window contains shortcuts to recently used desktops and applications. This is the default seing.
The Servers window appears when you launch Horizon Client. The Servers window contains shortcuts to the servers that you added to Horizon Client.
VMware, Inc. 17
VMware Horizon Client for iOS Installation and Setup Guide

Horizon Client Data Collected by VMware

If your company participates in the customer experience improvement program, VMware collects data from certain Horizon Client elds. Fields that contain sensitive information are anonymous.
VMware collects data on client systems to prioritize hardware and software compatibility. If your company's administrator has opted to participate in the customer experience improvement program, VMware collects anonymous data about your deployment to respond beer to customer requirements. VMware does not collect data that identies your organization. Horizon Client information is sent rst to the Connection Server instance and then to VMware, with data from Connection Server, desktop pools, and remote desktops.
Although the information is encrypted while in transit to the Connection Server instance, the information on the client system is logged unencrypted in a user-specic directory. The logs do not contain any personally identiable information.
The administrator who installs Connection Server can select whether to participate in the VMware customer experience improvement program while running the Connection Server installation wizard, or an administrator can set an option in Horizon Administrator after the installation.
Table 11. Data Collected from Horizon Clients for the Customer Experience Improvement Program
Is This Field Made Anonymous
Description
Company that produced the Horizon Client application
Product name No VMware Horizon Client
Client product version No (The format is x.x.x-yyyyyy, where x.x.x is the client version
Client binary architecture No Examples include the following:
Client build name No Examples include the following:
Host operating system No Examples include the following:
? Example Value
No VMware
number and yyyyyy is the build number.)
n
n
n
n
n
n
n
n
n
n
n
n
n
n
i386
x86_64
arm
VMware-Horizon-Client-Win32-Windows
VMware-Horizon-Client-Linux
VMware-Horizon-Client-iOS
VMware-Horizon-Client-Mac
VMware-Horizon-Client-Android
VMware-Horizon-Client-WinStore
Windows 8.1
Windows 7, 64-bit Service Pack 1 (Build 7601 )
iPhone OS 5.1.1 (9B206)
Ubuntu 12.04.4 LTS
Mac OS X 10.8.5 (12F45)
18 VMware, Inc.
Loading...
+ 40 hidden pages