VMware Horizon Client 4.2 User Guide

Using VMware Horizon Client for Linux
Horizon Client 4.2
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-002225-00
Using VMware Horizon Client for Linux
You can find the most up-to-date technical documentation on the VMware Web site at:
hp://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:
docfeedback@vmware.com
Copyright © 2012–2016 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com

Contents

Using VMware Horizon Client for Linux 5
System Requirements and Installation 7
1
System Requirements for Linux Client Systems 8
System Requirements for Real-Time Audio-Video 9
Requirements for Multimedia Redirection (MMR) 11
Requirements for Using Flash URL Redirection 12
Smart Card Authentication Requirements 12
Supported Desktop Operating Systems 14
Preparing Connection Server for Horizon Client 14
Installation Options 14
Install or Upgrade Horizon Client for Linux from VMware Product Downloads 15
Install Horizon Client for Linux from the Ubuntu Software Center 20
Congure VMware Blast Options 21
Horizon Client Data Collected by VMware 22
Conguring Horizon Client for End Users 25
2
Common Conguration Seings 25
Using the Horizon Client Command-Line Interface and Conguration Files 26
Using URIs to Congure Horizon Client 35
Conguring Certicate Checking for End Users 38
Conguring Advanced TLS/SSL Options 39
Conguring Specic Keys and Key Combinations to Send to the Local System 40
Using FreeRDP for RDP Connections 41
Enabling FIPS Mode 43
Conguring the PCoIP Client-Side Image Cache 44
VMware, Inc.
Managing Remote Desktop and Application Connections 47
3
Connect to a Remote Desktop or Application 47
Share Access to Local Folders and Drives 49
Seing the Certicate Checking Mode for Horizon Client 51
Switch Desktops or Applications 52
Log O or Disconnect 52
Using a Microsoft Windows Desktop or Application on a Linux System 55
4
Feature Support Matrix for Linux 55
Internationalization 58
Keyboards and Monitors 59
Connect USB Devices 60
Using the Real-Time Audio-Video Feature for Webcams and Microphones 62
Saving Documents in a Remote Application 66
3
Using VMware Horizon Client for Linux
Set Printing Preferences for the Virtual Printer Feature on a Remote Desktop 66
Copying and Pasting Text 67
Troubleshooting Horizon Client 69
5
Problems with Keyboard Input 69
Reset a Remote Desktop or Application 69
Uninstall Horizon Client for Linux 70
Conguring USB Redirection on the Client 71
6
System Requirements for USB Redirection 71
USB-Specic Log Files 72
Seing USB Conguration Properties 72
USB Device Families 75
Index 77
4 VMware, Inc.

Using VMware Horizon Client for Linux

This guide, Using VMware Horizon Client for Linux, provides information about installing and using VMware Horizon® Client™ software on a Linux client system to connect to a View desktop in the datacenter.
The information in this document includes system requirements and instructions for installing and using Horizon Client for Linux.
This information is intended for administrators who need to set up a View deployment that includes Linux client systems. The information is wrien for experienced system administrators who are familiar with virtual machine technology and datacenter operations.
N This document pertains mostly to the Horizon Client for Linux that VMware makes available. In addition, several VMware partners oer thin and zero client devices for View deployments. The features that are available for each thin or zero client device, and the operating systems supported, are determined by the vendor, the model, and the conguration that an enterprise chooses to use. For information about the vendors and models for these client devices, see the VMware Compatibility Guide, available on the VMware Web site.
VMware, Inc.
5
Using VMware Horizon Client for Linux
System Requirements and
Installation 1
Client systems must meet certain hardware and software requirements. The process of installing Horizon Client is like installing most other applications.
This chapter includes the following topics:
“System Requirements for Linux Client Systems,” on page 8
n
“System Requirements for Real-Time Audio-Video,” on page 9
n
“Requirements for Multimedia Redirection (MMR),” on page 11
n
“Requirements for Using Flash URL Redirection,” on page 12
n
“Smart Card Authentication Requirements,” on page 12
n
“Supported Desktop Operating Systems,” on page 14
n
“Preparing Connection Server for Horizon Client,” on page 14
n
“Installation Options,” on page 14
n
“Install or Upgrade Horizon Client for Linux from VMware Product Downloads,” on page 15
n
“Install Horizon Client for Linux from the Ubuntu Software Center,” on page 20
n
“Congure VMware Blast Options,” on page 21
n
“Horizon Client Data Collected by VMware,” on page 22
n
VMware, Inc.
7
Using VMware Horizon Client for Linux

System Requirements for Linux Client Systems

