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 ﬁnd 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

VMware, Inc.

3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com

2 VMware, Inc.

Using VMware Horizon Client for Linux 5

System Requirements and Installation 7

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

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

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

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

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

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

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.

Using VMware Horizon Client for Linux

6 VMware, Inc.

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

“System Requirements for Real-Time Audio-Video,” on page 9

“Requirements for Multimedia Redirection (MMR),” on page 11

“Requirements for Using Flash URL Redirection,” on page 12

“Smart Card Authentication Requirements,” on page 12

“Supported Desktop Operating Systems,” on page 14

“Preparing Connection Server for Horizon Client,” on page 14

“Installation Options,” on page 14

“Install or Upgrade Horizon Client for Linux from VMware Product Downloads,” on page 15

“Install Horizon Client for Linux from the Ubuntu Software Center,” on page 20

“Congure VMware Blast Options,” on page 21

“Horizon Client Data Collected by VMware,” on page 22

VMware, Inc.

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.

VMware Blast, the display protocol that is available starting with Horizon Client 4.0 and Horizon Agent

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)

PCoIP

RDP

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

higher processor speed.

PCoIP

8 VMware, Inc.

Chapter 1 System Requirements and Installation

Available RAM above system requirements to support various monitor

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

higher processor speed.

128MB RAM.

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 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.

To support Flash URL redirection: libexpat.so.1. (The libexpat.so.0

le is no longer required.)

To improve performance when using multiple monitors, enable

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 AudioVideo, 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

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:

Video4Linux2

libv4l

Pulse Audio

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

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

View

VMware Blast (requires Horizon Agent 7.0 or later)

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

Horizon Agent 7.0 or later, installed.

Session-based desktops must have View Agent 6.1.1 or later, or

Horizon Agent 7.0 or later, installed on the RDS host.

For information about operating system requirements and other

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

GStreamer core library and uendo 0.10

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 preinstalled 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.

Client systems must have IP connectivity to the Adobe Web server that hosts the ShockWave File (SWF)

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.

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

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

A compatible smart card reader

Product-specic application drivers

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

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

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.

(Optional) To make the Username hint eld appear in the Horizon Client login dialog box, enable the

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

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

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

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

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

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 1‑1. 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.

Desktops that are deployed on RDS hosts, where the RDS hosts are virtual machines.

Remote applications, which are provided by RDS hosts.

Remote applications that are launched from Horizon Client inside remote desktops (nested

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

Client Systems,” on page 8.

VMware, Inc. 15

Using VMware Horizon Client for Linux

Become familiar with the installation options. See “Installation Options,” on page 14.

Verify that you have root access on the host system.

Verify that VMware Workstation is not installed on the client system.

If you plan to use the RDP display protocol to connect to a View desktop, verify that you have the

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,”

on page 70.

If you plan to use the command-line installer, become familiar with the Linux command-line

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.

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 1‑2. 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-virtualprinting 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.

VMware, Inc. 17

Using VMware Horizon Client for Linux

Table 1‑3. 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:

NOTSET

DEBUG

INFO

WARNING

ERROR

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.

VMware, Inc. 19

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

Client Systems,” on page 8.

Verify that you have the correct version of OpenSSL installed. See “System Requirements for Linux

Client Systems,” on page 8.

Verify that you can log in as an administrator on the client system.

If you plan to use the RDP display protocol to connect to a View desktop, verify that you have the

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.

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.

The maximum resolution that is supported depends on the capability of the graphical processing unit

(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 1‑4. 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

x86_64

arm

22 VMware, Inc.

Chapter 1 System Requirements and Installation

Table 1‑4. 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

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)

Windows 6.1.7601 SP1

Darwin Kernel Version 11.0.0: Sun Apr 8 21:52:26 PDT

2012; root:xnu-1878.11.10~1/RELEASE_ARM_S5L8945X

Darwin 11.4.2

Linux 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24

17:27:10 UTC 2012

unknown (for Windows Store)

x86_64

i386

armv71

ARM

Dell Inc. OptiPlex 960

iPad3,3

MacBookPro8,2

Dell Inc. Precision WorkStation T3400 (A04 03/21/2008)

Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GH

Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GH

unknown (for iPad)

For example: 4

4096

unknown (for Windows Store)

Windows, and Mac OS X clients.)

No 2

VMware, Inc. 23

Using VMware Horizon Client for Linux

Table 1‑4. 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

NEC

Nokia

Wacom

DataTraveler

Gamepad

Storage Drive

Wireless Mouse

Security

Human Interface Device

Imaging

24 VMware, Inc.

Configuring Horizon Client for End

Users 2

Conguring Horizon Client for end users can involve constructing URIs, seing the certicate verication mode, modifying advanced TLS/SSL options, conguring specic keys and key combinations, seing display protocol options, and enabling FIPS mode.

This chapter includes the following topics:

“Common Conguration Seings,” on page 25

“Using the Horizon Client Command-Line Interface and Conguration Files,” on page 26

“Using URIs to Congure Horizon Client,” on page 35

“Conguring Certicate Checking for End Users,” on page 38

“Conguring Advanced TLS/SSL Options,” on page 39

“Conguring Specic Keys and Key Combinations to Send to the Local System,” on page 40

“Using FreeRDP for RDP Connections,” on page 41

“Enabling FIPS Mode,” on page 43

“Conguring the PCoIP Client-Side Image Cache,” on page 44

Common Configuration Settings

Horizon Client provides several conguration mechanisms to simplify the login and desktop selection experience for end users, and enforce security policies.

The following table shows only some of the conguration seings that you can set in one or more ways.

Table 2‑1. Common Configuration Settings

Setting Mechanisms for Configuring

View Connection Server address URI, Conguration File Property, Command Line

Active Directory user name URI, Conguration File Property, Command Line

Domain name URI, Conguration File Property, Command Line

Desktop display name URI, Conguration File Property, Command Line

Window size URI, Conguration File Property, Command Line

Display protocol URI, Conguration File Property, Command Line

Conguring certicate checking Conguration File Property

Conguring SSL protocols and

cryptographic algorithms

Conguration File Property, Command Line

VMware, Inc. 25

Using VMware Horizon Client for Linux

Using the Horizon Client Command-Line Interface and Configuration Files

You can congure Horizon Client using command-line options or equivalent properties in a conguration le.

You can use the vmware-view command-line interface or set properties in conguration les to dene default values your users see in Horizon Client or to suppress some dialog boxes from prompting users for information. You can also specify seings that you do not want users to change.

Processing Order for Configuration Settings

When Horizon Client starts up, conguration seings are processed from various locations in the following order:

1 /etc/vmware/view-default-config

2 ~/.vmware/view-preferences

3 Command-line arguments

4 /etc/vmware/view-mandatory-config

If a seing is dened in multiple locations, the value that is used is the value from the last le or commandline option read. For example, to specify seings that override users' preferences, set properties in the /etc/vmware/view-mandatory-config le.

To set default values that users can change, use the /etc/vmware/view-default-config le. After users change a seing, when they exit Horizon Client, any changed seings are saved in the ~/.vmware/view-

preferences le.

Properties That Prevent Users from Changing Defaults

For many properties, you can set a corresponding view.allow property that controls whether users are allowed to change the seing. For example, if you set the view.allowDefaultBroker property to "FALSE" in the /etc/vmware/view-mandatory-config le, users will not be able to change the name of the server when they connect using Horizon Client.

Syntax for Using the Command-Line Interface

Use the following form of the vmware-view command from a terminal window.

vmware-view [command-line-option [argument]] ...

By default, the vmware-view command is located in the /usr/bin directory.

You can use either the short form or the long form of the option name, although not all options have a short form. For example, to specify the domain you can use either -d (short form) or --domainName= (long form). You might choose to use the long form to make a script more human-readable.

You can use the --help option to get a list of command-line options and usage information.

I If you need to use a proxy, use the following syntax:

http_proxy=proxy_server_URL:port https_proxy=proxy_server_URL:port vmware-view options

This workaround is required because you must clear the environment variables that were previously set for the proxy. If you do not perform this action, the proxy exception seing does not take eect in Horizon Client. You congure a proxy exception for the View Connection Server instance.

26 VMware, Inc.

Chapter 2 Configuring Horizon Client for End Users

Horizon Client Configuration Settings and Command-Line Options

For your convenience, almost all conguration seings have both a key=value property and a corresponding command-line option name. For a few seings, there is a command-line option but no corresponding property you can set in a conguration le. For a few other seings, you must set a property because no command-line option is available.

I Some command-line options and conguration keys are available only with the version of Horizon Client provided by third-party vendors. For more information about VMware thin-client and zeroclient partners, see the VMware Compatibility Guide at

hp://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm.

Table 2‑2. Horizon Client Command-Line Options and Configuration File Keys

Configuration Key Command-Line Option Description

view.allMonitors --allmonitors

view.allowDefaultBroker -l, --lockServer

view.autoConnectBroker

view.autoConnectDesktop

view.autoDisconnectEmptyAppSession

None Automatically connects to the last View server used

None Automatically connects to the last View desktop used

None

Hides the host operating system and opens the Horizon Client user interface in full screen mode on all monitors that are connected when the client is launched.

If you are seing the conguration key, specify "TRUE" or "FALSE". Default is "FALSE".

Using this command-line option, or seing the property to "FALSE", disables the Server eld unless the client has never connected to any server, and no server address is provided in the command line or the preferences le.

Example of using the command-line option:

--lockServer -s view.company.com

unless the view.defaultBroker conguration property is set or unless the --serverURL= commandline option is used.

Specify "TRUE" or "FALSE". Default is "FALSE".

Seing this property and the view.autoConnectDesktop property to "TRUE" is the equivalent of seing the view.nonInteractive property to "TRUE".

unless the view.defaultDesktop conguration property is set or unless the --desktopName= command-line option is used.

Specify "TRUE" or "FALSE". Default is "FALSE".

Seing this property and the view.autoConnectBroker property to "TRUE" is the equivalent of seing the view.nonInteractive property to "TRUE".

When set to "TRUE" (the default), if the application session becomes empty because the user quits all applications, a message is displayed to the end user. This message prompts the user to choose between disconnecting the empty session or keeping the empty session running. If set to "FALSE", the session is closed according to the timeout seing used in View Administrator, which by default would be to disconnect after one minute.

VMware, Inc. 27

Using VMware Horizon Client for Linux

Table 2‑2. Horizon Client Command-Line Options and Configuration File Keys (Continued)

Configuration Key Command-Line Option Description

view.defaultAppHeight

view.defaultAppSize --appSize=

view.defaultAppWidth

view.defaultBroker -s, --serverURL=

view.defaultDesktop -n, --desktopName=

view.defaultDesktopHeight

None Species the default height of the window for remote

applications, in pixels. Use this property in conjunction with view.defaultAppWidth when specifying a custom desktop size (view.defaultAppSize property is set to "5"). Default is "480".

Sets the default size of the window for remote applications:

To use all monitors, specify "1".

To use full screen mode on one monitor, specify

"2".

To use a large window, specify "3".

To use a small window, specify "4".

To set a custom size, specify "5"and then also set the view.defaultAppWidth and view.defaultAppHeight properties.

Default is "1".

None Species the default width of the window for remote

applications, in pixels. Use this property in conjunction with view.defaultAppHeight when specifying a custom desktop size (view.defaultAppSize property is set to "5"). Default is "640".

Adds the name that you specify to the Server eld in Horizon Client. Specify a fully qualied domain name. You can also specify a port number if you do not use the default 443.

Default is the most recently used value.

Examples of using the command-line option:

--serverURL=https://view.company.com

-s view.company.com

--serverURL=view.company.com:1443

Species which desktop to use when

autoConnectDesktop is set to "TRUE" and the user has access to multiple desktops.

This is the name you would see in the Select Desktop dialog box. The name is usually the pool name.

None Species the default height of the window for the View

desktop, in pixels. Use this property in conjunction with view.defaultDesktopWidth when specifying a custom desktop size (view.defaultDesktopSize property is set to "5").

28 VMware, Inc.

Chapter 2 Configuring Horizon Client for End Users

Table 2‑2. Horizon Client Command-Line Options and Configuration File Keys (Continued)

Configuration Key Command-Line Option Description

view.defaultDesktopSize --desktopSize=

view.defaultDesktopWidth

None Species the default width of the window for the View

view.defaultDomain -d, --domainName=

view.defaultLogLevel

None Sets the log level for Horizon Client logs. Set the

view.defaultPassword -p "-", --password="-" For VMware Blast, PCoIP, and rdesktop connections,

Sets the default size of the window for the View desktop:

To use all monitors, set the property to "1" or use the command-line argument "all".

To use full screen mode on one monitor, set the

property to "2" or use the command-line argument "full".

To use a large window, set the property to "3" or use the command-line argument "large".

To use a small window, set the property to "4" or use the command-line argument "small".

To set a custom size, set the property to "5"and then also set the view.defaultDesktopWidth and view.defaultDesktopHeight properties. Alternatively, specify the width by height, in pixels, at the command-line as "widthxheight".

Examples of using the command-line option:

--desktopSize="1280x800"

--desktopSize="all"

desktop, in pixels. Use this property in conjunction with view.defaultDesktopHeight when specifying a custom desktop size (view.defaultDesktopSize property is set to "5").

Sets the domain name that Horizon Client uses for all connections and adds the domain name that you specify to the Domain Name eld in the authentication dialog box.

property to one of the following values:

"0" means include all log events.

"1" means include trace-level events and events captured for seings 2 though 6.

"2" means include debug events and events captured for seings 3 through 6.

"3" (the default) means include info-level events and events captured for seings 4 through 6.

"4" means include warning, error, and fatal events.

"5" means include error and fatal events.

"6" means include fatal events.

Default is "3".

always specify "-" to read the password from stdin.

Sets the password that Horizon Client uses for all connections and adds the password to the Password eld in the authentication dialog box if View Connection Server accepts password authentication.

N You cannot use a blank password. That is, you cannot specify --password=""

VMware, Inc. 29

Using VMware Horizon Client for Linux

Table 2‑2. Horizon Client Command-Line Options and Configuration File Keys (Continued)

Configuration Key Command-Line Option Description

view.defaultProtocol --protocol=

view.defaultUser -u, --userName=