The Linux PC or laptop on which you install Horizon Client, and the peripherals it uses, must meet certain system requirements.
N These system requirements pertain to the Horizon Client for Linux that VMware makes available. In addition, several VMware partners oer thin and zero client devices for View deployments. The features that are available for each thin or zero client device, and the operating systems supported, are determined by the vendor and model and the conguration that an enterprise chooses to use. For information about the vendors and models for these client devices, see the VMware Compatibility Guide, available on the VMware Web site.
N
Starting with version 7.0, View Agent is renamed Horizon Agent.
n
VMware Blast, the display protocol that is available starting with Horizon Client 4.0 and Horizon Agent
n
7.0, is also known as VMware Blast Extreme.
Architecture
Memory
Operating system
OpenSSL requirement
View Connection Server, Security Server, and View Agent or Horizon Agent
i386, x86_64, ARM
At least 2GB of RAM
Operating System Version
Ubuntu 12.04, 14.04
Ubuntu 64-bit 12.04, 14.04
Red Hat Enterprise Linux (RHEL) 6.8
Red Hat Enterprise Linux (RHEL) 64-bit 6.8, 7.2
SUSE Linux Enterprise Desktop (SLED) 11 SP4
CentOS 6.8
Horizon Client requires a specic version of OpenSSL. The correct version is automatically downloaded and installed.
Latest maintenance release of View 5.3.x and later releases
If client systems connect from outside the corporate rewall, VMware recommends that you use a security server. With a security server, client systems will not require a VPN connection.
Remote (hosted) applications are available only on Horizon 6.0 (or later) View servers.
Display protocol
Screen resolution on
VMware Blast (requires Horizon Agent 7.0 or later)
n
PCoIP
n
RDP
n
Minimum: 1024 X 768 pixels
the client system
Hardware requirements for VMware Blast and
x86- or x64-based processor with SSE2 extensions, with a 800MHz or
n
higher processor speed.
PCoIP
Chapter 1 System Requirements and Installation
Available RAM above system requirements to support various monitor
n
setups. Use the following formula as a general guide:
20MB + (24 * (# monitors) * (monitor width) * (monitor height))
As a rough guide, you can use the following calculations:
1 monitor: 1600 x 1200: 64MB 2 monitors: 1600 x 1200: 128MB 3 monitors: 1600 x 1200: 256MB
Hardware requirements for RDP
Software requirements for Microsoft RDP
Software requirements for FreeRDP
Other software requirements
x86- or x64-based processor with SSE2 extensions, with a 800MHz or
n
higher processor speed.
128MB RAM.
n
For Ubuntu 12.04, use rdesktop 1.7.0.
If you plan to use an RDP connection to View desktops and you would prefer to use a FreeRDP client for the connection, you must install the correct version of FreeRDP and any applicable patches. See “Install and Congure
FreeRDP,” on page 43.
Horizon Client also has certain other software requirements, depending on the Linux distribution you use. Be sure to allow the Horizon Client installation wizard to scan your system for library compatibilities and dependencies. The following list of requirements pertains only to Ubuntu distributions.
libudev0
n
N Beginning with Horizon Client 4.2, libudev0 is required to launch Horizon Client. By default, libudev0 is not installed in Ubuntu
14.04.
To support idle session timeouts: libXsso.so.1.
n
To support Flash URL redirection: libexpat.so.1. (The libexpat.so.0
n
le is no longer required.)
To improve performance when using multiple monitors, enable
n
Xinerama.

System Requirements for Real-Time Audio-Video

Real-Time Audio-Video works with standard webcam, USB audio, and analog audio devices, and with standard conferencing applications like Skype, WebEx, and Google Hangouts. To support Real-Time Audio­Video, your View deployment must meet certain software and hardware requirements.
View remote desktop
VMware, Inc. 9
The desktops must have View Agent 5.2 or later, or Horizon Agent 7.0 or later, installed. For View Agent 5.2 desktops, the desktops must also have the corresponding Remote Experience Agent installed. For example, if View Agent 5.2 is installed, you must also install the Remote Experience Agent from View 5.2 Feature Pack 2. See the View Feature Pack Installation and
Using VMware Horizon Client for Linux
Administration document for View. If you have View Agent 6.0 or later, or Horizon Agent 7.0 or later, no feature pack is required. To use Real-Time Audio-Video with RDS desktops and remote applications, you must have Horizon Agent 7.0.2 or later.
Horizon Client computer or client access device
Real-Time Audio-Video is supported on x86 and x64 devices. This
n
feature is not supported on ARM processors. The client system must meet the following minimum hardware requirements.
Required
Resolution Frame Rate CPU
320 x 240 15 FPS 2 core, 1800
640 x 480 15 FPS 2 core, 2700
1280 x 720 15 FPS 4 core, 3400
Horizon Client requires the following libraries:
n
Video4Linux2
n
libv4l
n
Pulse Audio
n
MHz
MHz
MHz
Memory
105 MB
150 MB
210 MB
The plug-in le (/usr/lib/pcoip/vchan_plugins/libviewMMDevRedir.so) has the following dependencies.:
libuuid.so.1 libv4l2.so.0 libspeex.so.1 libudev0 libtheoradec.so.1 libtheoraenc.so.1 libv4lconvert.so.0 libjpeg.so.8
All of these les must be present on the client system or the Real-Time Audio-Video feature will not work. Note that these dependencies are in addition to the dependencies required for Horizon Client itself.
The webcam and audio device drivers must be installed, and the
n
webcam and audio device must be operable, on the client computer. To support Real-Time Audio-Video, you do not have to install the device drivers on the desktop operating system where the agent is installed.
Display protocol for
PCoIP
n
View
VMware Blast (requires Horizon Agent 7.0 or later)
n
Real-Time Audio-Video is not supported in RDP desktop sessions.
10 VMware, Inc.

Requirements for Multimedia Redirection (MMR)

With multimedia redirection (MMR), the multimedia stream is processed, that is, decoded, on the client system. The client system plays the media content, thereby reducing the load on the ESXi host.
Chapter 1 System Requirements and Installation
View remote desktop
Horizon Client computer or client access device
Single-user desktops must have View Agent 6.0.2 or later, or
n
Horizon Agent 7.0 or later, installed.
Session-based desktops must have View Agent 6.1.1 or later, or
n
Horizon Agent 7.0 or later, installed on the RDS host.
For information about operating system requirements and other
n
software requirements and conguration seings for the remote desktop or application, see the topics about Windows Media Multimedia Redirection in Seing Up Desktop and Application Pools in View.
Because MMR ooads media processing from the server to the client, the client has the following minimum hardware requirements.
Processor: Intel Pentium 4 or AMD Athlon dual-core
Processor speed: 1.5 GHz for common case, or 1.8 GHz for Full HD
Memory: 2 GB RAM
Video adapter: Hardware accelerated
You must install one of the following libraries to avoid video playback issues:
GStreamer core library and gstreamer-mpeg 0.10
n
GStreamer core library and uendo 0.10
n
On SLED 11 SP4, if you encounter video playback issues such as a black screen, remove the library libvdpau.
On HP thin clients, you must remove the le /usr/lib/gstreamer-0.10/libgstfluvadec.so to avoid video playback issues such as a Horizon Client crash or a black screen.
On Dell Wyse thin clients, video playback might not work with the pre­installed uendo library. To resolve the problem, contact Dell support to obtain the latest uendo library.
Supported media formats
Media formats that are supported on Windows Media Player are supported. For example: M4V; MOV; MP4; WMP; MPEG-4 Part 2; WMV 7, 8, and 9; WMA; AVI; ACE; MP3; WAV.
N DRM-protected content is not redirected through Windows Media MMR.
MMR is not enabled by default. To enable it, you must set the conguration option view.enableMMR. For more information, see “Horizon Client Conguration Seings and Command-Line Options,” on page 27.
VMware, Inc. 11
Using VMware Horizon Client for Linux

Requirements for Using Flash URL Redirection

Streaming Flash content directly from Adobe Media Server to client endpoints lowers the load on the datacenter ESXi host, removes the extra routing through the datacenter, and reduces the bandwidth required to simultaneously stream live video events to multiple client endpoints.
The Flash URL redirection feature uses a JavaScript that is embedded inside a Web page by the Web page administrator. Whenever a virtual desktop user clicks on the designated URL link from within a Web page, the JavaScript intercepts and redirects the ShockWave File (SWF) from the virtual desktop session to the client endpoint. The endpoint then opens a local VMware Flash Projector outside of the virtual desktop session and plays the media stream locally. Both multicast and unicast are supported.
This feature is available when used in conjunction with the correct version of the agent software. For View
5.3, this feature is included in the Remote Experience Agent, which is part of the View Feature Pack. For View 6.0 and later releases, this feature is included in View Agent or Horizon Agent.
To use this feature, you must set up your Web page and your client devices. Client systems must meet certain software requirements:
This feature is supported for PCoIP only. This feature is not supported on ARM processors.
n
Client systems must have IP connectivity to the Adobe Web server that hosts the ShockWave File (SWF)
n
that initiates the multicast or unicast streaming. If needed, congure your rewall to open the appropriate ports to allow client devices to access this server.
Client systems must have the appropriate Flash plug-in installed.
n
a Install the libexpat.so.1 le, or verify that this le is already installed.
Ensure that the le is installed in the /usr/lib or /usr/local/lib directory.
b Install the libflashplayer.so le, or verify that this le is already installed.
Ensure that the le is installed in the appropriate Flash plug-in directory for your Linux operating system.
c Install the wget program, or verify that the program le is already installed.
libffi.so.5 is required on Ubuntu 14.04 to make Flash URL redirection work, but Ubuntu 14.04 has
n
only libffi.so.6 by default. You can work around this limitation by making a symbolic link between
libffi.so.6 and libffi.so.5.
For a list of the remote desktop requirements for Flash URL redirection, and for instructions about how to congure a Web page to provide a multicast or unicast stream, see the View documentation.

Smart Card Authentication Requirements

Client systems that use a smart card for user authentication must meet certain requirements.
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
Product-specic application drivers
n
You must also install product-specic application drivers on the remote desktops or Microsoft RDS host.
Users that authenticate with smart cards must have a smart card, and each smart card must contain a user
certicate.
12 VMware, Inc.
Chapter 1 System Requirements and Installation
In addition to meeting these requirements for Horizon Client systems, other View components must meet certain conguration requirements to support smart cards:
For information about conguring Connection Server to support smart card use, see "Seing Up Smart
n
Card Authentication" in the View Administration document.
You 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 tasks you might need to perform in Active Directory to implement smart card
n
authentication, see "Seing Up Smart Card Authentication" in the View Administration document.
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 View 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 "Seing Up Smart Card Authentication" in the View Administration document.
If your environment uses an Access Point appliance rather than a security server for secure external access, you must congure the Access Point appliance to support the smart card user name hints feature. The smart card user name hints feature is supported only with Access Point 2.7.2 and later. For information about enabling the smart card user name hints feature in Access Point, see the Deploying and Conguring Access Point document.
N Horizon Client still supports single-account smart card certicates when the smart card user name hints feature is enabled.

Configure Horizon Client for Smart Card Authentication

You must perform certain conguration steps to use a smart card in Horizon Client.
Prerequisites
Install Horizon Client.
n
(Optional) To make the Username hint eld appear in the Horizon Client login dialog box, enable the
n
smart card user name hints feature in Connection Server. For more information, see "Seing Up Smart Card Authentication" in the View Administration document.
Procedure
1 Create the folder /usr/lib/vmware/view/pkcs11.
2 Create a symbol link to the pkcs11 library, which is used for smart card authentication.
For example, run the following command:
sudo ln -s /usr/lib/pkcs11/libgtop11dotnet.so /usr/lib/vmware/view/pkcs11
VMware, Inc. 13
Using VMware Horizon Client for Linux

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 "Supported Operating Systems for View Agent" topic in the View 5.x or 6.x installation documentation. See the "Supported Operating Systems for Horizon Agent" topic in the Horizon 7 installation documentation.
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 6 or Horizon 7, and a list of supported features, see Seing Up Horizon 6 for Linux
Desktops, which is part of the Horizon 6, version 6.1 documentation, or see Seing Up Horizon 7 for Linux Desktops.

Preparing Connection Server for Horizon Client

Administrators must perform specic 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 congure certain pool seings and security seings:
If you plan to use Access Point, congure Connection Server to work with Access Point. See Deploying
n
and Conguring Access Point. Access Point 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 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
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 View Administrator, go to the Edit View 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 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 Seing Up Desktop and Application Pools in View document.
To use two-factor authentication with Horizon Client, such as RSA SecurID authentication, you must
n
enable this feature on Connection Server. For more information, see the topics about two-factor authentication in the View Administration document.

Installation Options

During the Horizon Client installation process, you are prompted to conrm whether to install various components. The default is to install all components.
The following table provides a brief summary of each optional component.
14 VMware, Inc.
Chapter 1 System Requirements and Installation
Table 11. Horizon Client for Linux Installation Options
Option Description
USB Redirection Gives users access to locally connected USB devices on their desktops.
USB redirection is supported on remote desktops that are deployed on single-user machines but is not supported on RDS host-based remote desktops.
The component les are installed in /usr/lib/vmware/view/usb/. The services vmware- usbarbitrator and vmware-view-usbd run automatically if you allow the installer to register and start installed services after the installation. Otherwise, you can start the two services manually by running vmware-usbarbitrator and vmware-view-usbd under /usr/lib/vmware/view/usb/.
N You can use group policy seings to disable USB redirection for specic users.
Real-Time Audio-Video
Virtual Printing Lets users print to any printer available on their client computers. Users do not have to install
Multimedia Redirection (MMR)
Smart Card Lets users authenticate with smart cards when they use the VMware Blast or PCoIP display protocol.
Client Drive Redirection
Redirects webcam and audio devices that are connected to the client system so that they can be used on the remote desktop.
The component le is installed in /usr/lib/pcoip/vchan_plugins/.
additional drivers on their remote desktops.
The component les are installed in /usr/lib/vmware/view/virtualPrinting/. After you install the client, you do not need to manually congure this feature if you allow the installer to register and start installed services after the installation. Otherwise, you can congure and enable this feature by following the instructions in “Enable the Virtual Printing Feature on a Linux Client,” on page 18.
In Horizon 6.0.2 and later, virtual printing is supported on the following remote desktops and applications:
Desktops that are deployed on single-user machines.
n
Desktops that are deployed on RDS hosts, where the RDS hosts are virtual machines.
n
Remote applications, which are provided by RDS hosts.
n
Remote applications that are launched from Horizon Client inside remote desktops (nested
n
sessions).
Redirects multimedia stream from the desktop to the client machine, where the stream is processed.
The component le is installed in /usr/lib/vmware/view/vdpService/.
Although this option is selected in the client installer by default, this option is not selected by default when you run the View Agent installer in the remote desktop.
Smart card is supported on remote desktops that are deployed on single-user machines and RDS hosts. For smart card support on RDS hosts, you must have View Agent 6.1.1 or later.
The component les are installed in /usr/lib/pcoip/vchan_plugins/.
Lets users share folders and drives on the client computer with remote desktops and applications. Drives can include mounted drives and USB storage devices.
The component les are installed in /usr/lib/vmware/view/vdpService/.

Install or Upgrade Horizon Client for Linux from VMware Product Downloads

You can download and run a Horizon Client installer bundle from the VMware Downloads page. This installer contains modules for features such as USB redirection, virtual printing, Real-Time Audio-Video, smart card, and client drive redirection.
N On most Linux distributions, the Horizon Client installer bundle launches a GUI wizard. On SUSE Linux distributions, the bundle installer launches a command-line wizard. You can also run the installer with the --console option to launch the command-line wizard.
Prerequisites
Verify that the client system runs a supported operating system. See “System Requirements for Linux
n
Client Systems,” on page 8.
Using VMware Horizon Client for Linux
Become familiar with the installation options. See “Installation Options,” on page 14.
n
Verify that you have root access on the host system.
n
Verify that VMware Workstation is not installed on the client system.
n
If you plan to use the RDP display protocol to connect to a View desktop, verify that you have the
n
appropriate RDP client installed. See “System Requirements for Linux Client Systems,” on page 8.
Uninstall any earlier version of the Horizon Client software. See “Uninstall Horizon Client for Linux,”
n
on page 70.
If you plan to use the command-line installer, become familiar with the Linux command-line
n
installation options. See “Command-Line Installation Options for the Linux Client,” on page 17.
On SUSE Linux distributions, run sudo zypper install python-curses to install the curses library.
n
As part of the installation process, the installer runs a scan of the system libraries to determine whether the system is compatible with Horizon Client, although you can select to skip the scan.
Procedure
1 On the Linux client system, download the Horizon Client installer le from the Horizon Client Product
Downloads page at hp://www.vmware.com/go/viewclients.
The name of the le is VMware-Horizon-Client-x.x.x-yyyyyyy.arch.bundle, where x.x.x is the version number, yyyyyyy is the build number, and arch is either x86 or x64.
2 Open a Terminal window, change directories to the directory that contains the installer le, and run the
installer, using the appropriate command.
Option Command
For the GUI wizard, if you have set executable permissions
For the GUI wizard, if you have not set executable permissions
For the command-line installer
sudo ./VMware-Horizon-Client-x.x.x-yyyyyyy.arch.bundle
sudo sh ./VMware-Horizon-Client-x.x.x-yyyyyyy.arch.bundle
sudo ./VMware-Horizon-Client-x.x.x-yyyyyyy.arch.bundle
--console
The installer wizard appears, prompting you to accept the end user license agreement.
3 Follow the prompts to nish the installation.
I You are prompted to allow the installer to register and start installed services after the installation. Allowing the installer to complete these tasks means that you will not need to manually start USB redirection services every time you reboot, and you will not need to manually enable the virtual printing feature.
4 After installation is complete, specify whether to perform the compatibility scan for libraries that
various feature components are dependent on.
The system scan displays a result value for each library compatibility.
Result Value Description
Success
Failed
All needed libraries were found.
The specied library was not found.
Log information about the installation is recorded in /tmp/vmware-root/vmware-installer-pid.log.
16 VMware, Inc.
What to do next
Start Horizon Client and verify that you can log in to the correct virtual desktop. See “Connect to a Remote
Desktop or Application,” on page 47.

Command-Line Installation Options for the Linux Client

You can use command-line installation options to install Horizon Client on a Linux system.
Install Horizon Client silently by using the --console option along with other command-line options and environment variable seings. With silent installation, you can eciently deploy View components in a large enterprise.
The following table lists the options you can use when you run the VMware-Horizon-Client-x.x.x-
yyyyyyy.arch.bundle installer le.
Table 12. Linux Command-Line Installation Options
Option Description
--help
--console
--custom
--eulas-agreed
--gtk
--ignore-errors or -I
--regular
--required
--set-setting vmware-horizon-smartcard smartcardEnable yes
--set-setting vmware-horizon-rtav rtavEnable yes
--set-setting vmware-horizon-usb usbEnable yes
--set-setting vmware-horizon-virtual­printing tpEnable yes
--set-setting vmware-horizon-tsdr tsdrEnable yes
--set-setting vmware-horizon-mmr mmrEnable yes
--stop-services
Displays usage information.
Enables you to use the command-line installer in a Terminal window.
Shows all installation questions, even if default answers have been scripted, such as, for example, by using the --set-setting options.
The default is --regular, which means show only questions that do not have a default answer.
Agrees to the end user license agreement.
Opens the GUI-based VMware installer, which is the default option. If the GUI cannot be displayed or loaded for any reason, console mode is used.
Allows the installation to continue even if there is an error in one of the installer scripts. Because the section that has an error does not complete, the component might not be properly congured.
Shows installation questions that have not been answered before or are required. This is the default option.
Shows the license agreement prompt only and then proceeds to install the client.
The default is --regular, which means show only questions that do not have a default answer.
Installs the smart card component.
Installs the Real-Time Audio-Video component.
Installs the USB redirection feature.
Installs the virtual printing feature.
Installs the client drive redirection feature.
Installs the multimedia redirection (MMR) feature.
Do not register and start installed services.
Chapter 1 System Requirements and Installation
In addition to the options listed in the table, you can set the following environment variables.
Using VMware Horizon Client for Linux
Table 13. Linux Environment Variable Installation Settings
Variable Description
TERM=dumb
VMWARE_EULAS_AGREED=yes
VMIS_LOG_LEVEL=value
Example: Silent Installation Commands
Following is an example of how to install Horizon Client silently, and, for each component, the example species whether to install that component.
sudo env TERM=dumb VMWARE_EULAS_AGREED=yes \
Displays a very basic text UI.
Allows you to silently accept the product EULAs.
Use one of the following values for value:
n
NOTSET
n
DEBUG
n
INFO
n
WARNING
n
ERROR
n
CRITICAL
Log information is recorded in /tmp/vmware-root/vmware-installer-pid.log.
./VMware-Horizon-Client-x.x.x-yyyyyyy.arch.bundle --console \
--set-setting vmware-horizon-usb usbEnable no \
--set-setting vmware-horizon-virtual-printing tpEnable yes \
--set-setting vmware-horizon-smartcard smartcardEnable no\
--set-setting vmware-horizon-rtav rtavEnable yes \
--set-setting vmware-horizon-tsdr tsdrEnable yes
This next example shows how to perform a silent installation of Horizon Client using the default seings.
sudo env TERM=dumb VMWARE_EULAS_AGREED=yes \ ./VMware-Horizon-Client-x.x.x-yyyyyyy.arch.bundle --console --required

Enable the Virtual Printing Feature on a Linux Client

The installer bundle for Horizon Client 3.2 and later includes a virtual printing component. If you have Horizon Client 3.2, you must create a conguration le and set some environment variables to enable the feature..
The virtual printing feature lets end users use local or network printers from a remote desktop without requiring that additional print drivers be installed in the remote desktop.
I Performing this procedure is usually not necessary if you have Horizon Client 3.4 or later because you can specify during client installation that the installer should register and start installed services after installation. When the user launches the client, a conguration le is automatically created and placed in the user's home directory
Prerequisites
You must use the installer bundle provided by VMware to install Horizon Client 3.2 or later. The virtual printing component is then installed by default.
18 VMware, Inc.
Chapter 1 System Requirements and Installation
Procedure
1 Open a Terminal window and enter a command to create a folder named .thnuclnt in the home
directory.
$ mkdir ~/.thnuclnt/
N Because this le is created in a specic user's home directory, the le needs to be created for each user who will be using the Linux client system.
2 Use a text editor to create a conguration le called thnuclnt.conf in the ~/.thnuclnt folder, and add
the following text to the le:
autoupdate = 15 automap = true autoid = 0 updatecount = 1 editcount = 0
connector svc { protocol = listen interface = /home/user/.thnuclnt/svc setdefault = true }
In this text, substitute the user name for user.
3 Save and close the le.
4 Enter a command to start the thnuclnt process.
$ thnuclnt -fg
5 Enter the commands to set the environment variables for the virtual printing components.
$ export TPCLIENTADDR=/home/user/.thnuclnt/svc $ export THNURDPIMG=/usr/bin/thnurdp
6 To launch Horizon Client, start the vmware-view process.
The printers that normally appear in the client are now also redirected so that they appear in the Print dialog boxes in your remote desktop.
7 (Optional) If you ever want to disable the virtual printing feature, use the following steps:
a Enter a command to stop the thnuclnt process.
$ killall thnuclnt
b Disconnect from the remote desktop and reconnect to the desktop.
The printers will no longer be redirected.
Using VMware Horizon Client for Linux

Install Horizon Client for Linux from the Ubuntu Software Center

If you have a Ubuntu system, you can install the client from the Ubuntu Software Center as an alternative to installing the version provided on the VMware Downloads Web site. If you use the Ubuntu Software Center, you install the client by using the Synaptic Package Manager.
This topic provides instructions for obtaining the client software from the Ubuntu software Center. You can also obtain the Horizon Client software from the VMware Product Downloads Web site, as described in
“Install or Upgrade Horizon Client for Linux from VMware Product Downloads,” on page 15.
I Customers using Linux-based thin clients must contact their thin client vendor for Horizon Client updates. Customers who have successfully built their own Linux-based endpoints and need an updated client must contact their VMware sales representative.
Prerequisites
Verify that the client system uses a supported operating system. See “System Requirements for Linux
n
Client Systems,” on page 8.
Verify that you have the correct version of OpenSSL installed. See “System Requirements for Linux
n
Client Systems,” on page 8.
Verify that you can log in as an administrator on the client system.
n
If you plan to use the RDP display protocol to connect to a View desktop, verify that you have the
n
appropriate RDP client installed. See “System Requirements for Linux Client Systems,” on page 8.
Uninstall any version of View Client 1.x or 2.x. See “Uninstall Horizon Client for Linux,” on page 70.
n
Procedure
1 On your Linux laptop or PC, enable Canonical Partners.
a From the Ubuntu menu bar, select System > Administration > Update Manager.
b Click the  buon and supply the password for performing administrative tasks.
c In the Software Sources dialog box, click the Other Software tab and select the Canonical Partners
check box to select the archive for software that Canonical packages for their partners.
d Click Close and follow the instructions to update the package list.
2 If you have Ubuntu 12.04 or 14.04, download and install the package from the Ubuntu software Center,
as follows.
a Open a Terminal window and enter the command to get new packages:
sudo apt-get update
New packages are downloaded, and you see a list of the packages in the Terminal window.
b Open the Update Manager, check for updates, and install updates.
c Open the Ubuntu Software Center app, and search on vmware-view-client.
d Install the vmware-view-client app.
If your operating system is Ubuntu 12.04 or 14.04, the latest version of Horizon Client is installed.
An application icon for VMware Horizon Client appears in the Application Launcher.
What to do next
Start Horizon Client and verify that you can log in to the correct virtual desktop. See “Connect to a Remote
Desktop or Application,” on page 47.
20 VMware, Inc.

Configure VMware Blast Options

You can congure H.264 decoding and network protocol options for remote desktop and application sessions that use the VMware Blast display protocol.
H.264 decoding has the following restrictions:
Multiple monitors are not supported.
n
The maximum resolution that is supported depends on the capability of the graphical processing unit
n
(GPU) on the client. A GPU that can support 4K resolution for JPEG/PNG might not be able to support 4K resolution for H.264. If a resolution for H.264 is not supported, Horizon Client uses JPEG/PNG instead.
H.264 decoding is supported on AMD, NVIDIA, and Intel GPUs. H.264 decoding requires that the graphics library OpenGL 3.2 or later is installed for AMD and NVIDIA GPUs.
If you plan to use H.264 decoding with an NVIDIA GPU, install VDPAU (Video Decode and Presentation API for Unix). VDPAU is no longer included with the latest NVIDIA driver and must be installed separately.
To use H.264 with an Intel GPU, the Intel VA-API driver and the GLX VA-API libraries are required. Running the command vainfo should show the H.264 proles. If the VA-API driver version is 1.2.x or earlier, you must add the entry mks.enableGLBasicRenderer = TRUE to /etc/vmware/config, /usr/lib/vmware/config or ~/.vmware/config. The conguration les are processed in the following order:
Chapter 1 System Requirements and Installation
1 /etc/vmware/config
2 /usr/lib/vmware/config
3 ~/.vmware/config
With Red Hat 7.2, Intel GPU, Intel driver version 1.2 or earlier, OpenGL 3.2, and H.264 enabled, you must add the following entries to one of the three conguration les to avoid display issues such as a black screen.
mks.enableGLRenderer=FALSE mks.enableGLBasicRenderer=TRUE
H.264 is not supported on SLED 11 SP4 with Intel GPU because the xorg version is too old.
Prerequisites
This feature requires Horizon Agent 7.0 or later.
Procedure
1 In the desktop and application selector window, select Connection >  or click the Seings icon
in the upper-right portion of the window, and select VMware Blast in the left pane of the Seings window.
VMware, Inc. 21
Using VMware Horizon Client for Linux
2 Congure the decoding and network protocol options.
Option Description
H.264
UDP
Select 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 encoding. If the agent does not support H.264 software encoding, Horizon Client uses JPG/PNG decoding.
Deselect this option to always use JPG/PNG decoding.
Select this option to allow UDP networking in Horizon Client. When this option is selected (the default seing), Horizon Client uses UDP networking if UDP connectivity is available. If UDP networking is blocked, Horizon Client uses TCP networking.
Deselect this option to always use TCP networking.
N UDP is disabled by default on a Horizon remote desktop. For UDP to work, it must be enabled on the desktop, the client, and the Blast Secure Gateway (BSG).
Your 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.

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 containing sensitive information are made anonymous.
VMware collects data on the clients 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 in order to improve VMware's response to customer requirements. No data that identies your organization is collected. Horizon Client information is sent rst to Connection Server and then on to VMware, along with data from Connection Server instances, desktop pools, and remote desktops.
Although the information is encrypted while in transit to Connection Server, 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 View Administrator after the installation.
Table 14. 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:
? Example Value
No VMware
number and yyyyyy is the build number.)
i386
n
x86_64
n
arm
n
22 VMware, Inc.
Chapter 1 System Requirements and Installation
Table 14. Data Collected from Horizon Clients for the Customer Experience Improvement Program (Continued)
Is This Field Made Anonymous
Description
Client build name No Examples include the following:
Host operating system No Examples include the following:
Host operating system kernel No Examples include the following:
Host operating system architecture No Examples include the following:
Host system model No Examples include the following:
Host system CPU No Examples include the following:
Number of cores in the host system's processor
MB of memory on the host system No Examples include the following:
Number of USB devices connected No 2 (USB device redirection is supported only for Linux,
Maximum concurrent USB device connections
? Example Value
VMware-Horizon-Client-Win32-Windows
n
VMware-Horizon-Client-Linux
n
VMware-Horizon-Client-iOS
n
VMware-Horizon-Client-Mac
n
VMware-Horizon-Client-Android
n
VMware-Horizon-Client-WinStore
n
Windows 8.1
n
Windows 7, 64-bit Service Pack 1 (Build 7601 )
n
iPhone OS 5.1.1 (9B206)
n
Ubuntu 12.04.4 LTS
n
Mac OS X 10.8.5 (12F45)
n
Windows 6.1.7601 SP1
n
Darwin Kernel Version 11.0.0: Sun Apr 8 21:52:26 PDT
n
2012; root:xnu-1878.11.10~1/RELEASE_ARM_S5L8945X
Darwin 11.4.2
n
Linux 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24
n
17:27:10 UTC 2012
unknown (for Windows Store)
n
x86_64
n
i386
n
armv71
n
ARM
n
Dell Inc. OptiPlex 960
n
iPad3,3
n
MacBookPro8,2
n
Dell Inc. Precision WorkStation T3400 (A04 03/21/2008)
n
Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GH
n
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GH
n
unknown (for iPad)
n
No
For example: 4
4096
n
unknown (for Windows Store)
n
Windows, and Mac OS X clients.)
No 2
VMware, Inc. 23
Using VMware Horizon Client for Linux
Table 14. Data Collected from Horizon Clients for the Customer Experience Improvement Program (Continued)
Description
USB device vendor ID No Examples include the following:
USB device product ID No Examples include the following:
USB device family No Examples include the following:
USB device usage count No (Number of times the device was shared)
Is This Field Made Anonymous ? Example Value
Kingston
n
NEC
n
Nokia
n
Wacom
n
DataTraveler
n
Gamepad
n
Storage Drive
n
Wireless Mouse
n
Security
n
Human Interface Device
n
Imaging
n
24 VMware, Inc.
Loading...
+ 54 hidden pages