view.disableMaximizedApp --disableMaximizedApp If set to "FALSE" (the default), the application is

view.enableMMR

None Enables multimedia redirection (MMR).

view.fullScreen --fullscreen

view.kbdLayout -k, --kbdLayout=

view.kioskLogin --kioskLogin

view.mmrPath -m, --mmrPath=

Species which display protocol to use. Specify

"PCOIP" or "RDP". These values are case-sensitive. For example, if you enter rdp the protocol used will be the default. Default is the seing specied in View Administrator, under pool seings for the pool.

If you use RDP and you want to use FreeRDP rather than rdesktop, you must also use the rdpClient

seing.

Sets the user name that Horizon Client uses for all connections and adds the user name that you specify to the User Name eld in the authentication dialog box.

For kiosk mode, the account name can be based on the client's MAC address, or it can begin with a recognized prex string, such as custom-.

launched in full screen mode.

Specify "TRUE" or "FALSE". Default is "FALSE".

Hides the host operating system and opens the Horizon Client user interface in full screen mode on one monitor. This option does not aect the screen mode of the desktop session.

If you are seing the conguration key, specify "TRUE" or "FALSE". Default is "FALSE".

Species which locale to use for the keyboard layout.

N rdesktop uses locale codes, such as "fr" and "de", whereas freerdp uses keyboard layout IDs. For

a list of these IDs, use the following command:

xfreerdp --kbd-list

Example of using the command-line option for rdesktop:

--kbdLayout="en-us"

-k "fr"

Example of using the command-line option for freerdp:

-k "0x00010407"

Species that Horizon Client is going to authenticate using a kiosk mode account.

If you are seing the conguration key, specify "TRUE" or "FALSE". Default is "FALSE".

For examples, see the kiosk mode example that follows this table.

(Available only with distributions from third-party vendors) Species the path to the directory that contains the Wyse MMR (multimedia redirection) libraries.

Example of using the command-line option:

--mmrPath="/usr/lib/altmmr"

30 VMware, Inc.

Chapter 2 Configuring Horizon Client for End Users

Table 2‑2. Horizon Client Command-Line Options and Configuration File Keys (Continued)

Configuration Key Command-Line Option Description

view.monitors --monitors= numbered list

view.nomenubar --nomenubar

view.nonInteractive -q, --nonInteractive

view.once --once

view.rdesktopOptions --rdesktopOptions=

None

-r, --redirect=

Allows you to specify which adjacent monitors to use for Horizon Client. Use --allmonitors (or view.allMonitors) to specify that you want to use full screen on all monitors, and use --monitors=numbered list to specify which subset of the monitors to use.

Example of using the command-line option to specify the rst and second monitors in a conguration where 3 monitors are set next to each other horizontally:

--allmonitors --monitors="1,2" `

Suppresses the Horizon Client menu bar when the client is in full screen mode, so that users cannot access menu options to log o of, reset, or disconnect from a View desktop. Use this option when conguring kiosk mode.

If you are seing the conguration key, specify "TRUE" or "FALSE". Default is "FALSE".

Hides unnecessary UI steps from end users by skipping the screens that are specied in the command line or conguration properties.

If you are seing the conguration key, specify "TRUE" or "FALSE". Default is "FALSE".

Seing this property to "TRUE" is the equivalent of seing the view.autoConnectBroker and

view.autoConnectDesktop properties to "TRUE".

Example of using the command-line option:

--nonInteractive

--serverURL="https://view.company.com"

--userName="user1" --password="-"

--domainName="xyz"

--desktopName="Windows 7"

Species that you do not want Horizon Client to retry connecting in the case of an error occurring.

You should usually specify this option if you use kiosk mode, and use the exit code to handle the error. Otherwise, you might nd it dicult to kill the vmware-view process remotely.

If you are seing the conguration key, specify "TRUE" or "FALSE". Default is "FALSE".

(Available if you use the Microsoft RDP display protocol) Species command-line options to forward to the rdesktop application. For information about rdesktop options, see the rdesktop documentation.

Example of using the command-line option:

--rdesktopOptions="-f -m"

(Available if you use the Microsoft RDP display protocol) Species a local device that you want rdesktop to redirect to the View desktop.

Specify the device information that you want to pass to the -r option of rdesktop. You can set multiple device options in a single command.

Example of using the command-line option:

--redirect="sound:off"

VMware, Inc. 31

Using VMware Horizon Client for Linux

Table 2‑2. Horizon Client Command-Line Options and Configuration File Keys (Continued)

Configuration Key Command-Line Option Description

view.rdpClient --rdpclient=

None

view.sendCtrlAltDelToLocal

view.sendCtrlAltDelToVM

view.sendCtrlAltInsToVM

--save

None (Available if you use the VMware Blast or PCoIP

view.sslCipherString --sslCipherString=

(Available if you use the Microsoft RDP display protocol) Species which type of RDP client to use. The default is rdesktop. To use FreeRDP instead, specify xfreerdp.

N To use FreeRDP, you must have the correct version of FreeRDP installed, along with any applicable patches. For more information, see “Install and

Congure FreeRDP,” on page 43.

Saves the user name and domain name that were last used to successfully log in so that you do not need to enter the user name or domain name the next time you are prompted to supply login credentials.

display protocol) When set to "TRUE", sends the key combination Ctrl+Alt+Del to the client system rather than opening a dialog box to prompt the user to disconnect from the View desktop. Default is "FALSE".

N If you use the Microsoft RDP display protocol, you can achieve this functionality by using the -K option; for example, vmware-view -K.

This option has the same priority as the seing in the /etc/vmware/view-keycombos-config le.

display protocol) When set to "TRUE", sends the key combination Ctrl+Alt+Del to the virtual desktop rather than opening a dialog box to prompt the user to disconnect from the View desktop. Default is "FALSE".

This option has a higher priority than the seing in the /etc/vmware/view-keycombos-config le.

display protocol) When set to "TRUE", sends the key combination Ctrl+Alt+Ins to the virtual desktop rather than sending Ctrl+Alt+Del. Default is "FALSE".

N To use this feature, you must also set the agentside GPO policy called "Use alternate key for sending Secure Aention Sequence," available in the pcoip.adm template. See the topic called "View PCoIP Session Variables for the Keyboard" in the "Conguring Policies" chapter of the Seing Up Desktop and Application Pools in View document.

This option has a lower priority than the seing in the /etc/vmware/view-keycombos-config le.

Congures the cipher list to restrict the use of certain cryptographic algorithms before establishing an encrypted SSL connection.

For a list of cipher strings, see

hp://www.openssl.org/docs/apps/ciphers.html .

The default for Horizon Client is "!aNULL:kECDH +AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH +AES:ECDH+AES:RSA+AES".

32 VMware, Inc.

Chapter 2 Configuring Horizon Client for End Users

Table 2‑2. Horizon Client Command-Line Options and Configuration File Keys (Continued)

Configuration Key Command-Line Option Description

view.sslProtocolString --sslProtocolString=

view.sslVerificationMode

None Sets the server certicate verication mode.

view.usbAutoConnectAtStartup —-usbAutoConnectAtStartUp=

view.usbAutoConnectOnInsert -—usbAutoConnectOnInsert=

view.xfreerdpOptions --xfreerdpOptions=

None

--enableNla

--printEnvironmentInfo

--usb=

--version

Congures the cipher list to restrict the use of certain cryptographic protocols before establishing an encrypted SSL connection.

The supported protocols are SSLv3/SSLv3.0, TLSv1.0/TLSv1, TLSv1.1, and TLSv1.2. The cipher list consists of one or more protocol strings separated by colons. The strings are not case-sensitive.

The default is "TLSv1.0:TLSv1.1:TLSv1.2".

Specify "1" to reject connections when the certicate fails any of the verication checks, "2" to warn but allow connections that use a self-signed certicate, or

"3" to allow unveriable connections. If you specify "3" no verication checks are performed. Default is "2".

Automatically connects USB devices when Horizon Client starts.

Specify "TRUE" or "FALSE". Default is "TRUE".

Automatically connects USB devices when a USB device is inserted.

Specify "TRUE" or "FALSE". Default is "TRUE".

(Available if you use the Microsoft RDP display protocol) Species command-line options to forward to the xfreerdp program. For information about xfreerdp options, see the xfreerdp documentation.

N To use FreeRDP, you must have the correct version of FreeRDP installed, along with any applicable patches. For more information, see “Install and

Congure FreeRDP,” on page 43.

(Applies if you are using FreeRDP for RDP connections) Enables network-level authentication (NLA). You must use this option in conjunction with the --ignore-certificate option. For more information, see “Using FreeRDP for RDP

Connections,” on page 41.

NLA is turned o by default if you are using FreeRDP.

You must have the correct version of FreeRDP installed, along with any applicable patches. For more information, see “Install and Congure FreeRDP,” on page 43.

N The rdesktop program does not support NLA.

Displays information about the environment of a client device, including its IP address, MAC address, machine name, and domain name.

For kiosk mode, you can create an account for the client based on the MAC address. To display the MAC address, you must use this option with the -s option.

Example of using the command-line option:

--printEnvironmentInfo

-s view.company.com

Species which options to use for USB redirection. See

“System Requirements for USB Redirection,” on

page 71.

Displays version information about Horizon Client.

VMware, Inc. 33

Using VMware Horizon Client for Linux

Example: Kiosk Mode Example

Kiosk users might include customers at airline check-in stations, students in classrooms or libraries, medical personnel at medical data entry workstations, or customers at self-service points. Accounts are associated with client devices rather than users because users do not need to log in to use the client device or the View desktop. Users can still be required to provide authentication credentials for some applications.

To set up kiosk mode, you must use the vdmadmin command-line interface on the View Connection Server instance and perform several procedures documented in the chapter about kiosk mode in the View Administration document. After you set up kiosk mode, you can use the vmware-view command on a Linux client to connect to a View desktop in kiosk mode.

To connect to View desktops from Linux clients in kiosk mode, you must, at a minimum, include the following conguration keys or command-line options.

Configuration Key Equivalent Command-line Options

view.kioskLogin --kioskLogin

view.nonInteractive -q, --nonInteractive

view.fullScreen --fullscreen

view.nomenubar --nomenubar

view.defaultBroker -s, --serverURL=

Omiing any of these conguration seings is not supported for kiosk mode. If View Connection Server is set up to require a non-default kiosk user name, you must also set the view.defaultUser property or use the -u or --userName= command-line option. If a non-default user name is not required and you do not specify a user name, Horizon Client can derive and use the default kiosk user name.

N If you set the view.sslVerificationMode conguration key, be sure to set it in the /etc/vmware/view-mandatory-config le. When the client runs in kiosk mode, the client does not look in the view-preferences le.

The command shown in this example runs Horizon Client on a Linux client system and has the following characteristics:

The user account name is based on the client's MAC address.

Horizon Client runs in full screen mode without a Horizon Client menu bar.

Users are automatically connected to the specied View Connection Server instance and View desktop

and are not prompted for login credentials.

If a connection error occurs, depending on the error code returned, a script might run or a kiosk

monitoring program might handle the error. As a result, for example, the client system might display an out-of-order screen or might wait a certain amount of time before aempting to connect to View Connection Server again.

./vmware-view --kioskLogin --nonInteractive --once --fullscreen --nomenubar

--serverURL="server.mycomany.com" --userName="CM-00:11:22:33:44:55:66:77" --password="mypassword"

I If a pre-login message has been congured to appear before allowing Horizon Client to connect to a View desktop, the user must acknowledge the message before being allowed to access the desktop. To avoid this issue, use View Administrator to disable pre-login messages.

34 VMware, Inc.

Using URIs to Configure Horizon Client

Using uniform resource identiers (URIs), you can create a Web page or an email with links that end users click to start Horizon Client, connect to a server, and open a specic desktop or application with specic conguration options.

You can simplify the process of connecting to a remote desktop or application by creating Web or email links for end users. You create these links by constructing URIs that provide some or all the following information, so that your end users do not need to supply it:

Connection Server address

Port number for Connection Server

Active Directory user name

Domain name

Desktop or application display name

Window size

Actions including reset, log out, and start session

Display protocol

Chapter 2 Configuring Horizon Client for End Users

To construct a URI, you use the vmware-view URI scheme with Horizon Client specic path and query parts.

N You can use URIs to start Horizon Client only if the client software is already installed on client computers.

Syntax for Creating vmware-view URIs

Syntax includes the vmware-view URI scheme, a path part to specify the desktop or application, and, optionally, a query to specify desktop or application actions or conguration options.

URI Specification

When you create a URI, you are essentially calling vmware-view with the full View URI string as an argument.

Use the following syntax to create URIs to start Horizon Client:

vmware-view://[authority-part][/path-part][?query-part]

The only required element is the URI scheme, vmware-view. For some versions of some client operating systems, the scheme name is case-sensitive. Therefore, use vmware-view.

I In all parts, non-ASCII characters must rst be encoded according to UTF-8 [STD63], and then each octet of the corresponding UTF-8 sequence must be percent-encoded to be represented as URI characters.

For information about encoding for ASCII characters, see the URL encoding reference at

hp://www.utf8-chartable.de/.

authority-part

Species the server address and, optionally, a user name, a non-default port number, or both. Underscores (_) are not supported in server names. Server names must conform to DNS syntax.

To specify a user name, use the following syntax:

user1@server-address

VMware, Inc. 35

Using VMware Horizon Client for Linux

You cannot specify a UPN address, which includes the domain. To specify the domain, you can use the domainName query part in the URI.

To specify a port number, use the following syntax:

server-address:port-number

path-part

Species the desktop or application. Use the desktop display name or application display name. This name is the one specied in View Administrator when the desktop or application pool was created. If the display name has a space in it, use the %20 encoding mechanism to represent the space.

query-part

Species the conguration options to use or the desktop or application actions to perform. Queries are not case-sensitive. To use multiple queries, use an ampersand (&) between the queries. If queries conict with each other, the last query in the list is used. Use the following syntax:

query1=value1[&query2=value2...]

Supported Queries

This topic lists the queries that are supported for this type of Horizon Client. If you are creating URIs for multiple types of clients, such as desktop clients and mobile clients, see the Using VMware Horizon Client guide for each type of client system.

action

Table 2‑3. Values That Can Be Used With the action Query

Value Description

browse

start-session

reset

logoff

Displays a list of available desktops and applications hosted on the specied server. You are not required to specify a desktop or application when using this action.

Opens the specied desktop or application. If no action query is provided and the desktop or application name is provided, start-session is the default action.

Shuts down and restarts the specied desktop or remote application. Unsaved data is lost. Reseing a remote desktop is the equivalent of pressing the Reset buon on a physical PC.

Logs the user out of the guest operating system in the remote desktop. If you specify an application, the action is ignored or the end user sees the warning message "Invalid URI action."

appProtocol

For remote applications, valid values are PCOIP and BLAST. For example, to specify PCoIP, use the syntax appProtocol=PCOIP.

desktopLayout

Sets the size of the window that displays a remote desktop. To use this query, you must set the action query to start-session or else not have an action query.

Table 2‑4. Valid Values for the desktopLayout Query

Value Description

fullscreen

multimonitor

windowLarge

36 VMware, Inc.

Full screen on one monitor. This value is the default.

Full screen on all monitors.

Large window.

Chapter 2 Configuring Horizon Client for End Users

Table 2‑4. Valid Values for the desktopLayout Query (Continued)

Value Description

windowSmall

WxH

Small window.

Custom resolution, where you specify the width by height, in pixels. An example of the syntax is desktopLayout=1280x800.

desktopProtocol

For remote desktops, valid values are RDP, PCOIP, and BLAST. For example, to specify PCoIP, use the syntax desktopProtocol=PCOIP.

domainName

The NETBIOS domain name associated with the user who is connecting to the remote desktop or application. For example, you might use mycompany rather than mycompany.com.

useExisting

If this option is set to true, only one Horizon Client instance can run. If users try to connect to a second server, they must log out of the rst server, causing desktop and application sessions to be disconnected. If this option is set to

false, multiple Horizon Client instances can run and users can connect to

multiple servers at the same time. The default is true. An example of the syntax is useExisting=false.

Examples of vmware-view URIs

You can create hypertext links or buons with the vmware-view URI scheme and include these links in email or on a Web page. Your end users can click these links to, for example, open a particular remote desktop with the startup options you specify.

URI Syntax Examples

Each URI example is followed by a description of what the end user sees after clicking the URI link.

vmware-view://view.mycompany.com/Primary%20Desktop?action=start-session

Horizon Client starts and connects to the view.mycompany.com server. The login box prompts the user for a user name, domain name, and password. After a successful login, the client connects to the desktop whose display name is displayed as Primary Desktop, and the user is logged in to the guest operating system.

N The default display protocol and window size are used. The default display protocol is PCoIP. The default window size is full screen.

You can change the defaults. See “Using the Horizon Client Command-Line Interface and

Conguration Files,” on page 26.

vmware-view://view.mycompany.com:7555/Primary%20Desktop

This URI has the same eect as the previous example, except that it uses the nondefault port of 7555 for Connection Server. (The default port is 443.) Because a desktop identier is provided, the desktop opens even though the start-session action is not included in the URI.

vmware-view://fred@view.mycompany.com/Finance%20Desktop?desktopProtocol=PCOIP

Horizon Client starts and connects to the view.mycompany.com server. In the login box, the User name text box is populated with the name fred. The user must supply the domain name and password. After a successful login, the client connects to the desktop whose display name is displayed as Finance Desktop, and the user is logged in to the guest operating system. The connection uses the PCoIP display protocol.

VMware, Inc. 37

Using VMware Horizon Client for Linux

vmware-view://view.mycompany.com/Calculator?action=start-session&appProtocol=BLAST

Horizon Client starts and connects to the view.mycompany.com server. In the login box, the user must supply the user name, domain name, and password. After a successful login, the client connects to the application whose display name is displayed as Calculator. The connection uses the VMware Blast display protocol.

vmware-view://fred@view.mycompany.com/Finance%20Desktop?domainName=mycompany

Horizon Client starts and connects to the view.mycompany.com server. In the login box, the User name text box is populated with the name fred, and the Domain text box is populated with mycompany. The user must supply only a password. After a successful login, the client connects to the desktop whose display name is displayed as Finance Desktop, and the user is logged in to the guest operating system.

vmware-view://view.mycompany.com/

Horizon Client starts and the user is taken to the login prompt for connecting to the

view.mycompany.com server.

vmware-view://view.mycompany.com/Primary%20Desktop?action=reset

Horizon Client starts and connects to the view.mycompany.com server. The login box prompts the user for a user name, domain name, and password. After a successful login, Horizon Client displays a dialog box that prompts the user to conrm the reset operation for Primary Desktop. After the reset occurs, depending on the type of client, the user might see a message that indicates whether the reset was successful.

N This action is available only if a View administrator has enabled this feature for end users.

vmware-view://

Horizon Client starts and the user is taken to the page for entering the address of a server.

HTML Code Examples

You can use URIs to make hypertext links and buons to include in emails or on Web pages. The following examples show how to use the URI from the rst URI example to code a hypertext link that says, Test Link, and a buon that says, .

</body> </html>

Configuring Certificate Checking for End Users

Administrators can congure the certicate verication mode so that, for example, full verication is always performed.

Certicate checking occurs for SSL connections between Connection Server and Horizon Client. Administrators can congure the verication mode to use one of the following strategies:

End users are allowed to choose the verication mode. The rest of this list describes the three

verication modes.

38 VMware, Inc.

(No verication) No certicate checks are performed.

(Warn) End users are warned if a self-signed certicate is being presented by the server. Users can

choose whether or not to allow this type of connection.

(Full security) Full verication is performed and connections that do not pass full verication are

rejected.

For details about the types of verication checks performed, see “Seing the Certicate Checking Mode for

Horizon Client,” on page 51.

Use the view.sslVerificationMode property to set the default verication mode:

1 implements Full Verification.

2 implements Warn If the Connection May Be Insecure.

3 implements No Verification Performed.

To congure the mode so that end users cannot change the mode, set the view.allowSslVerificationMode property to "False" in the /etc/vmware/view-mandatory-config le on the client system. See “Horizon

Client Conguration Seings and Command-Line Options,” on page 27.

Configuring 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 or between Horizon Client and the agent in the remote desktop.

Chapter 2 Configuring Horizon Client for End Users

These options are also used to encrypt the USB channel (communication between the USB service daemon and the agent).

With the default seing, cipher suites use 128- or 256-bit AES, remove anonymous DH algorithms, and then sort the current cipher list in order of encryption algorithm key length.

By default, TLS v1.0, TLS v1.1, and TLS v1.2 are enabled. SSL v2.0 and v3.0 are not supported.

N If TLS v1.0 and RC4 are disabled, USB redirection does not work when users are connected to Windows XP desktops. Be aware of the security risk if you choose to make this feature work by enabling TLS v1.0 and RC4.

If you congure a security protocol for Horizon Client that is not enabled on the View server to which the client connects, a TLS/SSL error occurs and the connection fails.

I At least one of the protocols that you enable in Horizon Client must also be enabled on the remote desktop. Otherwise, USB devices cannot be redirected to the remote desktop.

On the client system, you can use either conguration le properties or command-line options for these

seings:

To use conguration le properties, use the view.sslProtocolString and view.sslCipherString properties.

To use command-line conguration options, use the --sslProtocolString and --sslCipherString options.

For more information, see “Using the Horizon Client Command-Line Interface and Conguration Files,” on page 26 and look up the property and option names in the table in “Horizon Client Conguration Seings

and Command-Line Options,” on page 27.

VMware, Inc. 39

Using VMware Horizon Client for Linux

Configuring Specific Keys and Key Combinations to Send to the Local System

Starting with Horizon Client, if you use PCoIP, or, starting with Horizon Client 4.0, it you use VMware Blast or PCoIP, you can create a view-keycombos-config le to specify which individual keys and key combinations should not be forwarded to the remote desktop.

You might prefer to have some keys or key combinations handled by your local client system when working in a remote desktop. For example, you might want to use a particular key combination to start the screen saver on your client computer. You can create a le located at /etc/vmware/view-keycombos-config and specify the key combinations and individual keys.

Place each key or key combination on a new line using the following format:

<modName>scanCode

scanCode

The rst example is for a key combination. The second example is for a single key. The scanCode value is the keyboard scan code, in hexadecimal.

In this example, modName is one of four modier keys: ctrl, alt, shift, and super. The Super key is keyboard-specic. For example, the Super key is usually the Windows key on a Microsoft Windows keyboard but is the Command key on a Mac OS X keyboard. You can also use <any> as a wildcard for

modName. For example, <any>0x153 species all combinations of the Delete key, including the individual

Delete key for the US keyboard. The value you use for modName is not case-sensitive.

Specifying the Scan Code for a Key

The scanCode value must be in hexadecimal format. To determine which code to use, open the appropriate language- and keyboard-specic le in the lib/vmware/xkeymap directory on your client system. In addition to the key codes listed in that le, you can also use the following codes:

Table 2‑5. Multimedia Keys

Key Name Scan Code

PREVIOUS_TRACK 0x110

NEXT_TRACK 0x119

MUTE 0x120

CALCULATOR 0x121

PLAY_PAUSE 0x122

STOP 0x124

VOLUME_DOWN 0x12e

VOLUME_UP 0x130

BROWSER_HOME 0x132

BROWSER_SEARCH 0x165

BROWSER_FAVORITES 0x166

BROWSER_REFRESH 0x167

BROWSER_STOP 0x168

BROWSER_FORWARD 0x169

BROWSER_BACK 0x16A

MY_COMPUTER 0x16B

40 VMware, Inc.

Table 2‑5. Multimedia Keys (Continued)

Key Name Scan Code

MAIL 0x16C

MEDIA_SELECT 0x16D

Table 2‑6. Hangul and Hanja Keys

Key Name Scan Code

HANGUL_EN 0x72

HANJA_EN 0x71

HANGUL_KO 0x172

HANJA_KO 0x171

HANGUL 0xF2

HANJA 0xF1

Table 2‑7. System Sleep, Wake, and Power Keys

Key Name Scan Code

SYSTEM_SLEEP 0x15F

SYSTEM_WAKE 0x163

SYSTEM_POWER 0x15e

Chapter 2 Configuring Horizon Client for End Users

The following list shows the example contents of a /etc/vmware/view-keycombos-config le. Code comments are preceded by the # character.

<ctrl>0x152 #block ctrl-insert <alt>15 #block alt-tab <Ctrl><Alt>0x153 #block ctrl-alt-del <any>0x137 #block any combinations of the Print key 0x010 #block the individual Q key in a US English keyboard #or block the individual A key in a French keyboard 0x03b #block the individual F1 key 0x04f #block the individual 1 key in a numeric keypad

Using FreeRDP for RDP Connections

If you plan to use RDP rather than VMware Blast or PCoIP for connections to View desktops, you can choose between using an rdesktop client or xfreerdp, the open-source implementation of the Remote Desktop Protocol (RDP), released under the Apache license.

Because the rdesktop program is no longer being actively developed, Horizon Client can also run the

xfreerdp executable if your Linux machine has the required version and patches for FreeRDP.

I If you plan to connect to remote desktops or applications on a Microsoft RDS host, if that host is congured with the Per Device mode of licensing, you must use xfreerdp or else change the licensing mode to Per User mode. The reason is that Per Device licensing mode requires the RDP client to provide a client ID, and rdesktop does not provide that ID, whereas xfreerdp does.

You must have the correct version of FreeRDP installed, along with any applicable patches. For more information, see “Install and Congure FreeRDP,” on page 43.

VMware, Inc. 41

Using VMware Horizon Client for Linux

General Syntax

You can use the vmware-view command-line interface or some properties in conguration les to specify options for xfreerdp, just as you can for rdesktop.

To specify that Horizon Client should run xfreerdp rather than rdesktop, use the appropriate

command-line option or conguration key.

Command-line option:

Conguration key:

To specify options to forward to the xfreerdp program, use the appropriate command-line option or

--rdpclient="xfreerdp"

view.rdpClient="xfreerdp"

conguration key, and specify the FreeRDP options.

Command-line option:

Conguration key:

--xfreerdpOptions

view.xfreerdpOptions

For more information about using the vmware-view command-line interface and conguration les, see

“Using the Horizon Client Command-Line Interface and Conguration Files,” on page 26.

Syntax for Network Level Authentication

Many conguration options for the rdesktop program are the same as for the xfreerdp program. One important dierence is that xfreerdp supports network-level authentication (NLA). NLA is turned o by default. You must use the following command-line option to turn on network-level authentication:

--enableNla

Also, you must add the /cert-ignore option so that the certicate verication process can succeed. Following is an example of the correct syntax:

vmware-view --enableNla --rdpclient=xfreerdp --xfreerdpOptions="/p:password /cert-ignore /u:username /d:domain-name /v:server"

If the password contains any special characters, escape the special characters (for example: \$).

Syntax Specific to Using FreeRDP with Horizon Client

Keep the following guidelines in mind:

You must escape special characters that you might normally place in quotation marks. For example, the

following command does not work because the special character $ in pa$$word is not escaped:

(incorrect) vmware-view --rdpclient=xfreerdp --xfreerdpOptions="/p:'pa$

$word' /u:'crt\administrator'"

Instead, you must use:

(correct) vmware-view --rdpclient=xfreerdp --

xfreerdpOptions="/p:'pa\$\$word' /u:'crt\administrator'"

If end users will use a session-in-session implementation of Horizon Client, you must use the /rfx option. An example of a session-in-session implementation is one in which an end user logs in to Horizon Client on a thin client, so that the Horizon Client interface is the only one the end user sees, and the end user then launches a nested version of Horizon Client in order to use a remote application provided by an RDS host. In cases like this, if you do not use the /rfx option, the end user will not be able to see the remote desktop and application icons in the desktop and application selector of the nested client.

42 VMware, Inc.

Chapter 2 Configuring Horizon Client for End Users

Install and Configure FreeRDP

To use a FreeRDP client for RDP connections to View desktops, your Linux machine must include the required version of FreeRDP.

For a list of the packages that xfreerdp depends on in Ubuntu, go to

hps://github.com/FreeRDP/FreeRDP/wiki/Compilation.

Prerequisites

On your Linux client machine, download FreeRDP 1.1 from GitHub, at

hps://github.com/FreeRDP/FreeRDP.

Procedure

1 Patch with the le called freerdp-1.1.0.patch, using the following patch commands:

cd /client-installation-directory/patches/FreeRDP-stable-1.1 patch -p1 < freerdp-1.1.0.patch patch -p1 < freerdp-1.1.0-tls.patch

Here client-installation-directory is the path to VMware-Horizon-View-Client-x.x.x-yyyyyy.i386, where x.x.x is the version number and yyyyyy is the build number. The freerdp-1.1.0-tls.patch le enables

the TLSv1.2 connection in xfreerdp. For more information about the freerdp-1.1.0.patch le, see the

README.patches le in the same client-installation-directory/patches directory.

2 Run the following command:

cmake -DWITH_SSE2=ON -DWITH_PULSEAUDIO=ON -DWITH_PCSC=ON -DWITH_CUPS=ON .

3 Run the following command:

make

4 Run the following command, which installs the built xfreerdp binary in a directory on the execution

PATH so that Horizon Client can run the program by executing xfreerdp:

sudo make install

5 (Optional) Verify that the virtual printing module can be loaded successfully.

a To verify that tprdp.so can be loaded by FreeRDP 1.1, run the following command:

sudo ln -s /usr/lib/vmware/rdpvcbridge/tprdp.so /usr/local/lib/i386-linuxgnu/freerdp/tprdp-client.so

b To start Horizon Client with the virtual printing feature enabled, run the following command:

vmware-view --rdpclient=xfreerdp --xfreerdpOptions='/cert-ignore /vc:tprdp'

N The virtual printing feature is available if you use VMware Blast or PCoIP.

Enabling FIPS Mode

You can enable FIPS (Federal Information Processing Standard) mode so that the client uses FIPS-compliant cryptographic algorithms when communicating with remote desktops.

I If you enable FIPS mode in the client, the remote desktop must have FIPS mode enabled as well. Mixed mode, where only the client, or only the desktop, has FIPS mode enabled, is not supported.

VMware, Inc. 43

Using VMware Horizon Client for Linux

To enable FIPS mode, make the following conguration changes:

1 Edit /etc/vmware/config and add the following lines:

usb.enableFIPSMode = "TRUE" mks.enableFIPSMode = “TRUE”

2 Edit /etc/vmware/view-mandatory-config and add the following line:

View.fipsMode = ”TRUE”

3 Edit /etc/teradici/pcoip_admin.conf and add the following line:

pcoip.enable_fips_mode = 1

Configuring the PCoIP Client-Side Image Cache

PCoIP client-side image caching stores image content on the client to avoid retransmission. This feature is enabled by default to reduce bandwidth usage.

The PCoIP image cache captures spatial, as well as temporal, redundancy. For example, when you scroll down through a PDF document, new content appears from the boom of the window and the oldest content disappears from the top of the window. All the other content remains constant and moves upward. The PCoIP image cache is capable of detecting this spatial and temporal redundancy.

Because during scrolling, the display information sent to the client device is primarily a sequence of cache indices, using the image cache saves a signicant amount of bandwidth. This ecient scrolling has benets both on the LAN and over the WAN.

On the LAN, where bandwidth is relatively unconstrained, using client-side image caching delivers

signicant bandwidth savings.

Over the WAN, to stay within the available bandwidth constraints, scrolling performance is often

degraded unless client-side caching is used. In this situation, client-side caching can save bandwidth and ensure a smooth, highly responsive scrolling experience.

By default this feature is enabled, so that the client stores portions of the display that were previously transmied. The default cache size is 250MB. A larger cache size reduces bandwidth usage but requires more memory on the client. A smaller cache size requires more bandwidth usage. For example, a thin client with lile memory requires a smaller cache size.

Setting the Configuration Property

To congure the cache size, you can set the pcoip.image_cache_size_mb property. For example, the following seing congures the cache size to be 50MB:

pcoip.image_cache_size_mb = 50

Use a space before and after the equals (=) sign.

If you specify a value that is less than the amount of available memory divided by 2, the value is rounded to the nearest multiple of 10. The minimum value is 50. Any value that is less than 50 is ignored.

If you specify a value that is larger than the available memory divided by 2, the value is set to the amount of available memory divided by 2 and rounded to the nearest multiple of 10.

You can set this property in any of several les. When Horizon Client starts up, the seing is processed from various locations in the following order:

1 /etc/teradici/pcoip_admin_defaults.conf

2 ~/.pcoip.rc

3 /etc/teradici/pcoip_admin.conf

44 VMware, Inc.

Chapter 2 Configuring Horizon Client for End Users

If a seing is dened in multiple locations, the value that is used is the value from the last le read.

N You can set the following property to display a visual indication that the image cache is working:

pcoip.show_image_cache_hits = 1

With this conguration, for every tile (32 x 32 pixels) in an image that comes from the image cache, you can see a rectangle around the tile.

VMware, Inc. 45

Using VMware Horizon Client for Linux

46 VMware, Inc.

Managing Remote Desktop and

Application Connections 3

Use Horizon Client to connect to Connection Server or a security server and log in to or o of a remote desktop, and use remote applications. For troubleshooting purposes, you can also reset remote desktops and applications.

Depending on how the administrator congures policies for remote desktops, end users might be able to perform many operations on their desktops.

This chapter includes the following topics:

“Connect to a Remote Desktop or Application,” on page 47

“Share Access to Local Folders and Drives,” on page 49

“Seing the Certicate Checking Mode for Horizon Client,” on page 51

“Switch Desktops or Applications,” on page 52

“Log O or Disconnect,” on page 52

Connect to a Remote Desktop or Application

After connecting to a View server, you can use the remote desktops and applications that you are authorized to use.

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 must specify a server and supply credentials for your user account.

To use remote applications, you must connect to View Connection Server 6.0 or later.

Prerequisites

Obtain credentials to log in, 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).

Obtain the NETBIOS domain name for logging in. For example, you might use mycompany rather than

mycompany.com.

Perform the administrative tasks described in “Preparing Connection Server for Horizon Client,” on

page 14.

If you are outside the corporate network and are not using a security server to access the remote

desktop, verify that your client device is set up to use a VPN connection and turn on that connection.

I VMware recommends using a security server rather than a VPN.

VMware, Inc.

Using VMware Horizon Client for Linux

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. You also need the port number if the port is not 443.

If you plan to use the RDP display protocol to connect to a remote desktop, verify that the

AllowDirectRDP agent group policy seing is enabled.

Procedure

1 Either open a terminal window and enter vmware-view or search the applications for VMware Horizon

Client, and double-click the icon.

2 Double-click the + Add Server buon if no servers have yet been added, or click the + New Server

buon in the menu bar, and enter the name of View Connection Server or a security server, and click

Connect.

Connections between Horizon Client and View Connection Server always use SSL. The default port for SSL connections is 443. If View Connection Server is not congured to use the default port, use the format shown in this example: view.company.com:1443.

You might see a message that you must conrm before the login dialog box appears.

N After a successful connection is made, an icon for this server is saved to the Horizon Client home screen. The next time you open Horizon Client to connect to this server, you can double-click the icon, or, if you use only this one server, you can right-click the icon for the server and select Autoconnect to this Server from the context menu.

3 If you are prompted for RSA SecurID credentials or RADIUS authentication credentials, enter the user

name and passcode and click OK.

4 Enter your user name and password, select a domain, and click OK.

You might see a message that you must conrm before the login dialog box appears.

5 If the desktop security indicator turns red and a warning message appears, respond to the prompt.

Usually, this warning means that Connection Server did not send a certicate thumbprint to the client. The thumbprint is a hash of the certicate public key and is used as an abbreviation of the public key.

6 (Optional) To congure display seings for remote desktops, either right-click a desktop icon or select a

desktop icon and click the  (gear-shaped) icon next to the server name in the upper portion of the screen.

Option Description

Display protocol

Display layout

If your administrator has allowed it, you can use the Connect Via list to select the display protocol. VMware Blast requires Horizon Agent 7.0 or later.

Use the Display list to select a window size or to use multiple monitors.

7 (Optional) To mark the remote desktop or application as a favorite, right-click the desktop or

application icon and select Mark as Favorite from the context menu that appears.

A star icon appears in the upper-right corner of the desktop or application name. The next time you log in, you can click the Show Favorites buon to nd this application or desktop quickly.

8 Double-click a remote desktop or application to connect.

If you are connecting to a session-based remote desktop, which is hosted on a Microsoft RDS host, and if the desktop is already set to use a dierent display protocol, you will not be able to connect immediately. You will be prompted to either use the protocol that is currently set or have the system log you o of the remote operating system so that a connection can be made with the protocol you selected.

48 VMware, Inc.

Chapter 3 Managing Remote Desktop and Application Connections

After you are connected, the client window appears.

If authentication to View Connection Server fails or if the client cannot connect to the remote desktop or application, perform the following tasks:

Determine whether View Connection Server is congured not to use SSL. The client software requires

SSL connections. Check whether the global seing in View Administrator for the Use SSL for client connections check box is deselected. If so, you must either select the check box, so that SSL is used, or

set up your environment so that clients can connect to an HTTPS enabled load balancer or other intermediate device that is congured to make an HTTP connection to View Connection Server.

Verify that the security certicate for View Connection Server is working properly. If it is not, in View

Administrator, you might also see that the View Agent on desktops is unreachable. These are symptoms of additional connection problems caused by certicate problems.

Verify that the tags set on the View Connection Server instance allow connections from this user. See the

View Administration document.

Verify that the user is entitled to access this desktop or application. See the Seing Up Desktop and

Application Pools in View document.

If you are using the RDP display protocol to connect to a remote desktop, verify that the remote

operating system allows remote desktop connections.

Share Access to Local Folders and Drives

You can congure Horizon Client to share folders and drives on your local system with remote desktops and applications. Drives can include mapped drives and USB storage devices. This feature is called client drive redirection.

In a Windows remote desktop, shared folders and drives appear in the Devices and drives section in the This PC folder, or in the Other section in the Computer folder. In a remote application, such as Notepad, you can browse to and open a le in a shared folder or drive. The folders and drives you select for sharing appear in the le system as network drives that use the naming format name on MACHINE-NAME.

You do not need to be connected to a remote desktop or application to congure client drive redirection

seings. The seings apply to all your remote desktops and applications. That is, you cannot congure the seings so that local client folders are shared with one remote desktop or application but not with other

remote desktops or applications.

The client drive redirection feature requires that the following library les be installed. On some thin client machines, these library les might not be installed by default.

libsigc-2.0.so.0

libglibmm-2.4.so.1

Conguring the browser on the client system to use a proxy server can cause poor client drive redirection performance if the secure tunnel is enabled on the Connection Server instance. For the best client drive redirection performance, congure the browser not to use a proxy server or automatically detect LAN

seings.

Prerequisites

To share folders and drives with a remote desktop or application, you must enable the client drive redirection feature. This task includes installing View Agent 6.1.1 or later, or Horizon Agent 7.0 or later, and enabling the agent Client Drive Redirection option. It can also include seing policies or registry seings to control client drive redirection behavior. For more information, see the Seing Up Desktop and Application Pools in View document.

VMware, Inc. 49

Using VMware Horizon Client for Linux

Procedure

1 Open the Seings dialog box with the Sharing panel displayed.

Option Description

From the desktop and application selection window

From the Sharing dialog box when you connect to a desktop or application

From within a desktop OS

2 Congure the client drive redirection seings.

Option Action

Share a specific folder or drive with remote desktops and applications

Stop sharing a specific folder or drive

Allow remote desktops and applications access to files in your home directory

Do not show the Sharing dialog box when you connect to a remote desktop or application

Right-click a desktop or application icon, select , and click Sharing. Alternatively, select Connection >  from the menu bar and click Sharing.

Click Allow to share, or Deny to not share, your home directory.

Select Connection >  from the menu bar and click Sharing.

Click the Add buon, browse to and select the folder or drive to share, and click OK.

N You cannot share a folder on a USB device if the device is already connected to a remote desktop or application with the USB redirection feature.

Select the folder or drive in the Folder list and click the Remove buon.

Select the Share your home folder: home-directory check box.

Select the Do not show dialog when connecting to a desktop or application check box.

If this check box is deselected, the Sharing dialog box appears the rst time you connect to a desktop or application after you connect to a server. For example, if you log in to a server and connect to a desktop, you see the Sharing dialog box. If you then connect to another desktop or application, you do not see the dialog box again. To see the dialog box again, you must disconnect from the server and then log in again.

What to do next

Verify that you can see the shared folders from within the remote desktop or application:

From within a Windows remote desktop, open File Explorer and look in the Devices and drives section

in the This PC folder, or open Windows Explorer and look in the Other section in the Computer folder.

From within a remote application, if applicable, select File > Open or File > Save As and navigate to the

folder or drive, which appears in the le system as a network drive that uses the naming format foldername on MACHINE-NAME.

Share Folders by Editing a Configuration File

In addition to sharing folders through the Seings dialog box, you can also share folders by editing a conguration le.

Procedure

1 Create a conguration le named config if it does not exist in any of the following locations:

$HOME/.vmware/

/usr/lib/vmware/

/etc/vmware/

50 VMware, Inc.

Chapter 3 Managing Remote Desktop and Application Connections

2 Add the following line for each folder that you want to share:

tsdr.share=Folder Path

For example, to share folders / and /home/user1, create the le /etc/vmware/config and add the following lines:

tsdr.share=/ tsdr.share=/home/user1

Folders that are shared in a conguration le are not listed in the Sharing pane of the Seings dialog. You can edit the conguration le to stop sharing folders or share additional folders.

Setting the Certificate Checking Mode for Horizon Client

Administrators and sometimes end users can congure whether client connections are rejected if any or some server certicate checks fail.

Certicate checking occurs for SSL connections between Connection Server and Horizon Client. Certicate verication includes the following checks:

Is the certicate intended for a purpose other than verifying the identity of the sender and encrypting

server communications? That is, is it the correct type of certicate?

Has the certicate expired, or is it valid only in the future? That is, is the certicate valid according to

the computer clock?

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.

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.

N For information about distributing a self-signed root certicate that users can install on their Linux client systems, see the Ubuntu documentation.

Horizon Client uses the PEM-formaed certicates stored in the /etc/ssl/certs directory on the client system. For information about importing a root certicate stored in this location, see "Importing a Certicate into the System-Wide Certicate Authority Database" in the document at

hps://help.ubuntu.com/community/OpenSSL.

In addition to presenting a server certicate, Connection Server also sends a certicate thumbprint to Horizon Client. The thumbprint is a hash of the certicate public key and is used as an abbreviation of the public key. If Connection Server does not send a thumbprint, you see a warning that the connection is untrusted.

If your administrator has allowed it, you can set the certicate checking mode. Select File > Preferences from the menu bar. You have three choices:

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.

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.

Do not verify server identity . This seing means that no certicate checking occurs.

VMware, Inc. 51

Using VMware Horizon Client for Linux

Switch Desktops or Applications

If you are connected to a remote desktop, you can switch to another desktop. You can also connect to remote applications while you are connected to a remote desktop.

Procedure

Select a remote desktop or application from the same server or a dierent server.

Option Action

Choose a different desktop or application on the same server

Choose a different desktop or application on a different server

Perform one of the following actions:

Perform either of the following actions:

If you are logged in to a remote desktop and you want to switch to another remote desktop or application that is already running on your client, select the desktop or application from the View menu.

If you are logged in to a remote desktop or application and you want to switch to another desktop or application that is not running, select File > Return to Desktop and Applications List from the menu bar and then launch the desktop or application from the selector window.

From the desktop and application selector window, double-click the icon for the other desktop or application. That desktop or application opens in a new window so that you have multiple windows open, and you can switch between them.

If you want to keep the current desktop or application open and also connect to a remote desktop or application on another server, start a new instance of Horizon Client and connect to the other desktop or application.

If you want to close the current desktop and connect to a desktop on another server, go to the desktop selector window, click the Disconnect icon in the upper-left corner of the window, and conrm that you want to log o of the server. You will be disconnected from the current server and any open desktop or application sessions. You can then connect to a dierent server.

Log Off or Disconnect

With some congurations, if you disconnect from a remote desktop without logging o, applications in the desktop can remain open. You can also disconnect from a server and leave remote applications running.

Even if you do not have a remote desktop open, you can log o of the remote desktop operating system. Using this feature has the same result as sending Ctrl+Alt+Del to the desktop and then clicking Log .

Procedure

Disconnect without logging o.

Option Action

Also quit Horizon Client

Choose a different remote desktop on the same server

Choose a remote desktop on a different server

N Your View administrator can congure your desktop to automatically log o when disconnected. In that case, any open programs in your desktop are stopped.

Click the Close buon in the corner of the window or select File > Quit from the menu bar.

Select Desktop > Disconnect from the menu bar.

Select File > Disconnect from server from the menu bar.

52 VMware, Inc.

Chapter 3 Managing Remote Desktop and Application Connections

Log o and disconnect from a remote desktop.

Option Action

From within the desktop OS

From the menu bar

Use the Windows Start menu to log o.

Select Desktop > Disconnect and Log .

If you use this procedure, les that are open on the remote desktop will be closed without being saved rst.

Log o when you do not have a remote desktop open.

a From the Home screen with desktop shortcuts, select the desktop and select Desktop > Log 

from the menu bar.

b If prompted, supply credentials for accessing the remote desktop.

If you use this procedure, les that are open on the remote desktop will be closed without being saved

rst.

VMware, Inc. 53

Using VMware Horizon Client for Linux

54 VMware, Inc.

Using a Microsoft Windows Desktop

or Application on a Linux System 4

Horizon Client for Linux supports many features.

This chapter includes the following topics:

“Feature Support Matrix for Linux,” on page 55

“Internationalization,” on page 58

“Keyboards and Monitors,” on page 59

“Connect USB Devices,” on page 60

“Using the Real-Time Audio-Video Feature for Webcams and Microphones,” on page 62

“Saving Documents in a Remote Application,” on page 66

“Set Printing Preferences for the Virtual Printer Feature on a Remote Desktop,” on page 66

“Copying and Pasting Text,” on page 67

Feature Support Matrix for Linux

Some features are supported on one type of Horizon Client but not on another.

When planning which display protocol and features to make available to your end users, use the following information to determine which client operating systems support the feature.

Table 4‑1. Remote Desktop Features Supported Linux Clients

Windows Server

Windows Windows XP Desktop (View Agent 6.0.2

Feature

USB redirection Limited Limited X X X X

Real-Time AudioVideo (RTAV)

Scanner redirection

Serial port redirection

RDP display protocol

and earlier)

Limited Limited X X X X

Vista Desktop

(View Agent

6.0.2 and

earlier)

Windows 7 Desktop

Windows

8.x Desktop

Windows 10 Desktop

2008/2012 R2 or Windows Server 2016 Desktop

VMware, Inc. 55

Using VMware Horizon Client for Linux

Table 4‑1. Remote Desktop Features Supported Linux Clients (Continued)

Windows XP Desktop (View Agent 6.0.2

Feature

PCoIP display protocol

VMware Blast display protocol

Persona Management

Wyse MMR Partner client

Windows Media MMR

Location-based printing

Virtual printing Limited Limited X X X X

Smart cards Limited Limited X X X X

RSA SecurID or RADIUS

Single sign-on Limited Limited X X X X

Multiple monitors Limited Limited X X X X

Client Drive Redirection

and earlier)

Limited Limited X X X X

systems only, and only with RDP

Limited Limited X X X X

Windows

Vista Desktop

(View Agent

6.0.2 and

earlier)

Partner client

systems only,

and only with

RDP

Windows 7 Desktop

X X X X

X X X

X X X X

Windows

8.x Desktop

Windows 10 Desktop

Windows Server 2008/2012 R2 or Windows Server 2016 Desktop

Windows 10 desktops require View Agent 6.2 or later. Windows Server 2012 R2 desktops require View Agent 6.1 or later. Windows Server 2016 desktops require Horizon Agent 7.0.2 or later.

VMware Blast requires Horizon Agent 7.0 or later.

I View Agent 6.1 and later releases do not support Windows XP and Windows Vista desktops. View Agent 6.0.2 is the last View release that supports these guest operating systems. Customers who have an extended support agreement with Microsoft for Windows XP and Vista, and an extended support agreement with VMware for these guest operating systems, can deploy the View Agent 6.0.2 version of their Windows XP and Vista desktops with View Connection Server 6.1.

Feature Support for Session-Based Desktops on RDS Hosts

RDS hosts are server computers that have Windows Remote Desktop Services and View Agent or Horizon Agent installed. Multiple users can have desktop sessions on an RDS host simultaneously. An RDS host can be either a physical machine or a virtual machine.

N The following table contains rows only for the features that are supported. Where the text species a minimum version of View Agent, the text "and later" is meant to include Horizon Agent 7.0.x and later.

56 VMware, Inc.

Chapter 4 Using a Microsoft Windows Desktop or Application on a Linux System

Table 4‑2. Features Supported for RDS Hosts with View Agent 6.0.x or Later, or Horizon Agent 7.0.x or Later, Installed

Windows Server 2008 R2

Feature

RSA SecurID or RADIUS X X Horizon Agent 7.0.2 and later

Smart card View Agent 6.1 and later View Agent 6.1 and later Horizon Agent 7.0.2 and later

Single sign-on X X Horizon Agent 7.0.2 and later

RDP display protocol (for desktop clients)

PCoIP display protocol X X Horizon Agent 7.0.2 and later

VMware Blast display protocol

HTML Access View Agent 6.0.2 and later

Windows Media MMR View Agent 6.1.1 and later View Agent 6.1.1 and

Client drive redirection View Agent 6.1.1 and later View Agent 6.1.1 and

Virtual printing (for desktop clients)

Location-based printing View Agent 6.0.1 and later

Multiple monitors (for desktop clients)

Unity Touch (for mobile and Chrome OS clients)

Real-Time Audio-Video (RTAV)

RDS Host

X X Horizon Agent 7.0.2 and later

Horizon Agent 7.0 and later Horizon Agent 7.0 and

(virtual machine only)

View Agent 6.0.1 and later (virtual machine only)

(virtual machine only)

X X Horizon Agent 7.0.2 and later

Horizon Agent 7.0.2 and later

Windows Server 2012 RDS Host

later

View Agent 6.0.2 and later (virtual machine only)

later

View Agent 6.0.1 and later (virtual machine only)

Horizon Agent 7.0.2 and later

Windows Server 2016 RDS Host

Horizon Agent 7.0.2 and later

Horizon Agent 7.0.2 and later (virtual machine only)

For information about which editions of each guest operating system are supported, or which service packs, 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.

Limitations for Specific Features

Features that are supported on Windows desktops with Horizon Client for Linux have the following restrictions.

VMware, Inc. 57

Using VMware Horizon Client for Linux

Table 4‑3. Requirements for Specific Features

Feature Requirements

Real-Time Audio-Video

Virtual printing and locationbased printing for Windows Server 2008 R2 desktops, RDS desktops (on virtual machine RDS hosts), and remote applications

USB redirection

Smart cards For single-user virtual machine desktops, this feature requires View Agent 6.0.2 or later.

Client drive redirection View Agent 6.1.1 or later.

For client software from third-party vendors, this feature requires View 5.2 with

Feature Pack 2 or later.

For Horizon Client from VMware, this feature requires View Agent 6.0.2 or later.

Requires the VMware Blast or PCoIP display protocol.

For client software from third-party vendors, this feature requires Horizon 6.0.1 with

View or later.

For Horizon Client from VMware, this feature requires View Agent 6.0.2 or later.

Requires the VMware Blast or PCoIP display protocol.

For client software from third-party vendors, this feature requires View 5.1 or later.

For Horizon Client from VMware, this feature requires View Agent 6.0.2 or later.

Requires the VMware Blast or PCoIP display protocol.

For session-based desktops provided by RDS hosts, this feature requires View Agent 6.1 or later.

N You can also use Horizon Client to securely access remote Windows-based applications, in addition to remote desktops. Selecting an application in Horizon Client opens a window for that application on the local client device, and the application looks and behaves as if it were locally installed.

You can use remote applications only if you are connected to Connection Server 6.0 or later. For information about which operating systems are supported for the RDS (Remote Desktop Sessions) host, which provides remote applications and session-based desktops, see "Supported Operating Systems for Horizon 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.

N The features that are available for each thin client device 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 thin client devices, see the VMware Compatibility Guide at

hp://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm.

For descriptions of these features and their limitations, see the View Planning document.

Feature Support for Linux Desktops

Some Linux guest operating systems are supported if you have View Agent 6.1.1 or later. For a list of supported Linux operating systems and information about supported features, see Seing Up Horizon 6 for Linux Desktops, which is part of the Horizon 6, version 6.1 documentation.

Internationalization

The user interface and documentation are available in English, Japanese, French, German, Simplied Chinese, Traditional Chinese, Korean, and Spanish.

If you are using a Ubuntu 10.4 Linux client system and you want to display the client user interface in a language other than English, you must set the client system to use a locale that uses UTF-8 encoding.

58 VMware, Inc.

Chapter 4 Using a Microsoft Windows Desktop or Application on a Linux System

Keyboards and Monitors

You can use multiple monitors and all types of keyboards with a remote desktop. Certain seings ensure the best possible user experience.

Best Practices for Using Multiple Monitors

Following are recommendations for successfully using multiple monitors with a remote desktop:

Dene the primary monitor as the boom-left-most monitor.

Enable Xinerama. If you do not enable Xinerama, the primary display might be identied incorrectly.

The menu bar will appear on the top-left-most monitor. For example, if you have two monitors side by

side and the top of the left monitor is lower than the top of the right monitor, the menu bar will appear on the right monitor because the right monitor is still the top-left-most monitor.

You can use up to 4 monitors if you have enough video RAM.

To use more than 2 monitors to display your remote desktop on a Ubuntu client system, you must congure the kernel.shmmax seing correctly. Use the following formula:

max horizontal resolution X max vertical resolution X max number of monitors X 4

For example, manually seing kernel.shmmax to 65536000 allows you to use four monitors with a screen resolution of 2560x1600.

Horizon Client uses the monitor conguration that is in use when Horizon Client starts. If you change a

monitor from landscape to portrait mode or if you plug an additional monitor in to the client system while Horizon Client is running, you must restart Horizon Client in order to use the new monitor

conguration.

Horizon Client supports the following monitor congurations:

If you use 2 monitors, the monitors are not required to be in the same mode. For example, if you are

using a laptop connected to an external monitor, the external monitor can be in portrait mode or landscape mode.

If you have a version of Horizon Client that is earlier than 4.0, and you use more than 2 monitors, the

monitors must be in the same mode and have the same screen resolution. That is, if you use 3 monitors, all 3 monitors must be in either portrait mode or landscape mode and must use the same screen resolution.

Monitors can be placed side by side, stacked 2 by 2, or vertically stacked only if you are using 2

monitors.

If you specify that you want to use all monitors, and if you are using the VMware Blast or PCoIP

display protocol, you can specify a subset of adjacent monitors to use by right-clicking the desktop in the desktop selector window, selecting Full Screen - All Monitors from the Display drop-down list, and clicking to select the monitors you want to use.

N If you have a Ubuntu client system, you must select the top-left-most monitor as one of the monitors. For example, if you have 4 monitors stacked 2 X 2, you must select either the 2 monitors on top or the 2 left-most monitors.

Screen Resolution

Consider the following guidelines when seing screen resolutions:

If you open a remote desktop on a secondary monitor and then change the screen resolution on that

monitor, the remote desktop moves to the primary monitor.

VMware, Inc. 59

Using VMware Horizon Client for Linux

With PCoIP, if you use 2 monitors, you can adjust the resolution for each monitor separately, with a

resolution of up to 2560 x 1600 per display. If you use more than 2 monitors, the monitors must use the same screen resolution.

With the VMware Blast display protocol or the PCoIP display protocol, a remote desktop screen

resolution of 4K (3840 x 2160) is supported. The number of 4K displays that are supported depends on the hardware version of the desktop virtual machine and the Windows version.

Hardware Version Windows Version

10 (ESXi 5.5.x compatible) 7, 8, 8.x, 10 1

11 (ESXi 6.0 compatible) 7 (3D rendering feature disabled and Windows Aero

11 7 (3D rendering feature enabled) 1

11 8, 8.x, 10 1

The remote desktop must have View Agent 6.2 or later, or Horizon Agent 7.0 or later, installed. For best performance, the virtual machine should have at least 2 GB of RAM and 2 vCPUs. This feature might require good network conditions, such as a bandwidth of 1000Mbps with low network latency and a low package loss rate.

N When the remote desktop screen resolution is set to 3840 x 2160 (4K), items on the screen might appear smaller, and you might not be able to use the Screen Resolution dialog box in the remote desktop to make text and other items larger.

Number of 4K Displays Supported

disabled)

With RDP, if you have multiple monitors, you cannot adjust the resolution for each monitor separately.

Keyboard Limitations

For the most part, keyboards work as well with a remote desktop as they do with a physical computer. Following is a list of the limitations you might encounter, depending on the type of peripherals and software on your client system:

If you use the PCoIP display protocol and want the remote desktop to detect which keyboard map your

client system uses, such as, for example, a Japanese keyboard or a German keyboard, you must set a GPO in the View agent. Use the Turn on PCOIP user default input language synchronization policy, available as part of the View PCoIP Session Variables ADM template le. For more information, see the Seing Up Desktop and Application Pools in View document.

Some multimedia keys on a multimedia keyboard might not work. For example, the Music key and My

Computer key might not work.

If you connect to a desktop using RDP and if you have the Fluxbox window manager, if a screen saver

is running in the remote desktop, after a period of inactivity, the keyboard might stop working.

Regardless of which window manager you use, VMware recommends turning o the screen saver in a remote desktop and not specifying a sleep timer.

Connect USB Devices

You can access locally aached USB devices, such as thumb ash drives, cameras, and printers, from a remote desktop. This feature is called USB redirection.

With this feature, most USB devices that are aached to the local client system are available from a menu in Horizon Client. You can use the menu to connect and disconnect the devices.

60 VMware, Inc.

Chapter 4 Using a Microsoft Windows Desktop or Application on a Linux System

Using USB devices with remote desktops has the following limitations:

When you access a USB device from a menu in Horizon Client and use the device in a remote desktop,

you cannot access the device on the local computer.

USB devices that do not appear in the menu, but are available in a remote desktop, include human

interface devices such as keyboards and pointing devices. The remote desktop and the local computer use these devices at the same time. Interaction with these devices can sometimes be slow because of network latency.

Large USB disk drives can take several minutes to appear in the desktop.

Some USB devices require specic drivers. If a required driver is not already installed on a remote

desktop, you might be prompted to install it when you connect the USB device to the remote desktop.

If you plan to aach USB devices that use MTP drivers, such as Android-based Samsung smart phones

and tablets, you must set Horizon Client to automatically connect USB devices to your remote desktop. Otherwise, if you try to manually redirect the USB device by using a menu item, the device will not be redirected unless you unplug the device and then plug it in again.

Webcams are not supported for USB redirection using the Connect USB Device menu. To use a

webcam or audio input device, you must use the Real-Time Audio-Video feature. This feature is available when used in conjunction with View 5.2 Feature Pack 2 or a later release. See “Using the Real-

Time Audio-Video Feature for Webcams and Microphones,” on page 62.

The redirection of USB audio devices depends on the state of the network and is not reliable. Some

devices require a high data throughput even when they are idle. If you have the Real-Time AudioVideo feature, included with View 5.2 Feature Pack 2 or a later release, audio input and output devices will work well using that feature, and you do not need to use USB redirection for those devices.

You can connect USB devices to a remote desktop either manually or automatically.

N Do not redirect USB devices such as USB Ethernet devices and touch screen devices to the remote desktop. If you redirect a USB Ethernet device, your client system will lose network connectivity. If you redirect a touch screen device, the remote desktop will receive touch input but not keyboard input. If you have set your virtual desktop to autoconnect USB devices, you can congure a policy to exclude specic devices. See the topic "Conguring Filter Policy Seings for USB Devices" in the Seing Up Desktop and Application Pools in View document.

I This procedure describes how to use the Horizon Client menu to connect USB devices and to

congure connecting USB devices automatically. You can also congure USB redirection by using a conguration le or by creating a group policy. For more information about using a conguration le, see

“System Requirements for USB Redirection,” on page 71. For more information about creating group

policies, see the Seing Up Desktop and Application Pools in View document.

Prerequisites

To use USB devices with a remote desktop, the View administrator must have enabled the USB feature

for the remote desktop.

This task includes installing the USB Redirection component of the agent, and can include seing policies regarding USB redirection. For more information, see the View Administration document if you are using Connection Server and Agent 5.3.x. See Seing Up Desktop and Application Pools in View if you are using Connection Server and Agent 6.0 or later.

When Horizon Client was installed, the USB Redirection component must have been installed. If you

did not include this component in the installation, uninstall the client and run the installer again to include the USB Redirection component.

VMware, Inc. 61

Using VMware Horizon Client for Linux

Procedure

Manually connect or disconnect a USB device.

a From the Horizon Client menu bar, click Connect USB Device.

b Select or unselect the USB device.

From the Connect USB Device menu, select or unselect Automatically Connect at Startup to congure

whether to connect USB devices when Horizon Client starts.

This option is selected by default.

From the Connect USB Device menu, select or unselect Automatically Connect when Inserted to

congure whether to connect a USB device when you inset it into the client system.

Enable this option if you plan to connect devices that use MTP drivers, such as Android-based Samsung smart phones and tablets. This option is selected by default.

You can also congure automatically connecting USB devices using the conguration le options view.usbAutoConnectAtStartup and view.usbAutoConnectOnInsert For more information, see

“Horizon Client Conguration Seings and Command-Line Options,” on page 27..

If the USB device does not appear in the desktop after several minutes, disconnect and reconnect the device to the client computer.

What to do next

If you have problems with USB redirection, see the topic about troubleshooting USB redirection problems in the Seing Up Desktop and Application Pools in View document.

Using the Real-Time Audio-Video Feature for Webcams and Microphones

With the Real-Time Audio-Video feature, you can use your local computer's webcam or microphone on your remote desktop. Real-Time Audio-Video is compatible with standard conferencing applications and browser-based video applications, and supports standard webcams, audio USB devices, and analog audio input.

For information about seing up the Real-Time Audio-Video feature and conguring the frame rate and image resolution in a remote desktop, see the VMware Horizon View Feature Pack Installation and Administration document (for View 5.3.x desktops) or the Seing Up Desktop and Application Pools in View document (for Horizon 6.0 with View and later desktops). For information about conguring these seings on client systems, see the VMware knowledge base article Seing Frame Rates and Resolution for Real-Time Audio-Video on Horizon View Clients, at hp://kb.vmware.com/kb/2053644.

To download a test application that veries the correct installation and operation of the Real-Time Audio- Video functionality, go to hp://labs.vmware.com/ings/real-time-audio-video-test-application. This test application is available as a VMware ing, and therefore no technical support is available for it.

N This feature is available only with the version of Horizon Client for Linux provided by third-party vendors or with the Horizon Client software available from the VMware Product Downloads Web site.

62 VMware, Inc.

Chapter 4 Using a Microsoft Windows Desktop or Application on a Linux System

When You Can Use Your Webcam

If a View administrator has congured the Real-Time Audio-Video feature, and if you use the VMware Blast display protocol or the PCoIP display protocol, a webcam that is built-in or connected to your local computer can be used on your desktop. You can use the webcam in conferencing applications such as Skype, Webex, or Google Hangouts.

During the setup of an application such as Skype, Webex, or Google Hangouts on your remote desktop, you can choose input and output devices from menus in the application. For virtual machine desktops, you can choose VMware Virtual Microphone and VMware Virtual Webcam. For RDS desktops, you can choose Remote Audio Device and VMware Virtual Webcam.

With many applications, however, this feature will just work, and selecting an input device will not be necessary.

If the webcam is currently being used by your local computer it cannot be used by the remote desktop simultaneously. Also, if the webcam is being used by the remote desktop it cannot be used by your local computer at the same time.

I If you are using a USB webcam, your administrator must not congure the client to automatically forward devices through USB redirection. If the webcam connects through USB redirection, the performance will be unusable for video chat.

If you have more than one webcam connected to your local computer, you can congure a preferred webcam to use on your remote desktop.

Select a Default Microphone on a Linux Client System

If you have multiple microphones on your client system, only one of them is used on your View desktop. To specify which microphone is the default, you can use the Sound control on your client system.

With the Real-Time Audio-Video feature, audio input devices and audio output devices work without requiring the use of USB redirection, and the amount of network bandwidth required is greatly reduced. Analog audio input devices are also supported.

This procedure describes choosing a default microphone from the user interface of the client system. Administrators can also congure a preferred microphone by editing a conguration le. See “Select a

Preferred Webcam or Microphone on a Linux Client System,” on page 64.

Prerequisites

Verify that you have a USB microphone or another type of microphone installed and operational on

your client system.

Verify that you are using the VMware Blast display protocol or the PCoIP display protocol for your

remote desktop.

Procedure

1 In the Ubuntu graphical user interface, select System > Preferences > Sound.

You can alternatively click the Sound icon on the right side of the toolbar at the top of the screen.

2 Click the Input tab in the Sound Preferences dialog box.

3 Select the preferred device and click Close.

VMware, Inc. 63

Using VMware Horizon Client for Linux

Select a Preferred Webcam or Microphone on a Linux Client System

With the Real-Time Audio-Video feature, if you have multiple webcams and microphones on your client system, only one webcam and one microphone can be used on your View desktop. To specify which webcam and microphone are preferred, you can edit a conguration le.

The preferred webcam or microphone is used on the remote desktop if it is available, and if not, another webcam or microphone is used.

With the Real-Time Audio-Video feature, webcams, audio input devices, and audio output devices work without requiring the use of USB redirection, and the amount network bandwidth required is greatly reduced. Analog audio input devices are also supported.

To set the properties in the /etc/vmware/config le and specify a preferred device, you must determine the values of certain elds. You can search the log le for the values of these elds.

For webcams, you set the rtav.srcWCamId property to the value of the UserId eld for the webcam and

the rtav.srcWCamName property to the value of the Name eld for the webcam.

The rtav.srcWCamName property has a higher priority than the rtav.srcWCamId property. Both properties should specify the same webcam. If the properties specify dierent webcams, the webcam specied by

rtav.srcWCamName is used, if it exists. If it does not exist, the webcam specied by rtav.srcWCamId is

used. If both webcams are not found, the default webcam is used.

For audio devices, you set the rtav.srcAudioInId property to the value of the Pulse Audio

device.description eld.

Prerequisites

Depending on whether you are conguring a preferred webcam, preferred microphone, or both, perform the appropriate prerequisite tasks:

Verify that you have a USB webcam installed and operational on your client system.

Verify that you have a USB microphone or another type of microphone installed and operational on

your client system.

Verify that you are using the VMware Blast display protocol or the PCoIP display protocol for your

remote desktop.

Procedure

1 Launch the client, and start a webcam or microphone application to trigger an enumeration of camera

devices or audio devices to the client log.

a Aach the webcam or audio device you want to use.

b Use the command vmware-view to start Horizon Client.

c Start a call and then stop the call.

This process creates a log le.

64 VMware, Inc.

Chapter 4 Using a Microsoft Windows Desktop or Application on a Linux System

2 Find log entries for the webcam or microphone.

a Open the debug log le with a text editor.

The log le with real-time audio-video log messages is located at /tmp/vmware-<username>/vmware-

RTAV-<pid>.log. The client log is located at /tmp/vmware-<username>/vmware-view-<pid>.log.

b Search the log le to nd the log le entries that reference the aached webcams and microphones.

The following example shows an extract of the webcam selection:

main| I120: RTAV: static void VideoInputBase::LogDevEnum() - 3 Device(s) found main| I120: RTAV: static void VideoInputBase::LogDevEnum() - Name=UVC Camera (046d:

0819) UserId=UVC Camera (046d:0819)#/sys/devices/pci0000:00/0000:00:1a. 7/usb1/1-3/1-3.4/1-3.4.5 SystemId=/dev/video1 main| I120: RTAV: static void VideoInputBase::LogDevEnum() - Name=gspca main driver UserId=gspca main driver#/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3.4/1-3.4.7 SystemId=/dev/video2 main| I120: RTAV: static void VideoInputBase::LogDevEnum() Name=Microsoft® LifeCam HD-6000 for Notebooks UserId=Microsoft® LifeCam HD-6000 for Notebooks#/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3.6 SystemId=/dev/video0 main| W110: RTAV: static bool AudioCaptureLin::EnumCaptureDevices(MMDev::DeviceList&) enumeration data unavailable

The following example shows an extract of the audio device selection, and the current audio level for each:

vthread-18| I120: RTAV: bool AudioCaptureLin::TriggerEnumDevices() - Triggering enumeration vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioGetSourceCB(pa_context*, const pa_source_info*, int, void*) - PulseAudio Get Source (idx=1 'alsa_output.usbLogitech_Logitech_USB_Headset-00-Headset.analog-stereo.monitor' 'Monitor of Logitech USB Headset Analog Stereo')

vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioGetSourceCB(pa_context*, const pa_source_info*, int, void*) - channel:0 vol:65536 vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioGetSourceCB(pa_context*, const pa_source_info*, int, void*) - channel:1 vol:65536 vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioGetSourceCB(pa_context*, const pa_source_info*, int, void*) - PulseAudio Get Source (idx=2 'alsa_input.usbLogitech_Logitech_USB_Headset-00-Headset.analog-mono' 'Logitech USB Headset Analog Mono')

vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioGetSourceCB(pa_context*, const pa_source_info*, int, void*) - channel:0 vol:98304 vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioGetSourceCB(pa_context*, const pa_source_info*, int, void*) - PulseAudio Get Source (idx=3 'alsa_output.usbMicrosoft_Microsoft_LifeChat_LX-6000-00-LX6000.analog-stereo.monitor' 'Monitor of Microsoft LifeChat LX-6000 Analog Stereo')

vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioGetSourceCB(pa_context*, const pa_source_info*, int, void*) - channel:0 vol:65536

Warnings are shown if any of the source audio levels for the selected device do not meet the PulseAudio criteria if the source is not set to 100% (0dB), or if the selected source device is muted, as follows:

vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioSourceInfoCB(pa_context*, const pa_source_info*, int, void*) - Note, selected device channel volume: 0: 67% vthread-18| I120: RTAV: static void AudioCaptureLin::PulseAudioSourceInfoCB(pa_context*, const pa_source_info*, int, void*) - Note, selected device channel is muted

VMware, Inc. 65

Using VMware Horizon Client for Linux

3 Copy the description of the device and use it to set the appropriate property in the /etc/vmware/config

le.

For a webcam example, copy Microsoft

HD-6000 for Notebooks#/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3.6 to specify the

Microsoft webcam as the preferred webcam and set the properties as follows:

rtav.srcWCamName = “Microsoft® LifeCam HD-6000 for Notebooks” rtav.srcWCamId = “Microsoft® LifeCam HD-6000 for Notebooks#/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3.6”

For this example, you could also set the rtav.srcWCamId property to "Microsoft". The rtav.srcWCamId property supports both partial and exact matches. The rtav.srcWCamName property supports only an exact match.

For an audio device example, copy Logitech USB Headset Analog Mono to specify the Logitech headset as the preferred audio device and set the property as follows:

rtav.srcAudioInId="Logitech USB Headset Analog Mono"

4 Save your changes and close the /etc/vmware/config conguration le.

5 Log o of the desktop session and start a new session.

LifeCam HD-6000 for Notebooks and Microsoft® LifeCam

Saving Documents in a Remote Application

With certain remote applications, such as Microsoft Word or WordPad, you can create and save documents. Where these documents are saved depends on your company's network environment. For example, your documents might be saved to a home share mounted on your local computer.

Administrators can use an ADMX template le to set a group policy that species where documents are saved. This policy is called "Set Remote Desktop Services User Home Directory." For more information, see the "RDS Proles Seings" topic in the Seing Up Desktop and Application Pools in View document.

Set Printing Preferences for the Virtual Printer Feature on a Remote Desktop

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. For each printer available through this feature, you can set preferences for data compression, print quality, double-sided printing, color, and so on.

I The virtual printing feature is available only with Horizon Client 3.2 or a later release that is available from the VMware Product Downloads Web site, or with the version of Horizon Client for Linux that is provided by third-party vendors.

This feature also has the following requirements:

The remote desktop must have View Agent 6.0.2 or later, or Horizon Agent 7.0 or later, installed.

You must be using the VMware Blast or PCoIP display protocol.

For more information about VMware thin-client and zero-client partners, see the VMware Compatibility Guide at hp://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm. For client software provided by third-party vendors, you must be using the VMware Blast, PCoIP, or FreeRDP display protocol. This feature does not work with rdesktop.

66 VMware, Inc.

Chapter 4 Using a Microsoft Windows Desktop or Application on a Linux System

After a printer is added on the local computer, Horizon Client adds that printer to the list of available printers on the remote desktop. No further conguration is required. Users who have administrator privileges can still install printer drivers on the remote desktop without creating a conict with the virtual printer component.

I This feature is not available for the following types of printers:

USB printers that are using the USB redirection feature to connect to a virtual USB port in the remote

desktop

You must disconnect the USB printer from the remote desktop in order to use the virtual printing feature with it.

The Windows feature for printing to a le

Selecting the Print to  check box in a Print dialog box does not work. Using a printer driver that creates a le does work. For example, you can use a PDF writer to print to a PDF le.

This procedure is wrien for a remote desktop that has a Windows 7 or Windows 8.x (Desktop) operating system. The procedure is similar but not exactly the same for Windows Server 2008 and Windows Server

2012.

Prerequisites

Verify that the Virtual Printing component of the agent is installed on the remote desktop. In the remote desktop le system, verify that the following folder exists: C:\Program Files\Common Files\ThinPrint.

To use virtual printing, the View administrator must have enabled the virtual printing feature for the remote desktop. This task includes enabling the Virtual Printing setup option in the agent installer, and can include seing policies regarding virtual printing behavior. For more information, see the View Administration document if you are using Connection Server and View Agent 5.x or an earlier version. See Seing Up Desktop and Application Pools in View if you are using Horizon 6 or later.

Procedure

1 In the Windows 7 or Windows 8.x remote desktop, click Start > Devices and Printers.

2 In the Devices and Printers window, right-click the default printer, select Printer Properties from the

context menu, and select the printer.

Virtual printers appear as <printer_name> in single-user virtual machine desktops and as <printer_name>(s<session_ID>) in session-based desktops on RDS hosts if View Agent 6.2 or later, or Horizon Agent 7.0 or later, is installed. If View Agent 6.1 or earlier is installed in the remote desktop, virtual printers appear as <printer_name>#:<number>.

3 In the Printer Properties window, click the Device Setup tab and specify which seings to use.

4 On the General tab, click Preferences and specify which seings to use.

5 In the Printing Preferences dialog box, select the dierent tabs and specify which seings to use.

For the Page Adjustment advanced seing, VMware recommends that you retain the default seings.

6 Click OK.

Copying and Pasting Text

It is possible to copy text to and from remote desktops and applications. Your View administrator can set this feature so that copy and paste operations are allowed only from your client system to a remote desktop or application, or only from a remote desktop or application to your client system, or both, or neither.

This feature is available if you use the VMware Blast display protocol or the PCoIP display protocol. Remote applications are supported with Horizon 6.0 or later.

VMware, Inc. 67

Using VMware Horizon Client for Linux

Administrators congure the ability to copy and paste by using group policy objects (GPOs) that pertain to View Agent or Horizon Agent in remote desktops. For more information, see the chapter about conguring policies in the Seing Up Desktops and Applications in View document.

You can copy text from Horizon Client to a remote desktop or application, or the reverse, but the pasted text is plain text.

You cannot copy and paste graphics. You also cannot copy and paste les between a remote desktop and the le system on your client computer.

Configuring the Client Clipboard Memory Size

In Horizon 7 version 7.0.1 and later and Horizon Client 4.1 and later, the clipboard memory size is congurable for both the server and the client.

When a PCoIP or VMware Blast session is established, the server sends its clipboard memory size to the client. The eective clipboard memory size is the lesser of the server and client clipboard memory size values.

To set the client clipboard memory size, add the following parameter to any one of three conguration les:

~/.vmware/config, /usr/lib/vmware/config, or /etc/vmware/config.

mksvchan.clipboardSize=value

value is the client clipboard memory size in kilobytes (KB). You can specify a maximum value of 16384 KB. If you specify 0 or do not specify a value, the default client clipboard memory size is 8192 KB (8 MB).

Horizon Client looks for the clipboard memory size in the conguration les in the following order and stops as soon as a non-zero value is found.

1 ~/.vmware/config

2 /usr/lib/vmware/config

3 /etc/vmware/config

A large clipboard memory size can negatively aect performance, depending on your network. VMware recommends that you do not set the clipboard memory size to a value greater than 16 MB.

68 VMware, Inc.

Troubleshooting Horizon Client 5

You can solve most problems with Horizon Client by reseing the desktop or by reinstalling the VMware Horizon Client application.

This chapter includes the following topics:

“Problems with Keyboard Input,” on page 69

“Reset a Remote Desktop or Application,” on page 69

“Uninstall Horizon Client for Linux,” on page 70

Problems with Keyboard Input

If, when you type in a remote desktop or application, none of the keystrokes seem to work, the issue might be with security software on your local client system.

Problem

While connected to a remote desktop or application, no characters appear when you type. Another symptom might be that a single key keeps repeating itself.

Cause

Some security software, such as Norton 360 Total Security, includes a feature that detects keylogger programs and blocks keystroke logging. This security feature is meant to protect the system against unwanted spyware that, for example, steals passwords and credit card numbers. Unfortunately, this security software might block Horizon Client from sending keystrokes to the remote desktop or application.

Solution

On the client system, turn o the keylogger detection feature of your antivirus or security software.

Reset a Remote Desktop or Application

You might need to reset a desktop or application if the application or desktop operating system stops responding. Reseing a remote desktop shuts down and restarts the desktop. Reseing your remote applications quits the applications. Unsaved data is lost.

Reseing a remote desktop is the equivalent of pressing the Reset buon on a physical PC to force the PC to restart. Any les that are open on the remote desktop will be closed without being saved rst.

Reseing applications is the equivalent of quiing all remote applications without saving any unsaved data. All open applications are closed, even if the applications come from dierent RDS server farms.

You can reset a remote desktop only if your administrator has enabled this feature.

VMware, Inc.

Using VMware Horizon Client for Linux

Procedure

Use the Reset command.

Option Action

Reset a remote desktop from within the desktop

Reset a remote desktop from the desktop and application selection window

Reset remote applications from the desktop and application selection window

Select Connection > Reset from the menu bar.

Select the remote desktop and select Connection > Reset from the menu bar.

Click the  buon (gear icon) in the upper right corner of the window, select Applications in the left pane, click Reset, and click Continue.

For a remote desktop, the operating system in the remote desktop is rebooted. The client disconnects from the desktop. For remote applications, the applications are quit.

What to do next

Wait an appropriate amount of time for system startup before aempting to connect to the remote desktop.

Uninstall Horizon Client for Linux

You can sometimes resolve problems with Horizon Client by uninstalling and reinstalling the Horizon Client application.

The method you use for uninstalling Horizon Client for Linux depends on the version and the method you used for installing the client software.

Prerequisites

Verify that you have root access on the Linux client system.

Procedure

If you have Horizon Client 3.1 or earlier, or if you installed the client from the Ubuntu Software Center,

select Applications > Ubuntu Software Center, and in the Installed Software section, select vmwareview-client and click Remove.

If you have Horizon Client 3.2 or later, which you installed from the VMware Product Downloads Web

site, open a Terminal window, change directories to the directory that contains the installer le, and run the installer command with the -u option.

sudo env VMWARE_KEEP_CONFIG=yes \

./VMware-Horizon-Client-x.x.x-yyyyyyy.arch.bundle -u vmware-horizon-client

In the le name, x.x.x is the version number, yyyyyyy is the build number, and arch is either x86 or x64. Using the VMWARE_KEEP_CONFIG=yes seing means retain the conguration seings when the client is uninstalled. If this environment variable is not set, you are prompted to specify whether to save the conguration seings.

What to do next

You can reinstall the client or install a new version. See “Install or Upgrade Horizon Client for Linux from

VMware Product Downloads,” on page 15.

70 VMware, Inc.

Configuring USB Redirection on the

Client 6

With the USB redirection feature, you can use a conguration le on the client system to specify which USB devices can be redirected to a remote desktop.

For example, you can restrict the types of USB devices that Horizon Client makes available for redirection, make View Agent prevent certain USB devices from being forwarded from a client computer, and specify whether Horizon Client should split composite USB devices into separate components for redirection.

This chapter includes the following topics:

“System Requirements for USB Redirection,” on page 71

“USB-Specic Log Files,” on page 72

“Seing USB Conguration Properties,” on page 72

“USB Device Families,” on page 75

System Requirements for USB Redirection

The USB redirection feature is available only with certain versions of the client software.

For the Horizon Client software provided by third-party vendors, the USB redirection feature has the following requirements:

The version of View Agent and View Connection Server must be View 5.1 or later.

The USB ltering features and device spliing features described in this document are available with

View Connection Server 5.1 and later.

For more information about VMware thin-client and zero-client partners, see the VMware Compatibility

Guide. To use the USB components available for third-party vendors, certain les must be installed in

certain locations, and certain processes must be congured to start before Horizon Client is launched. These details are beyond the scope of this document.

For Horizon Client, the USB redirection feature has the following requirements:

The remote desktop must have View Agent 6.0.2 or later installed.

You must be using the VMware Blast or PCoIP display protocol.

If you use Horizon 6.0.1 and later, you can plug USB 3.0 devices into USB 3.0 ports. USB 3.0 devices are supported only with a single stream. Because multiple stream support is not yet implemented, USB device performance is not enhanced. Note that on the Linux client system, i386 processors are supported, whereas armel and armhf architectures are not. The Linux kernel version must be 2.6.35 or later.

VMware, Inc.

Using VMware Horizon Client for Linux

USB-Specific Log Files

Horizon Client sends USB information to log les.

For troubleshooting purposes, you can increase the amount of information sent to USB-specic logs by using the following commands:

vmware-usbarbitrator --verbose

vmware-view-usbd -o log:trace

To get a list of usage information, use the following command:

vmware-usbarbitrator -h

Setting USB Configuration Properties

You can set USB conguration properties in the /etc/vmware/config, /usr/lib/vmware/config, and

~/.vmware/config conguration les.

The vmware-view-usbd service examines these conguration les in the following order:

1 /etc/vmware/config. If USB conguration properties are set in this le, those properties are used.

2 /usr/lib/vmware/config. If the USB properties are not found in /etc/vmware/config,

the /usr/lib/vmware/config le is checked.

3 ~/.vmware/config. If USB properties are not found in the other les, the ~/.vmware/config le is

checked.

Use the following syntax to set USB conguration properties in the conguration les.

viewusb.property1 = "value1"

With USB conguration properties, you can control whether certain types of devices are redirected. Filtering properties are also available to enable you to include or exclude certain types of devices. For Linux clients version 1.7 and later, and for Windows clients, properties for spliing composite devices are also provided.

Some property values require the VID (vendor ID) and PID (product ID) for a USB device. To nd the VID and PID, you can search on the Internet for the product name combined with vid and pid. Alternatively, you can look in the /tmp/vmware-root/vmware-view-usbd-*.log le after you plug in the USB device to the local system when Horizon Client is running. To set the location of this le, use the view-usbd.log.fileName property in the /etc/vmware/config le, for example:

view-usbd.log.fileName = "/tmp/usbd.log"

I When redirecting audio devices, make sure that the kernel version of your Ubuntu system is

3.2.0-27.43 or later. Ubuntu 12.04 includes kernel version 3.2.0-27.43. If you cannot upgrade to this kernel version, you can alternatively disable host access to the audio device. For example, you can add the line "blacklist snd-usb-audio" at the end of the /etc/modprobe.d/blacklist.conf le. If your system does not meet either of these requirements, the client system might crash when Horizon Client aempts to redirect the audio device. By default, audio devices are redirected.

The following table describes the available USB conguration properties.

72 VMware, Inc.

Table 6‑1. Configuration Properties for USB Redirection

Policy Name and Property Description

Allow Auto Device Spliing

Property:

viewusb.AllowAutoDeviceSplitting

Exclude Vid/Pid Device From Split

Property:

viewusb.SplitExcludeVidPid

Split Vid/Pid Device

Property:

viewusb.SplitVidPid

Allow Audio Input Devices

Property:

viewusb.AllowAudioIn

Allow Audio Output Devices

Property:

viewusb.AllowAudioOut

Allow HID

Property:

viewusb.AllowHID

Allow HIDBootable

Property:

viewusb.AllowHIDBootable

Allow Device Descriptor Failsafe

Property:

viewusb.AllowDevDescFailsafe

Allow Keyboard and Mouse Devices

Property:

viewusb.AllowKeyboardMouse

Allow Smart Cards

Property:

viewusb.AllowSmartcard

Allow Video Devices

Property:

viewusb.AllowVideo

Allow the automatic spliing of composite USB devices.

The default value is undened, which equates to false.

Excludes a composite USB device specied by vendor and product IDs from spliing. The format of the seing is vid-xxx1_pid-yyy1[;vid-xxx2_pid-yyy2]...

You must specify ID numbers in hexadecimal. You can use the wildcard character (*) in place of individual digits in an ID.

For example: vid-0781_pid-55**

The default value is undened.

Treats the components of a composite USB device specied by vendor and product IDs as separate devices. The format of the seing is

vid-xxxx_pid-yyyy([exintf:zz[;exintf:ww ]])[;...]

You can use the exintf keyword to exclude components from redirection by specifying their interface number. You must specify ID numbers in hexadecimal, and interface numbers in decimal including any leading zero. You can use the wildcard character (*) in place of individual digits in an ID.

For example: vid-0781_pid-554c(exintf:01;exintf:02)

N If the composite device includes components that are automatically excluded, such as mouse and keyboard components, then View does not automatically include the components that you have not explicitly excluded. You must specify a lter policy such as Include Vid/Pid Device to include those components.

The default value is undened.

Allows audio input devices to be redirected.

The default value is undened, which equates to false because the Real-Time Audio-Video feature is used for audio input and video devices, and USB redirection is not used for those devices by default.

Allows audio output devices to be redirected.

The default value is undened, which equates to false.

Allows input devices other than keyboards or mice to be redirected.

The default value is undened, which equates to true.

Allows input devices other than keyboards or mice that are available at boot time (also known as hid-bootable devices) to be redirected.

The default value is undened, which equates to true.

Allows devices to be redirected even if the Horizon Client fails to get the cong/device descriptors.

To allow a device even if it fails the cong/desc, include it in the Include lters, such IncludeVidPid or IncludePath.

The default value is undened, which equates to false.

Allows keyboards with integrated pointing devices (such as a mouse, trackball, or touch pad) to be redirected.

The default value is undened, which equates to false.

Allows smart-card devices to be redirected.

The default value is undened, which equates to false.

Allows video devices to be redirected.

Chapter 6 Configuring USB Redirection on the Client

VMware, Inc. 73

Using VMware Horizon Client for Linux

Table 6‑1. Configuration Properties for USB Redirection (Continued)

Policy Name and Property Description

Disable Remote Conguration Download

Property:

viewusb.DisableRemoteConfig

Exclude All Devices

Property:

viewusb.ExcludeAllDevices

Exclude Device Family

Property:

viewusb.ExcludeFamily

Exclude Vid/Pid Device

Property:

viewusb.ExcludeVidPid

Exclude Path

Property:

viewusb.ExcludePath

Include Device Family

Property:

viewusb.IncludeFamily

Include Path

Property:

viewusb.IncludePath

Include Vid/Pid Device

Property:

viewusb.IncludeVidPid

Disables the use of View Agent seings when performing USB device ltering.

The default value is undened, which equates to false.

Excludes all USB devices from being redirected. If set to true, you can use other policy seings to allow specic devices or families of devices to be redirected. If set to false, you can use other policy seings to prevent specic devices or families of devices from being redirected.

If you set the value of Exclude All Devices to true on View Agent, and this seing is passed to Horizon Client, the View Agent seing overrides the Horizon Client seing.

The default value is undened, which equates to false.

Excludes families of devices from being redirected. The format of the seing is family_name_1[;family_name_2]...

For example: bluetooth;smart-card

If you have enabled automatic device spliing, View examines the device family of each interface of a composite USB device to decide which interfaces should be excluded. If you have disabled automatic device spliing, View examines the device family of the whole composite USB device.

The default value is undened.

Excludes devices with specied vendor and product IDs from being redirected. The format of the seing is vid-xxx1_pid-yyy2[;vid-xxx2_pid-yyy2]...

You must specify ID numbers in hexadecimal. You can use the wildcard character (*) in place of individual digits in an ID.

For example: vid-0781_pid-****;vid-0561_pid-554c

The default value is undened.

Exclude devices at specied hub or port paths from being redirected. The format of the seing is bus-x1[/y1]..._port-z1[;bus-x2[/y2]..._port-z2]...

You must specify bus and port numbers in hexadecimal. You cannot use the wildcard character in paths.

For example: bus-1/2/3_port-02;bus-1/1/1/4_port-ff

The default value is undened.

Includes families of devices that can be redirected. The format of the seing is family_name_1[;family_name_2]...

For example: storage

The default value is undened.

Include devices at a specied hub or port paths that can be redirected. The format of the seing is bus-x1[/y1]..._port-z1[;bus-x2[/y2]..._port-z2]...

You must specify bus and port numbers in hexadecimal. You cannot use the wildcard character in paths.

For example: bus-1/2_port-02;bus-1/7/1/4_port-0f

The default value is undened.

Includes devices with specied vendor and product IDs that can be redirected. The format of the seing is vid-xxx1_pid-yyy2[;vid-xxx2_pid-yyy2]...

You must specify ID numbers in hexadecimal. You can use the wildcard character (*) in place of individual digits in an ID.

For example: vid-0561_pid-554c

The default value is undened.

74 VMware, Inc.

USB Redirection Examples

Each example is followed by a description of the eect on USB redirection.

Include most devices within mouse device family.

viewusb.IncludeFamily = "mouse" viewusb.ExcludeVidPid = "Vid-0461_Pid-0010;Vid-0461_Pid-4d20"

The rst property in this example tells Horizon Client to allow mouse devices to be redirected to a View desktop. The second property overrides the rst and tells Horizon Client to keep two specic mouse devices local and not redirect them.

Turn on automatic device spliing, but exclude one particular device from spliing. For another

particular device, keep one of its components local and redirect the other components to the remote desktop:

viewusb.AllowAutoDeviceSplitting = "True" viewusb.SplitExcludeVidPid = "Vid-03f0_Pid-2a12" viewusb.SplitVidPid = "Vid-0911_Pid-149a(exintf:03)" viewusb.IncludeVidPid = "Vid-0911_Pid-149a"

Composite USB devices consist of a combination of two or more devices, such as a video input device and a storage device. The rst property in this example turns on automatic spliing of composite devices. The second property excludes the specied composite USB device (Vid-03f0_Pid-2a12) from

spliing.

Chapter 6 Configuring USB Redirection on the Client

The third line tells Horizon Client to treat the components of a dierent composite device (Vid-0911_Pid-149a) as separate devices but to exclude the following component from being redirected: the component whose interface number is 03. This component is kept local.

Because this composite device includes a component that is ordinarily excluded by default, such as a mouse or keyboard, the fourth line is necessary so that the other components of the composite device

Vid-0911_Pid-149a can be redirected to the View desktop.

The rst three properties are spliing properties. The last property is a ltering property. Filtering properties are processed before spliing properties.

I These client conguration properties might be merged with or overridden by corresponding policies set for View Agent on the remote desktop. For information about how USB spliing and ltering properties on the client work in conjunction with View Agent USB policies, see the topics about using policies to control USB redirection, in the View Administration document.

USB Device Families

You can specify a family when you are creating USB ltering rules for Horizon Client, or View Agent or Horizon Agent.

N Some devices do not report a device family.

Table 6‑2. USB Device Families

Device Family Name Description

audio

audio-in

audio-out

bluetooth

Any audio-input or audio-output device.

Audio-input devices such as microphones.

Audio-output devices such as loudspeakers and headphones.

Bluetooth-connected devices.

VMware, Inc. 75

Using VMware Horizon Client for Linux

Table 6‑2. USB Device Families (Continued)

Device Family Name Description

comm

hid

hid-bootable

imaging

keyboard

mouse

other

pda

physical

printer

security

smart-card

storage

unknown

vendor

video

wireless

wusb

Communications devices such as modems and wired networking adapters.

Human interface devices excluding keyboards and pointing devices.

Human interface devices that are available at boot time excluding keyboards and pointing devices.

Imaging devices such as scanners.

Keyboard device.

Pointing device such as a mouse.

Family not specied.

Personal digital assistants.

Force feedback devices such as force feedback joysticks.

Printing devices.

Security devices such as ngerprint readers.

Smart-card devices.

Mass storage devices such as ash drives and external hard disk drives.

Family not known.

Devices with vendor-specic functions.

Video-input devices.

Wireless networking adapters.

Wireless USB devices.

76 VMware, Inc.

Index

Adobe Media Server 12 agent, installation requirements 14 autoconnect USB devices 60

caching, client-side image 44 Canonical 20 certificates, ignoring problems 38, 51 client image cache 44 client drive redirection 49 clipboard memory size 68 command line options 17 command-line interface 27 configuration properties 26, 27 configuration settings 25 connect

to a desktop 47 to View Connection Server 47

USB devices 60 Connection Server 14 copying text 67 customer experience program, desktop pool

data 22

desktop

connect to 47

display options 47

display protocol 47

log off from 52

reset 69

switch 52 device families 75 devices

connecting USB 60

USB 71, 72 disconnecting from a remote desktop 52 display options, desktop 47

display protocol, desktop 47 domain 47

feature support matrix, for Linux 55 FIPS mode, enabling 43 Flash URL Redirection, system requirements 12

folder sharing, through a configuration file 50 forwarding USB devices 71 FreeRDP connections 41, 43

hardware requirements

for Linux systems 8 smart card authentication 12

Horizon Client

configuring 25 disconnect from a desktop 52 installation 7 system requirements 7 system requirements for Linux 8 troubleshooting 69

Horizon Client for Linux, installing 15, 20

image cache, client 44 installation instructions 15, 20 installation options 14

key combinations 40 keyboards 59 keyloggers 69

Linux, installing Horizon Client on 8 log in, View Connection Server 47

log off 52 logging, for USB devices 72

media file formats, supported 11 microphone 63 monitors 59 multimedia redirection (MMR) 11

operating systems, supported on the agent 14 options

display protocol 47 screen layout 47

pasting text 67

VMware, Inc.

Using VMware Horizon Client for Linux

PCoIP client image cache 44 prerequisites for client devices 14 printers, setting up 66 proxy settings 27

Real-Time Audio-Video, system requirements 9 redirection, USB 71, 72

reset desktop 69

saving documents in a remote application 66 screen resolution 59 screen layout 47 security servers 14 server connections 47 server certificate verification 38 sharing files and folders from the client

system 49

smart card authentication

configure Horizon Client 13

requirements 12 SSL certificates, verifying 38

SSL options 39 streaming multimedia 11 switch desktops 52 system requirements, for Linux 8

xfreerdp for RDP connections 41, 43

text, copying 67 ThinPrint setup 66

Ubuntu 20 uninstalling Horizon Client 70 URI examples 37 URI syntax for Horizon Clients 35 URIs (uniform resource identifiers) 35 USB redirection 71, 72 USB device families 75 USB devices 60

verification modes for certificate checking 38 View Connection Server, connect to 47 virtual printing feature 18, 66 VMware Blast 21 vmware-view command-line interface 26, 27

webcam 62–64

78 VMware, Inc.

VMware Horizon Client 4.2 User Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Using VMware Horizon Client for Linux

System Requirements for Linux Client Systems

System Requirements for Real-Time Audio-Video

Requirements for Multimedia Redirection (MMR)

Requirements for Using Flash URL Redirection

Smart Card Authentication Requirements

Configure Horizon Client for Smart Card Authentication

Supported Desktop Operating Systems

Preparing Connection Server for Horizon Client

Installation Options

Install or Upgrade Horizon Client for Linux from VMware Product Downloads

Command-Line Installation Options for the Linux Client

Enable the Virtual Printing Feature on a Linux Client

Install Horizon Client for Linux from the Ubuntu Software Center

Configure VMware Blast Options

Horizon Client Data Collected by VMware

Common Configuration Settings

Using the Horizon Client Command-Line Interface and Configuration Files

Horizon Client Configuration Settings and Command-Line Options

Using URIs to Configure Horizon Client

Syntax for Creating vmware-view URIs

Examples of vmware-view URIs

Configuring Certificate Checking for End Users

Configuring Advanced TLS/SSL Options

Configuring Specific Keys and Key Combinations to Send to the Local System

Using FreeRDP for RDP Connections

Install and Configure FreeRDP

Enabling FIPS Mode

Configuring the PCoIP Client-Side Image Cache

Connect to a Remote Desktop or Application

Share Access to Local Folders and Drives

Share Folders by Editing a Configuration File

Setting the Certificate Checking Mode for Horizon Client

Switch Desktops or Applications

Log Off or Disconnect

Feature Support Matrix for Linux

Internationalization

Keyboards and Monitors

Connect USB Devices

Using the Real-Time Audio-Video Feature for Webcams and Microphones

When You Can Use Your Webcam

Select a Default Microphone on a Linux Client System

Select a Preferred Webcam or Microphone on a Linux Client System

Saving Documents in a Remote Application

Set Printing Preferences for the Virtual Printer Feature on a Remote Desktop

Copying and Pasting Text

Configuring the Client Clipboard Memory Size

Troubleshooting Horizon Client 5

Problems with Keyboard Input

Reset a Remote Desktop or Application

Uninstall Horizon Client for Linux

System Requirements for USB Redirection

USB-Specific Log Files

Setting USB Configuration Properties

USB Device Families

Index