Horizon View Client Linux Document

Using VMware Horizon View Client forLinuxJanuary 2014Horizon View

This document supports the version of each product listed andsupports all subsequent versions until the document isreplaced by a new edition. To check for more recent editionsof this document, see http://www.vmware.com/support/pubs.

EN-001162-03

Using VMware Horizon View Client for Linux

2 VMware, Inc.

You can find the most up-to-date technical documentation on the VMware Web site at:

http://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:

[email protected]

Copyright 20122014 VMware, Inc. All rights reserved. Copyright and trademark information.

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

Contents

Using VMware Horizon View Client for Linux 5 1 System Requirements and Installation 7

System Requirements 8System Requirements for Real-Time Audio-Video 9Supported Desktop Operating Systems 10Requirements for Using Flash URL Redirection 10Preparing View Connection Server for Horizon View Client 11Install Horizon View Client for Linux 11Configure the View Client Download Links Displayed in View Portal 12Horizon View Client Data Collected by VMware 13

2 Configuring Horizon View Client for End Users 17Using URIs to Configure Horizon View Client 18Using the View Client Command-Line Interface and Configuration Files 21Using FreeRDP for RDP Connections 32Enabling FIPS Mode on the Client 33Configuring the PCoIP Client-Side Image Cache 33

3 Managing Server Connections and Desktops 35Log In to a Remote Desktop for the First Time 35Certificate Checking Modes for Horizon View Client 37Switch Desktops 38Log Off or Disconnect from a Desktop 38Roll Back a Desktop 39

4 Using a Microsoft Windows Desktop on a Linux System 41Feature Support Matrix for Linux 41Internationalization 42Keyboards and Monitors 42Using the Real-Time Audio-Video Feature for Webcams and Microphones 44Set Printing Preferences for the Virtual Printer Feature 47Copying and Pasting Text 48

5 Troubleshooting Horizon View Client 49Reset a Desktop 49Uninstalling Horizon View Client 49

6 Configuring USB Redirection on the Client 51Setting USB Configuration Properties 51USB Device Families 55

VMware, Inc. 3

Using the View Client 1.5 Command-Line Option to Redirect USB Devices 56

Index 59


4 VMware, Inc.


This guide, Using VMware Horizon View Client for Linux, provides information about installing and usingVMware Horizon View 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 usingHorizon View Client for Linux.This information is intended for administrators who need to set up a Horizon View deployment thatincludes Linux client systems. The information is written for experienced system administrators who arefamiliar with virtual machine technology and datacenter operations.NOTE This document pertains to the Horizon View Client for Linux that VMware makes available onUbuntu. In addition, several VMware partners offer thin client devices for Horizon View deployments. Thefeatures that are available for each thin client device, and the operating systems supported, are determinedby the vendor and model and the configuration that an enterprise chooses to use. For information about thevendors and models for thin client devices, see the VMware Compatibility Guide, available on the VMwareWeb site.

VMware, Inc. 5


6 VMware, Inc.

System Requirements andInstallation 1

Client systems must meet certain hardware and software requirements. The process of installing ViewClient is like installing most other applications.n System Requirements on page 8

The Linux PC or laptop on which you install Horizon View Client, and the peripherals it uses, mustmeet certain system requirements.

n System Requirements for Real-Time Audio-Video on page 9Real-Time Audio-Video works with standard webcam, USB audio, and analog audio devices, andwith standard conferencing applications like Skype, WebEx, and Google Hangouts. To support Real-Time Audio-Video, your Horizon View deployment must meet certain software and hardwarerequirements.

n Supported Desktop Operating Systems on page 10Administrators create virtual machines with a guest operating system and install View Agent in theguest operating system. End users can log in to these virtual machines from a client device.

n Requirements for Using Flash URL Redirection on page 10Streaming Flash content directly from Adobe Media Server to client endpoints lowers the load on thedatacenter ESXi host, removes the extra routing through the datacenter, and reduces the bandwidthrequired to simultaneously stream live video events to multiple client endpoints.

n Preparing View Connection Server for Horizon View Client on page 11Administrators must perform specific tasks to enable end users to connect to remote desktops.

n Install Horizon View Client for Linux on page 11End users open Horizon View Client to connect to remote desktops from a physical machine.Horizon View Client for Linux runs on Ubuntu 12.04 systems, and you install it by using the SynapticPackage Manager.

n Configure the View Client Download Links Displayed in View Portal on page 12By default, when you open a browser and enter the URL of a View Connection Server instance, theportal page that appears contains links to the VMware Download site for downloadingHorizon View Client. You can change the default .

n Horizon View Client Data Collected by VMware on page 13If your company participates in the customer experience improvement program, VMware collects datafrom certain Horizon View Client fields. Fields containing sensitive information are made anonymous.

VMware, Inc. 7

System RequirementsThe Linux PC or laptop on which you install Horizon View Client, and the peripherals it uses, must meetcertain system requirements.NOTE These system requirements pertain to the Horizon View Client for Linux that VMware makesavailable on Ubuntu. In addition, several VMware partners offer thin client devices for Horizon Viewdeployments. The features that are available for each thin client device, and the operating systemssupported, are determined by the vendor and model and the configuration that an enterprise chooses to use.For information about the vendors and models for thin client devices, see the VMware Compatibility Guide,available on the VMware Web site.

Model Intel-based desktop or laptop computerMemory At least 2GB of RAMOperating systems n View Client 2.0 and later: 32-bit Ubuntu Linux 12.04

n View Client 1.6 and 1.7: 32-bit Ubuntu Linux 10.04 or 12.04n View Client 1.5: 32-bit Ubuntu Linux 10.04 or 10.10

View ConnectionServer, Security Server,and View Agent

Latest maintenance release of VMware View 4.6.x and later releasesIf client systems connect from outside the corporate firewall, VMwarerecommends that you use a security server. With a security server, clientsystems will not require a VPN connection.

Display protocol forHorizon View

PCoIP or RDPIMPORTANT Although Horizon View Client for Linux supports the RDPdisplay protocol, the particular RDP client that ships with your distributionof Ubuntu might not work with Horizon View Client.

Screen resolution onclient system

Minimum: 1024 X 768 pixels

Hardware Requirementsfor PCoIP

n x86-based processor with SSE2 extensions, with a 800MHz or higherprocessor speed.

n Available RAM above system requirements to support various monitorsetups. 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 Requirementsfor RDP

n x86-based processor with SSE2 extensions, with a 800MHz or higherprocessor speed.

n 128MB RAM.Software Requirementsfor Microsoft RDP

n For Ubuntu 12.04, use rdesktop 1.7.0.


8 VMware, Inc.

n For Ubuntu 10.04, use rdesktop 1.6.0.Software Requirementsfor FreeRDP

If you plan to use an RDP connection to View desktops and you wouldprefer to use a FreeRDP client for the connection, you must install the correctversion of FreeRDP and any applicable patches. See Install and ConfigureFreeRDP, on page 32.

System Requirements for Real-Time Audio-VideoReal-Time Audio-Video works with standard webcam, USB audio, and analog audio devices, and withstandard conferencing applications like Skype, WebEx, and Google Hangouts. To support Real-Time Audio-Video, your Horizon View deployment must meet certain software and hardware requirements.Horizon View remotedesktop

The desktops must have View Agent 5.2 or later installed. The desktops mustalso have the corresponding Remote Experience Agent installed. Forexample, if View Agent 5.3 is installed, you must also install the RemoteExperience Agent from Horizon View 5.3 Feature Pack 1. See theVMware Horizon View Feature Pack Installation and Administration documentfor VMware Horizon View

Horizon View Clientsoftware

Horizon View Client 2.2 for Linux or a later release. Note that this feature isavailable only with the version of Horizon View Client for Linux providedby third-party vendors.

Horizon View Clientcomputer or clientaccess device

n Real-Time Audio-Video is supported on x86 devices. This feature is notsupported on ARM processors. The client system processor must have atleast two cores.

n Horizon View Client requires the following libraries:n Video4Linux2

n libv4l

n Pulse Audio

The plug-in file /usr/lib/pcoip/vchan_plugins/libmmredir_plugin.sohas the following dependencies.:libuuid.so.1

libv4l2.so.0

libspeex.so.1

libudev.so.0

libtheoradec.so.1

libtheoraenc.so.1

libv4lconvert.so.0

libjpeg.so.8

All of these files must be present on the client system or the Real-TimeAudio-Video feature will not work. Note that these dependencies are inaddition to the dependencies required for Horizon View Client itself.

Chapter 1 System Requirements and Installation

VMware, Inc. 9

n The webcam and audio device drivers must be installed, and thewebcam and audio device must be operable, on the client computer. Tosupport Real-Time Audio-Video, you do not have to install the devicedrivers on the desktop operating system where View Agent is installed.

Display protocol forHorizon View

PCoIPReal-Time Audio-Video is not supported in RDP desktop sessions.

Supported Desktop Operating SystemsAdministrators create virtual machines with a guest operating system and install View Agent in the guestoperating system. End users can log in to these virtual machines from a client device.For a list of the supported guest operating systems, see the "Supported Operating Systems for View Agent"topic in the Horizon View 4.6.x or 5.x installation documentation.

Requirements for Using Flash URL RedirectionStreaming Flash content directly from Adobe Media Server to client endpoints lowers the load on thedatacenter ESXi host, removes the extra routing through the datacenter, and reduces the bandwidthrequired 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 pageadministrator. 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 theclient endpoint. The endpoint then opens a local VMware Flash Projector outside of the virtual desktopsession and plays the media stream locally.This feature is available when used in conjunction with the correct version of VMware Horizon ViewFeature Pack.n Multicast support requires VMware Horizon View 5.2 Feature Pack 2 or later.n Unicast support requires VMware Horizon View 5.3 Feature Pack 1 or later.To use this feature, you must set up your Web page and your client devices. Client systems must meetcertain software requirements:n For multicast support, client systems must use Horizon View Client 2.1 or later. For unicast support,

client systems must use Horizon View Client 2.2 or later.NOTE This feature is supported only on the version of Horizon View Client provided by partners andonly on x86 thin client devices. This feature is not supported on ARM processors.

n Client systems must have IP connectivity to the Adobe Web server that hosts the ShockWave File (SWF)that initiates the multicast or unicast streaming. If needed, configure your firewall to open theappropriate ports to allow client devices to access this server.

n Client systems must have the appropriate Flash plug-in installed.a Install the libexpat.so.0 file, or verify that this file is already installed.

Ensure that the file is installed in the /usr/lib or /usr/local/lib directory.b Install the libflashplayer.so file, or verify that this file is already installed.

Ensure that the file is installed in the appropriate Flash plug-in directory for your Linux operatingsystem.

c Install the wget program, or verify that the program file is already installed.


10 VMware, Inc.

For a list of the View desktop requirements for Flash URL redirection, and for instructions about how toconfigure a Web page to provide a multicast or unicast stream, see the VMware Horizon View Feature PackInstallation and Administration document.

Preparing View Connection Server for Horizon View ClientAdministrators must perform specific tasks to enable end users to connect to remote desktops.Before end users can connect to View Connection Server or a security server and access a remote desktop,you must configure certain pool settings and security settings:n If you are using a security server, as VMware recommends, verify that you are using the latest

maintenance releases of View Connection Server 4.6.x and View Security Server 4.6.x or later releases.See the VMware Horizon View Installation documentation.

n If you plan to use a secure tunnel connection for client devices and if the secure connection isconfigured with a DNS host name for View Connection Server or a security server, verify that the clientdevice can resolve this DNS name.To enable or disable the secure tunnel, in View Administrator, go to the Edit View Connection ServerSettings dialog box and use the check box called Use secure tunnel connection to desktop.

n Verify that a desktop pool has been created and that the user account that you plan to use is entitled toaccess the remote desktop. See the topics about creating desktop pools in the VMware Horizon ViewAdministration documentation.

n To use two-factor authentication with Horizon View Client, such as RSA SecurID or RADIUSauthentication, you must enable this feature on View Connection Server. RADIUS authentication isavailable with View 5.1 or later View Connection Server. For more information, see the topics abouttwo-factor authentication in the VMware Horizon View Administration documentation.

Install Horizon View Client for LinuxEnd users open Horizon View Client to connect to remote desktops from a physical machine.Horizon View Client for Linux runs on Ubuntu 12.04 systems, and you install it by using the SynapticPackage Manager.IMPORTANT Customers using Linux-based thin clients must contact their thin client vendor forHorizon View Client updates. Customers who have successfully built their own Linux-based endpoints andneed an updated client must contact their VMware sales representative.

Prerequisitesn Verify that the client system uses a supported operating system. See System Requirements, on page 8.n Verify that you can log in as an administrator on the client system.n If you plan to use the RDP display protocol to connect to a View desktop, verify that you have the

appropriate RDP client installed. See System Requirements, on page 8.Procedure1 On your Linux laptop or PC, enable Canonical Partners.

a From the Ubuntu menu bar, select System > Administration > Update Manager.b Click the Settings button 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.


VMware, Inc. 11

2 Download the package from the Ubuntu Software Center, as follows.a From the Ubuntu menu bar, select System > Administration > Synaptic Package Managerb Click Search and search for vmware.c In the list of packages returned, select the check box next to vmware-view-client and select Mark

for Installation.d Click Apply in the toolbar.

If your operating system is Ubuntu 12.04, the latest version of Horizon View Client is installed. Ifyour operating system is Ubuntu 10.04, View Client for Linux 1.7 is installed.

3 To determine that installation succeeded, verify that the VMware Horizon View application iconappears in the Applications > Internet menu.

What to do nextStart Horizon View Client and verify that you can log in to the correct virtual desktop. See Log In to aRemote Desktop for the First Time, on page 35.

Configure the View Client Download Links Displayed in View PortalBy default, when you open a browser and enter the URL of a View Connection Server instance, the portalpage that appears contains links to the VMware Download site for downloading Horizon View Client. Youcan change the default .The default Horizon View Client links on portal page ensure that you are directed to the latest compatibleHorizon View Client installers. In some cases, however, you might want to have the links point to aninternal Web server, or you might want to make specific client versions available on your own ViewConnection Server. You can reconfigure the page to point to a different URL.When you make links for Mac OS X, Linux, and Windows client systems, the correct operating systemspecific link is shown on the portal page. For example, if you browse to the portal page from a Windowssystem, only the link or links for Windows installers appear. You can make separate links for 32-bit and 64-bit installers. You can also make links for iOS and Android systems, but these operating systems are notautomatically detected, so that if you browse to the portal page from an iPad, for example, you see the linksfor both iOS and Android, if you created links for both.IMPORTANT If you customize the portal page links, as described in this topic, and later installVMware Horizon View HTML Access on the server, your customized portal page is replaced by anHTML Access page. For information about customizing that page, see UsingVMware Horizon View HTML Access.

Prerequisitesn Download the installer files for the Horizon View Client types that you want to use in your

environment. The URL to the client download page is https://www.vmware.com/go/viewclients.n Determine which HTTP server will host the installer files. The files can reside on a View Connection

Server instance or on another HTTP server.Procedure1 On the HTTP server where the installer files will reside, create a folder for the installer files.

For example, to place the files in a downloads folder on the View Connection Server host, in the defaultinstallation directory, use the following path:C:\Program Files\VMware\VMware View\Server\broker\webapps\downloads


12 VMware, Inc.

The links to the files would then use URLs with the format https://server-name/downloads/client-installer-file-name. For example, a server with the name view.mycompany.com might use the followingURL for View Client for Windows: https://view.mycompany.com/downloads/VMware-Horizon-View-Client.exe. In this example, the folder named downloads is located in the webapps root folder.

2 Copy the installer files into the folder.If the folder resides on View Connection Server, you can replace any files in this folder without havingto restart the VMware View Connection Server service.

3 On the View Connection Server machine, copy the portal-links.properties file and theportal.properties file located in install-path\Server\Extras\PortalExamples.

4 Create a portal folder the directory C:\ProgramData\VMware\VDM, and copy the portal-links.properties and portal.properties files into the portal folder.

5 Edit C:\ProgramData\VMware\VDM\portal\portal-links.properties file to point to the new location ofthe installer files.You can edit the lines in this file and add to them if you need to create more links. You can also deletelines.The following examples show properties for creating two links for View Client for Windows and twolinks for View Client for Linux:link.win=https://server-name/downloads/VMware-Horizon-View-Client-x86_64-y.y.y-XXXX.exe#win

link.win.1=https://server-name/downloads/VMware-Horizon-View-Client-y.y.y-XXXX.exe#win

link.linux=https://server-name/downloads/VMware-Horizon-View-Client-x86_64-y.y.y-

XXXX.rpm#linux

link.linux.1=https://server-name/downloads/VMware-Horizon-View-Client-y.y.y-XXXX.tar.gz#linux

In this example, y.y.y-XXXX indicates the version and build number. The win text at the end of the lineindicates that this link should appear in the browser if the client has a Windows operating system. Usewin for Windows, linux for Linux, and mac for Mac OS X. For other operating systems, use unknown.

6 Edit C:\ProgramData\VMware\VDM\portal\portal.properties file to specify the text to display for thelinks.These lines appear in the section of the file called # keys based on key names in portal-links.properties.The following example shows the text that corresponds to the links specified for link.win andlink.win.1:text.win=View Client for Windows 32 bit Client users

text.win.1=View Client for Windows 64 bit Client users

7 Restart the VMware View Connection Server service.

When end users enter the URL for View Connection Server, they see links with the text you specified. Thelinks point to the locations you specified.

Horizon View Client Data Collected by VMwareIf your company participates in the customer experience improvement program, VMware collects data fromcertain Horizon View Client fields. Fields containing sensitive information are made anonymous.NOTE This feature is available only if your Horizon View deployment uses View Connection Server 5.1 orlater. Client information is sent for View Client 1.7 and later clients.


VMware, Inc. 13

VMware collects data on the clients to prioritize hardware and software compatibility. If your company'sadministrator has opted to participate in the customer experience improvement program, VMware collectsanonymous data about your deployment in order to improve VMware's response to customer requirements.No data that identifies your organization is collected. Horizon View Client information is sent first to ViewConnection Server and then on to VMware, along with data from Horizon View servers, desktop pools, andremote desktops.Although the information is encrypted while in transit to View Connection Server, the information on theclient system is logged unencrypted in a user-specific directory. The logs do not contain any personallyidentifiable information.To participate in the VMware customer experience improvement program, the administrator who installsView Connection Server can opt in while running the View Connection Server installation wizard, or anadministrator can set an option in View Administrator after the installation.Table 11. Data Collected from Horizon View Clients for the Customer Experience Improvement Program

DescriptionIs This Field MadeAnonymous? Example Value

Company that produced theHorizon View Client application

No VMware

Product name No VMware Horizon View ClientClient product version No The format is x.x.x-yyyyyy, where x.x.x is the client version

number and yyyyyy is the build number.Client binary architecture No Examples include the following:

n i386n x86_64n arm

Client build name No Examples include the following:n VMware-Horizon-View-Client-Win32-Windowsn VMware-Horizon-View-Client-Linuxn VMware-Horizon-View-Client-iOSn VMware-Horizon-View-Client-Macn VMware-Horizon-View-Client-Androidn VMware-Horizon-View-Client-WinStore

Host operating system No Examples include the following:n Windows 8.1n Windows 7, 64-bit Service Pack 1 (Build 7601 )n iPhone OS 5.1.1 (9B206)n Ubuntu 10.04.4 LTSn Mac OS X 10.7.5 (11G63)

Host operating system kernel No Examples include the following:n Windows 6.1.7601 SP1n Darwin Kernel Version 11.0.0: Sun Apr 8 21:52:26 PDT

2012; root:xnu-1878.11.10~1/RELEASE_ARM_S5L8945Xn Darwin 11.4.2n Linux 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24

17:27:10 UTC 2012n unknown (for Windows Store)

Host operating systemarchitecture

No Examples include the following:n x86_64n i386n armv71n ARM


14 VMware, Inc.

Table 11. Data Collected from Horizon View Clients for the Customer Experience Improvement Program(Continued)

DescriptionIs This Field MadeAnonymous? Example Value

Host system model No Examples include the following:n Dell Inc. OptiPlex 960n iPad3,3n MacBookPro8,2n Dell Inc. Precision WorkStation T3400 (A04 03/21/2008)

Host system CPU No Examples include the following:n Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHn Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHn unknown (for iPad)

Number of cores in the hostsystem's processor

No For example: 4

MB of memory on the host system No Examples include the following:n 4096n unknown (for Windows Store)


VMware, Inc. 15


16 VMware, Inc.

Configuring Horizon View Client forEnd Users 2

Horizon View Client provides several configuration mechanisms to simplify the login and desktop selectionexperience for end users, and also to enforce security policies.The following table shows some of the configuration settings that you can set in any of several ways. Formany other configuration settings, you must use a particular mechanism. For example, to use the setting forDisable Toaster Notifications, you must use a Group Policy setting..Table 21. Common Configuration SettingsSetting Mechanisms for ConfiguringView Connection Server address URI, Group Policy, Command Line, Windows RegistryActive Directory user name URI, Group Policy, Command Line, Windows RegistryLog in as current user Group Policy, Command LineDomain name URI, Group Policy, Command Line, Windows RegistryDesktop display name URI, Group Policy, Command LineWindow size URI, Group Policy, Command LineDisplay protocol URI, Command LineOptions for redirecting USB devices URI, Group Policy, Command LineConfiguring certificate checking Group Policy, Windows RegistryConfiguring SSL protocols andcryptographic algorithms

Group Policy, Windows Registry

This chapter includes the following topics:n Using URIs to Configure Horizon View Client, on page 18n Using the View Client Command-Line Interface and Configuration Files, on page 21n Using FreeRDP for RDP Connections, on page 32n Enabling FIPS Mode on the Client, on page 33n Configuring the PCoIP Client-Side Image Cache, on page 33

VMware, Inc. 17

Using URIs to Configure Horizon View ClientUsing uniform resource identifiers (URIs), you can create a Web page or an email with links that end usersclick to launch Horizon View Client, connect to View Connection Server, and launch a specific desktop withspecific configuration options.You can simplify the process of logging in to a remote desktop by creating Web or email links for end users.You create these links by constructing URIs that provide some or all of the following information, so thatyour end users do not need to supply it:n View Connection Server addressn Port number for View Connection Servern Active Directory user namen Domain namen Desktop display namen Window sizen Desktop actions, including reset, log off, and start sessionn Display protocolTo construct a URI, you use the vmware-view URI scheme with Horizon View Client specific path and queryparts.NOTE You can use URIs to launch Horizon View Client only if the client software is already installed onend users' client computers.

Syntax for Creating vmware-view URIsSyntax includes the vmware-view URI scheme, a path part to specify the desktop, and, optionally, a query tospecify desktop actions or configuration options.

VMware Horizon View URI SpecificationWhen you create a URI, you are essentially calling vmware-view with the full View URI string as anargument.Use the following syntax to create URIs for launching Horizon View 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 operatingsystems, the scheme name is case-sensitive. Therefore, use vmware-view.IMPORTANT In all parts, non-ASCII characters must first be encoded according to UTF-8 [STD63], and theneach octet of the corresponding UTF-8 sequence must be percent-encoded to be represented as URIcharacters.For information about encoding for ASCII characters, see the URL encoding reference at http://www.utf8-chartable.de/.

authority-part Specifies the server address and, optionally, a user name, a non-default portnumber, or both. Server names must conform to DNS syntax.To specify a user name, use the following syntax:user1@server-address


18 VMware, Inc.

Note that you cannot specify a UPN address, which includes the domain. Tospecify 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 Specifies the desktop. Use the desktop display name. If the display name hasa space in it, use the %20 encoding mechanism to represent the space.

query-part Specifies the configuration options to use or the desktop actions to perform.Queries are not case-sensitive. To use multiple queries, use an ampersand(&) between the queries. If queries conflict with each other, the last query inthe list is used. Use the following syntax:query1=value1[&query2=value2...]

Supported QueriesThis topic lists the queries that are supported for this type of Horizon View Client. If you are creating URIsfor multiple types of clients, such as desktop clients and mobile clients, see the UsingVMware Horizon View Client guide for each type of client system.action Table 22. Values That Can Be Used with the action Query

Value Descriptionbrowse Displays a list of available desktops hosted on the specified server.

You are not required to specify a desktop when using this action.start-session Launches the specified desktop. If no action query is provided and

the desktop name is provided, start-session is the defaultaction.

reset Shuts down and restarts the specified desktop. Unsaved data islost. Resetting a remote desktop is the equivalent of pressing theReset button on a physical PC.

logoff Logs the user out of the guest operating system in the remotedesktop.

rollback Discards changes made to the specified desktop while it waschecked out for use in local mode on a Windows PC or laptop.

connectUSBOnInsert (The USB component is included only with the Horizon View Clientavailable from third-party vendors.) Connects a USB device to theforeground desktop when you plug in the device. This query is implicitly setif you specify the unattended query. To use this query, you must set theaction query to start-session or else not have an action query. Valid valuesare yes and no. An example of the syntax is connectUSBOnInsert=yes.

connectUSBOnStartup (The USB component is included only with the Horizon View Clientavailable from third-party vendors.) Redirects all USB devices to the desktopthat are currently connected to the client system. This query is implicitly setif you specify the unattended query. To use this query, you must set theaction query to start-session or else not have an action query. Valid valuesare yes and no. An example of the syntax is connectUSBOnStartup=yes.

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

Chapter 2 Configuring Horizon View Client for End Users

VMware, Inc. 19

Table 23. Valid Values for the desktopLayout QueryValue Descriptionfullscreen Full screen on one monitor. This is the default.multimonitor Full screen on all monitors.windowLarge Large window.windowSmall Small window.WxH Custom resolution, where you specify the width by height,

in pixels. An example of the syntax isdesktopLayout=1280x800.

desktopProtocol Valid values are RDP and PCoIP. For example, to specify PCoIP, use the syntaxdesktopProtocol=PCoIP.

domainName The domain associated with the user who is connecting to the remotedesktop.

Examples of vmware-view URIsYou can create hypertext links or buttons with the vmware-view URI scheme and include these links in emailor on a Web page. Your end users can click these links to, for example, launch a particular remote desktopwith the startup options you specify.

URI Syntax ExamplesEach URI example is followed by a description of what the end user sees after clicking the URI link.1 vmware-view://view.mycompany.com/Primary%20Desktop?action=start-session

Horizon View Client is launched and connects to the view.mycompany.com server. The login box promptsthe user for a user name, domain name, and password. After a successful login, the client connects tothe desktop whose display name is displayed as Primary Desktop, and the user is logged in to theguest operating system.NOTE 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 View Client Command-Line Interface and ConfigurationFiles, on page 21.

2 vmware-view://view.mycompany.com:7555/Primary%20DesktopThis URI has the same effect as the previous example, except that it uses the nondefault port of 7555 forView Connection Server. (The default port is 443.) Because a desktop identifier is provided, the desktopis launched even though the start-session action is not included in the URI.

3 vmware-view://[email protected]/Finance%20Desktop?desktopProtocol=PCoIPHorizon View Client is launched and connects to the view.mycompany.com server. In the login box, theUser name text box is populated with the name fred. The user must supply the domain name andpassword. After a successful login, the client connects to the desktop whose display name is displayedas Finance Desktop, and the user is logged in to the guest operating system. The connection uses thePCoIP display protocol.

4 vmware-view://[email protected]/Finance%20Desktop?domainName=mycompany


20 VMware, Inc.

Horizon View Client is launched and connects to the view.mycompany.com server. In the login box, theUser name text box is populated with the name fred, and the Domain text box is populated withmycompany. The user must supply only a password. After a successful login, the client connects to thedesktop whose display name is displayed as Finance Desktop, and the user is logged in to the guestoperating system.

5 vmware-view://view.mycompany.com/Horizon View Client is launched, and the user is taken to the login prompt for connecting to theview.mycompany.com server.

6 vmware-view://view.mycompany.com/Primary%20Desktop?action=resetHorizon View Client is launched and connects to the view.mycompany.com server. The login box promptsthe user for a user name, domain name, and password. After a successful login, Horizon View Clientdisplays a dialog box that prompts the user to confirm the reset operation for Primary Desktop. Afterthe reset occurs, depending on the type of client, the user might see a message indicating whether thereset was successful.NOTE This action is available only if the View administrator has enabled this feature for end users.

7 vmware-view://Horizon View Client is launched, and the user is taken to the page for entering the address of a ViewConnection Server instance.

HTML Code ExamplesYou can use URIs to make hypertext links and buttons to include in emails or on Web pages. The followingexamples show how to use the URI from the first URI example to code a hypertext link that says, Test Link,and a button that says, TestButton.

Test

Link

Using the View Client Command-Line Interface and ConfigurationFiles

You can configure View Client using command-line options or equivalent properties in a configuration file.You can use the vmware-view command-line interface or set properties in configuration files to define defaultvalues your users see in View Client or to suppress some dialog boxes from prompting users forinformation. You can also specify settings that you do not want users to change.

Processing Order for Configuration SettingsWhen View Client starts up, configuration settings are processed from various locations in the followingorder:1 /etc/vmware/view-default-config


VMware, Inc. 21

2 ~/.vmware/view-preferences3 Command-line arguments4 /etc/vmware/view-mandatory-configIf a setting is defined in multiple locations, the value that is used is the value from the last file or command-line option read. For example, to specify settings that override users' preferences, set properties inthe /etc/vmware/view-mandatory-config file.To set default values that users can change, use the /etc/vmware/view-default-config file. After userschange a setting, when they exit View Client, any changed settings are saved in the ~/.vmware/view-preferences file.

Properties That Prevent Users from Changing DefaultsFor each property, you can set a corresponding view.allow property that controls whether users areallowed to change the setting. For example, if you set the view.allowDefaultBroker property to "FALSE"in the /etc/vmware/view-mandatory-config file, users will not be able to change the name in the ServerName field when they use View Client.

Syntax for Using the Command-Line InterfaceUse 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 shortform. 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.IMPORTANT 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 forthe proxy. If you do not perform this action, the proxy exception setting does not take effect in View Client.You configure a proxy exception for the View Connection Server instance.

View Client Configuration Settings and Command-Line OptionsFor your convenience, almost all configuration settings have both a key=value property and a correspondingcommand-line option name. For a few settings, there is a command-line option but no correspondingproperty you can set in a configuration file. For a few other settings, you must set a property because nocommand-line option is available.IMPORTANT Some command-line options and configuration keys, such as the ones for USB redirection andMMR, are available only with the version of View Client provided by third-party vendors. For moreinformation about VMware thin-client and zero-client partners, see the VMware Compatibility Guide at http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm.


22 VMware, Inc.

Table 24. View Client Command-Line Options and Configuration File KeysConfiguration Key Command-Line Option Descriptionview.allMonitors --allmonitors Hides the host operating system and

opens the View Client user interface infull screen mode across all monitors thatare connected when View Client islaunched.If you are setting the configuration key,specify "TRUE" or "FALSE". Default is"FALSE".

view.allowDefaultBroker -l, --lockServerExample:--lockServer -s view.company.com

Using this command-line option, orsetting the property to "FALSE", disablesthe Server Name field unless the clienthas never connected to any server, andno server address is provided in thecommand line or the preferences file.

view.autoConnectBroker None Automatically connects to the last Viewserver used unless theview.defaultBroker configurationproperty is set or unless the--serverURL= command-line option isused.Specify "TRUE" or "FALSE". Default is"FALSE".Setting this property and theview.autoConnectDesktop property to"TRUE" is the equivalent of setting theview.nonInteractive property to"TRUE".

view.autoConnectDesktop None Automatically connects to the last Viewdesktop used unless theview.defaultDesktop configurationproperty is set or unless the--desktopName= command-line optionis used.Specify "TRUE" or "FALSE". Default is"FALSE".Setting this property and theview.autoConnectBroker property to"TRUE" is the equivalent of setting theview.nonInteractive property to"TRUE".

view.defaultBroker -s, --serverURL=Examples:--serverURL=https://view.company.com-s view.company.com--serverURL=view.company.com:1443

Adds the name that you specify to theServer Name field in View Client.Specify a fully qualified domain name.You can also specify a port number if youdo not use the default 443.Default is the most recently used value.

view.defaultDesktop -n, --desktopName= Specifies which desktop to use whenautoConnectDesktop is set to "TRUE"and the user has access to multipledesktops.This is the name you would see in theSelect Desktop dialog box. The name isusually the pool name.

view.defaultDesktopHeight None Specifies the default height of thewindow for the View desktop, in pixels.


VMware, Inc. 23

Table 24. View Client Command-Line Options and Configuration File Keys (Continued)Configuration Key Command-Line Option Descriptionview.defaultDesktopSize --desktopSize=

Examples:--desktopSize="1280x800"--desktopSize="all"

Sets the default size of the window forthe View desktop:n To use all monitors, set the property

to "1" or use the command-lineargument "all".

n To use full screen mode on onemonitor, set the property to "2" oruse the command-line argument"full".

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

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

n To set a custom size, set the propertyto "5"and then also set theview.defaultDesktopWidth andview.defaultDesktopHeightproperties. Alternatively, specify thewidth by height, in pixels, at thecommand-line as "widthxheight".

view.defaultDesktopWidth None Specifies the default width of thewindow for the View desktop, in pixels.

view.defaultDomain -d, --domainName= Sets the domain name that View Clientuses for all connections and adds thedomain name that you specify to theDomain Name field in View Clientauthentication dialog box.

view.defaultPassword -p "-", --password="-" For PCoIP and rdesktop connections,always specify "-" to read the passwordfrom stdin.Sets the password that View Client usesfor all connections and adds thepassword to the Password field in ViewClient authentication dialog box if ViewConnection Server accepts passwordauthentication.NOTE You cannot use a blank password.That is, you cannot specify --password=""

view.defaultProtocol --protocol= Specifies which display protocol to use.Specify "PCOIP" or "RDP". These valuesare case-sensitive. For example, if youenter rdp the protocol used will be thedefault. Default is the setting specified inView Administrator, under pool settingsfor the pool.If you use RDP and you want to useFreeRDP rather than rdesktop, youmust also use the rdpClient setting.


24 VMware, Inc.

Table 24. View Client Command-Line Options and Configuration File Keys (Continued)Configuration Key Command-Line Option Descriptionview.defaultUser -u, --userName= Sets the user name that View Client uses

for all connections and adds the username that you specify to the User Namefield in View Client authentication dialogbox.For kiosk mode, the account name can bebased on the client's MAC address, or itcan begin with a recognized prefix string,such as custom-.

view.fullScreen --fullscreen Hides the host operating system andopens the View Client user interface infull screen mode on one monitor. Thisoption does not affect the screen mode ofthe desktop session.If you are setting the configuration key,specify "TRUE" or "FALSE". Default is"FALSE".

view.kbdLayout -k, --kbdLayout=rdesktop examples:--kbdLayout="en-us"-k "fr"

freerdp example:-k "0x00010407"

Specifies which locale to use for thekeyboard layout.NOTE rdesktop uses locale codes, suchas "fr" and "de", whereas freerdp useskeyboard layout IDs. For a list of theseIDs, use the following command:xfreerdp --kbd-list

view.kioskLogin --kioskLogin

Example: See the kiosk mode example thatfollows this table.

Specifies that View client is going toauthenticate using a kiosk mode account.If you are setting the configuration key,specify "TRUE" or "FALSE". Default is"FALSE".

view.mmrPath -m, --mmrPath=Example:--mmrPath="/usr/lib/altmmr"

(Available only with distributions fromthird-party vendors) Specifies the path tothe directory that contains the WyseMMR (multimedia redirection) libraries.

view.nomenubar --nomenubar Suppresses the View Client menu barwhen View Client is in full screen mode,so that users cannot access menu optionsto log off of, reset, or disconnect from aView desktop. Use this option whenconfiguring kiosk mode.If you are setting the configuration key,specify "TRUE" or "FALSE". Default is"FALSE".

view.nonInteractive -q, --nonInteractiveExample:--nonInteractive--serverURL="https://view.company.com" --userName="user1" --password="-" --domainName="xyz" --desktopName="Windows 7"

Hides unnecessary UI steps from endusers by skipping the screens that arespecified in the command line orconfiguration properties.If you are setting the configuration key,specify "TRUE" or "FALSE". Default is"FALSE".Setting this property to "TRUE" is theequivalent of setting theview.autoConnectBroker andview.autoConnectDesktop propertiesto "TRUE".


VMware, Inc. 25

Table 24. View Client Command-Line Options and Configuration File Keys (Continued)Configuration Key Command-Line Option Descriptionview.once --once Specifies that you do not want View

Client to retry connecting in the case ofan error occurring.Use --once if you want to obtain asimilar workflow to the View 4.6 client.This option will force the View client toexit after the user disconnects or logs offfrom a desktop.You should usually specify this option ifyou use kiosk mode, and use the exitcode to handle the error. Otherwise, youmight find it difficult to kill the vmware-view process remotely.If you are setting the configuration key,specify "TRUE" or "FALSE". Default is"FALSE".

view.rdesktopOptions --rdesktopOptions=

Example:--rdesktopOptions="-f -m"

(Available if you use the Microsoft RDPdisplay protocol) Specifies command-lineoptions to forward to the rdesktopapplication. For information aboutrdesktop options, see the rdesktopdocumentation.

None -r, --redirect=Example:--redirect="sound:off"

(Available if you use the Microsoft RDPdisplay protocol) Specifies a local devicethat you want rdesktop to redirect to theView desktop.Specify the device information that youwant to pass to the -r option of rdesktop.You can set multiple device options in asingle command.

view.rdpClient --rdpclient= (Available if you use the Microsoft RDPdisplay protocol) Specifies which type ofRDP client to use. The default isrdesktop. To use FreeRDP instead,specify xfreerdp.NOTE To use FreeRDP, you must havethe correct version of FreeRDP installed,along with any applicable patches. Formore information, see Install andConfigure FreeRDP, on page 32.

None --save (Available if you use View Client 2.2 orlater) Saves the user name and domainname that were last used to successfullylog in so that you do not need to enterthe user name or domain name the nexttime you are prompted to supply logincredentials.


26 VMware, Inc.

Table 24. View Client Command-Line Options and Configuration File Keys (Continued)Configuration Key Command-Line Option Descriptionview.sendCtrlAltDelToLocal None (Available if you use the PCoIP display

protocol and View Client 2.1 or later)When set to "TRUE", sends the keycombination Ctrl+Alt+Del to the clientsystem rather than opening a dialog boxto prompt the user to disconnect from theView desktop. Default is "FALSE".NOTE If you use the Microsoft RDPdisplay protocol, you can achieve thisfunctionality by using the -K option; forexample, vmware-view -K.You can also configure this keycombination by using the view-keycombos-config file, as describedin Configuring Specific Keys and KeyCombinations to Send to the LocalSystem, on page 29.

view.sendCtrlAltInsToVM None (Available if you use the PCoIP displayprotocol and View Client 2.1 or later)When set to "TRUE", sends the keycombination Ctrl+Alt+Ins to the virtualdesktop rather than sending Ctrl+Alt+Del. Default is "FALSE".NOTE To use this feature, you must alsoset the agent-side GPO policy called "Usealternate key for sending SecureAttention Sequence," available in thepcoip.adm template. See the topic called"View PCoIP Session Variables for theKeyboard" in the "Configuring Policies"chapter of the VMware Horizon ViewAdministration document.

view.sslVerificationMode None Sets the server certificate verificationmode.Specify "1" to reject connections whenthe certificate fails any of the verificationchecks, "2" to warn but allowconnections that use a self-signedcertificate, or "3" to allow unverifiableconnections. If you specify "3" noverification checks are performed.Default is "2".

view.xfreerdpOptions --xfreerdpOptions= (Available if you use the Microsoft RDPdisplay protocol) Specifies command-lineoptions to forward to the xfreerdpprogram. For information aboutxfreerdp options, see the xfreerdpdocumentation.NOTE To use FreeRDP, you must havethe correct version of FreeRDP installed,along with any applicable patches. Formore information, see Install andConfigure FreeRDP, on page 32.


VMware, Inc. 27

Table 24. View Client Command-Line Options and Configuration File Keys (Continued)Configuration Key Command-Line Option DescriptionNone --enableNla (Applies if you are using FreeRDP for

RDP connections) Enables network-levelauthentication (NLA). NLA is turned offby default if you are using FreeRDP.You must have the correct version ofFreeRDP installed, along with anyapplicable patches. For moreinformation, see Install and ConfigureFreeRDP, on page 32.NOTE The rdesktop program does notsupport NLA.

None --printEnvironmentInfoExample:--printEnvironmentInfo -s view.company.com

Displays information about theenvironment of a client device, includingits IP address, MAC address, machinename, and domain name.For kiosk mode, you can create anaccount for the client based on the MACaddress. To display the MAC address,you must use this option with the -soption.

None --usb= (Available only with distributions fromthird-party vendors and only for ViewClient 1.5) Specifies which options to usefor USB redirection. SeeUsing the ViewClient 1.5 Command-Line Option toRedirect USB Devices, on page 56.To configure USB options with ViewClient 1.6 and later, see Chapter 6,Configuring USB Redirection on theClient, on page 51.

None --version Displays version information about ViewClient.

Example: Kiosk Mode ExampleKiosk users might include customers at airline check-in stations, students in classrooms or libraries, medicalpersonnel at medical data entry workstations, or customers at self-service points. Accounts are associatedwith client devices rather than users because users do not need to log in to use the client device or the Viewdesktop. 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 Serverinstance and perform several procedures documented in the chapter about kiosk mode in theVMware Horizon View Administration document. After you set up kiosk mode, you can use the vmware-viewcommand 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 thefollowing configuration keys or command-line options.Configuration Key Equivalent Command-line Optionsview.kioskLogin --kioskLogin

view.nonInteractive -q, --nonInteractiveview.fullScreen --fullscreen

view.nomenubar --nomenubar

view.defaultBroker -s, --serverURL=


28 VMware, Inc.

Omitting any of these configuration settings is not supported for kiosk mode. If View Connection Server isset up to require a non-default kiosk user name, you must also set the view.defaultUser property or usethe -u or --userName= command-line option. If a non-default user name is not required and you do notspecify a user name, View Client can derive and use the default kiosk user name.

NOTE If you set the view.sslVerificationMode configuration key, be sure to set it inthe /etc/vmware/view-mandatory-config file. When the client runs in kiosk mode, the client does not look inthe view-preferences file.The command shown in this example runs View Client on a Linux client system and has the followingcharacteristics:n The user account name is based on the client's MAC address.n View Client runs in full screen mode without a View Client menu bar.n Users are automatically connected to the specified View Connection Server instance and View desktop

and are not prompted for login credentials.n 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 displayan out-of-order screen or might wait a certain amount of time before attempting to connect to ViewConnection 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"

IMPORTANT If a pre-login message has been configured to appear before allowing View Client to connect toa View desktop, the user must acknowledge the message before being allowed to access the desktop. Toavoid this issue, use View Administrator to disable pre-login messages.

Configuring Specific Keys and Key Combinations to Send to the Local SystemIf you use the PCoIP display protocol and Horizon View Client 2.2 or later, you can create a view-keycombos-config file to specify which key combinations should not be forwarded to the remote desktop. Ifyou use Horizon View Client 2.3, you can also specify individual keys.You might prefer to have some keys or key combinations handled by your local client system when workingin a remote desktop. For example, you might want to use a particular key combination to start the screensaver on your client computer. Beginning with Horizon View Client 2.2, you can create a file locatedat /etc/vmware/view-keycombos-config and specify the key combinations. If you have Horizon View Client2.3 or later, you can also specify individual keys.Place each key or key combination on a new line using the format shown in the following table.Table 25. Format for Specifying Keys That Must Not Be Forwarded to Remote DesktopsClient Version FormatHorizon View Client 2.2 keyName

IMPORTANT This feature pertains to key combinations and not to single keys. Forexample, you cannot specify only or only keyName.

Horizon View Client 2.3 or later scanCodescanCode

The first example is for a key combination. The second example is for a single key. ThescanCode value is the keyboard scan code, in hexadecimal.


VMware, Inc. 29

In this example, modName is one of four modifier keys: ctrl, alt, shift, and super. The Super key iskeyboard-specific. For example, the Super key is usually the Windows key on a Microsoft Windowskeyboard but is the Command key on a Mac OS X keyboard. If you have Horizon View Client 2.3 or later,you can also use as a wildcard for modName. For example, 0x153 specifies all combinations of theDelete key, including the individual Delete key for the US keyboard. The value you use for modName is notcase-sensitive.

Specifying the Scan Code for a Key in Horizon View Client 2.3 or LaterThe scanCode value must be in hexadecimal format. To determine which code to use, open the appropriatelanguage- and keyboard-specific file in the lib/vmware/xkeymap directory on your client system.The following list shows the example contents of a /etc/vmware/view-keycombos-config file. Codecomments are preceded by the # character.0x152 #block ctrl-insert

15 #block alt-tab

0x153 #block ctrl-alt-del

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

Specifying a Key Name in Horizon View Client 2.2The keyName value is case-sensitive and can be any of the following: the numbers 0 through 9, the functionkeys F1 through F12, lowercase or uppercase letters A through Z, or any of the other keys in the list thatfollows.NOTE In the list that follows, the keys prefixed with KP, such as in KP_Enter, mean keys in the numerickeypad. BackSpace Execute KP_Page_Down quotedbl asciicircumTab Insert KP_End numbersign underscoreLinefeed Undo KP_Begin dollar graveClear Redo KP_Insert percent quoteleftReturn Menu KP_Delete ampersand braceleftPause Find KP_Equal apostrophe barScroll_Lock Cancel KP_Multiply quoteright bracerightSys_Req Help KP_Add quoteleft asciitildeEscape Break KP_Separator parenleftDelete Num_Lock KP_Subtract parenrightMulti_key KP_Space KP_Decimal asteriskCodeinput KP_Tab KP-Divide plusHome KP_Enter KP_0 commaLeft KP_F1 KP_1 minusUp KP_F2 KP_2 periodRight KP_F3 KP_3 slashDown KP_F4 KP_4 colonPrior KP_Home KP_5 less


30 VMware, Inc.

Page_Up KP_Left KP_6 equalNext KP_UP KP_7 greaterPage_Down KP_Right KP_8 questionEnd KP_Down KP_9 atBegin KP_Prior Caps_Lock bracketleftSelect KP_Page_Up space backslashPrint KP_Next exclam bracketrightThe following list shows the example contents of a /etc/vmware/view-keycombos-config file:Delete

Tab

1

h

1

S

h

h

h

space

KP_Enter

Up

Configuring Certificate Checking for End UsersAdministrators can configure the certificate verification mode so that, for example, full verification is alwaysperformed.Certificate checking occurs for SSL connections between View Connection Server and Horizon View Client.Administrators can configure the verification mode to use one of the following strategies:n End users are allowed to choose the verification mode. The rest of this list describes the three

verification modes.n (No verification) No certificate checks are performed.n (Warn) End users are warned if a self-signed certificate is being presented by the server. Users can

choose whether or not to allow this type of connection.n (Full security) Full verification is performed and connections that do not pass full verification are

rejected.For details about the types of verification checks performed, see Certificate Checking Modes for HorizonView Client, on page 37.Use the view.sslVerificationMode property to set the default verification mode:n 1 implements Full Verification.n 2 implements Warn If the Connection May Be Insecure.n 3 implements No Verification Performed.To configure the mode so that end users cannot change the mode, set the view.allowSslVerificationModeproperty to "False" in the /etc/vmware/view-mandatory-config file on the client system. See View ClientConfiguration Settings and Command-Line Options, on page 22.


VMware, Inc. 31

Using FreeRDP for RDP ConnectionsIf you plan to use RDP rather than PCoIP for connections to View desktops, you can choose between usingan 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, View Client 1.7 and later can also runthe xfreerdp executable if your Linux machine has the required version and patches for FreeRDP.You can use the vmware-view command-line interface or some properties in configuration files to specifyoptions for xfreerdp, just as you can for rdesktop.n To specify that View Client should run xfreerdp rather than rdesktop, use the appropriate command-

line option or configuration key. Command-line option: --rdpclient="xfreerdp"Configuration key: view.rdpClient="xfreerdp"

n To specify options to forward to the xfreerdp program, use the appropriate command-line option orconfiguration key, and specify the FreeRDP options. Command-line option: --xfreerdpOptionsConfiguration key: view.xfreerdpOptions

Many configuration options for the rdesktop program are the same as for the xfreerdp program. Oneimportant difference is that xfreerdp supports network-level authentication (NLA). NLA is turned off bydefault. You must use the following command-line option to turn on network-level authentication:--enableNla

For more information about using the vmware-view command-line interface and configuration files, see Using the View Client Command-Line Interface and Configuration Files, on page 21.You must have the correct version of FreeRDP installed, along with any applicable patches. For moreinformation, see Install and Configure FreeRDP, on page 32.

Install and Configure FreeRDPTo use a FreeRDP client for RDP connections to View desktops, your Linux machine must include therequired version and patches for FreeRDP.You must have FreeRDP 1.0.x installed and install the applicable patches so that the --from-stdin and -Xoptions will work correctly.For a list of the packages that xfreerdp depends on in Ubuntu, go to https://github.com/FreeRDP/FreeRDP/wiki/Compilation.Procedure1 On your Linux client machine, download FreeRDP 1.0.x from GitHub, at

https://github.com/FreeRDP/FreeRDP.2 If you install FreeRDP 1.0.1, patch with the file called freerdp-1.0.1.patch, using following patch

command:patch -p1 < freerdp-1.0.1.patch


32 VMware, Inc.

3 To build and install FreeRDP, open a terminal window and run the following commands.a Run the following command:

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

b Run the following command:make

c Run the following command, which installs the built xfreerdp binary in a directory on theexecution PATH so that View Client can run the program by executing xfreerdp:sudo make install

Enabling FIPS Mode on the ClientYou can set a configuration property so that the client uses only FIPS (Federal Information ProcessingStandard) 140-2 approved cryptographic algorithms and protocols to establish a remote PCoIP connection.NOTE View PCoIP FIPS mode does not support AES-256 encryption algorithms.This setting applies to both server and client. You can configure either endpoint or both endpoints tooperate in FIPS mode. Configuring a single endpoint to operate in FIPS mode limits the encryptionalgorithms that are available for session negotiation.IMPORTANT If you enable FIPS mode on one endpoint but the other endpoint does not supportcryptographic algorithms that are approved by FIPS 140-2, the connection will fail.When this setting is disabled or not configured, FIPS mode is not used.

Setting the Configuration PropertyTo enable or disable FIPS mode, you can set the pcoip.enable_fips_mode property. Setting the propertyto 1 turns on FIPS mode, and setting the property to 0 turns off FIPS mode. For example, the followingsetting turns on FIPS mode: pcoip.enable_fips_mode = 1

Use a space before and after the equals (=) sign.You can set this property in any of several files. When View Client starts up, the setting is processed fromvarious locations in the following order:1 /etc/teradici/pcoip_admin_defaults.conf2 ~/.pcoip.rc3 /etc/teradici/pcoip_admin.confIf a setting is defined in multiple locations, the value that is used is the value from the last file read.

Configuring the PCoIP Client-Side Image CachePCoIP client-side image caching stores image content on the client to avoid retransmission. This feature isenabled by default to reduce bandwidth usage.IMPORTANT This feature is available only when the version of View Agent and View Connection Server isView 5.0 or later.


VMware, Inc. 33

The PCoIP image cache captures spatial, as well as temporal, redundancy. For example, when you scrolldown through a PDF document, new content appears from the bottom of the window and the oldest contentdisappears from the top of the window. All the other content remains constant and moves upward. ThePCoIP 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 cacheindices, using the image cache saves a significant amount of bandwidth. This efficient scrolling has benefitsboth on the LAN and over the WAN.n On the LAN, where bandwidth is relatively unconstrained, using client-side image caching delivers

significant bandwidth savings.n 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 bandwidthand ensure a smooth, highly responsive scrolling experience.

By default this feature is enabled, so that the client stores portions of the display that were previouslytransmitted. The default cache size is 250MB. You can configure the client image cache size, from aminimum of 50MB to a maximum of 1024MB for View Client 1.7 and later versions. The maximum size forearlier versions is 300MB. A larger cache size reduces bandwidth usage but requires more memory on theclient. A smaller cache size requires more bandwidth usage. For example, a thin client with little memoryrequires a smaller cache size.

Setting the Configuration PropertyTo configure the cache size, you can set the pcoip.image_cache_size_mb property. For example, thefollowing setting configures 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 number less than 50, the number isconverted to 50. If you specify a number larger than the maximum, the number is converted to maximum.You can set this property in any of several files. When View Client starts up, the setting is processed fromvarious locations in the following order:1 /etc/teradici/pcoip_admin_defaults.conf2 ~/.pcoip.rc3 /etc/teradici/pcoip_admin.confIf a setting is defined in multiple locations, the value that is used is the value from the last file read.NOTE 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 configuration, for every tile (32 x 32 pixels) in an image that comes from the image cache, you cansee a rectangle around the tile.


34 VMware, Inc.

Managing Server Connections andDesktops 3

Use Horizon View Client to connect to View Connection Server or a security server and log in to or off of aremote desktop. For troubleshooting purposes, you can also reset a remote desktop assigned to you.Depending on how the administrator configures policies for remote desktops, end users might be able toperform many operations on their desktops.n Log In to a Remote Desktop for the First Time on page 35

Before you have end users access their remote desktops, test that you can log in to a remote desktopfrom the client system.

n Certificate Checking Modes for Horizon View Client on page 37Administrators and sometimes end users can configure whether client connections are rejected if anyor some server certificate checks fail.

n Switch Desktops on page 38If you are connected to a desktop, you can switch to another desktop.

n Log Off or Disconnect from a Desktop on page 38If you disconnect from a remote desktop without logging off, applications remain open.

n Roll Back a Desktop on page 39Rolling back discards changes made to a virtual desktop that you checked out for use in local mode ona Windows PC or laptop.

Log In to a Remote Desktop for the First TimeBefore you have end users access their remote desktops, test that you can log in to a remote desktop fromthe client system.Prerequisitesn Obtain the credentials that you need to log in, such as Active Directory user name and password, RSA

SecurID user name and passcode, or RADIUS authentication user name and passcode.n Obtain the domain name for logging in.n Perform the administrative tasks described in Preparing View Connection Server for Horizon View

Client, on page 11.n 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 that connection on.IMPORTANT VMware recommends using a security server rather than a VPN.

VMware, Inc. 35

n Verify that you have the fully qualified domain name (FQDN) of the server that provides access to theremote desktop. You also need the port number if the port is not 443.

n If you plan to use the RDP display protocol to connect to a remote desktop, verify that theAllowDirectRDP View Agent group policy setting is enabled.

n If your administrator has allowed it, you can configure the certificate checking mode for the SSLcertificate that the View server presents. See Certificate Checking Modes for Horizon View Client, onpage 37.

Procedure1 Either open a terminal window and enter vmware-view or select Applications > Internet > VMware

Horizon View Client from the Ubuntu menu bar.2 Enter the server name and a port number if required, and click Continue.

An example using a nondefault port is view.company.com:1443.3 If you are prompted for RSA SecurID credentials or RADIUS authentication credentials, enter the user

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

You might see a message that you must confirm 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 View Connection Server did not send a certificate thumbprint to theclient. The thumbprint is a hash of the certificate public key and is used as an abbreviation of the publickey. View Connection Server 4.6.1, 5.0.1, and later versions send thumbprint information, but earlierversions do not.

6 (Optional) Select the display protocol and window size to use.

Option DescriptionDisplay protocol The default is PCoIP. To use Microsoft RDP instead, click PCoIP under the

desktop name to toggle and select Microsoft RDP.Window size The default is Full Screen - All Monitors. To choose another window size,

click one of the other options under the desktop name, such as LargeScreen or Custom Size.

7 Double-click a remote desktop shortcut to connect.

After you are connected, the client window appears. If Horizon View Client cannot connect to the desktop,perform the following tasks:n Determine whether View Connection Server is configured not to use SSL. Horizon View Client requires

SSL connections. Check whether the global setting in View Administrator for the Use SSL for clientconnections check box is deselected. If so, you must either select the check box, so that SSL is used, orset up your environment so that clients can connect to an HTTPS enabled load balancer or otherintermediate device that is configured to make an HTTP connection to View Connection Server.

n Verify that the security certificate for View Connection Server is working properly. If it is not, in ViewAdministrator, you might also see that the View Agent on desktops is unreachable.

n Verify that the tags set on the View Connection Server instance allow connections from this user. Seethe VMware Horizon View Administration document.

n Verify that the user is entitled to access this desktop. See the VMware Horizon View Administrationdocument.


36 VMware, Inc.

n If you are using the RDP display protocol to connect to a remote desktop, verify that the clientcomputer allows remote desktop connections.

Certificate Checking Modes for Horizon View ClientAdministrators and sometimes end users can configure whether client connections are rejected if any orsome server certificate checks fail.Certificate checking occurs for SSL connections between View Connection Server and Horizon View Client.Certificate verification includes the following checks:n Is the certificate intended for a purpose other than verifying the identity of the sender and encrypting

server communications? That is, is it the correct type of certificate?n Has the certificate expired, or is it valid only in the future? That is, is the certificate valid according to

the computer clock?n Does the common name on the certificate match the host name of the server that sends it? A mismatch

can occur if a load balancer redirects Horizon View Client to a server that has a certificate that does notmatch the host name entered in Horizon View Client. Another reason a mismatch can occur is if youenter an IP address rather than a host name in the client.

n Is the certificate signed by an unknown or untrusted certificate authority (CA)? Self-signed certificatesare one type of untrusted CA.To pass this check, the certificate's chain of trust must be rooted in the device's local certificate store.

NOTE For instructions about distributing a self-signed root certificate that users can install on their Linuxclient systems, see the Ubuntu documentation.Horizon View Client uses the PEM-formatted certificates stored in the /etc/ssl/certs directory on theclient system. For instructions about importing a root certificate stored in this location, see the procedurecalled "Importing a Certificate into the System-Wide Certificate Authority Database" in the document at https://help.ubuntu.com/community/OpenSSL.In addition to presenting a server certificate, View Connection Server 4.6.1, 5.0.1, and later versions alsosend a certificate thumbprint to Horizon View Client. The thumbprint is a hash of the certificate public keyand is used as an abbreviation of the public key. If the View server does not send a thumbprint, you see awarning that the connection is untrusted.If your administrator has allowed it, you can set the certificate checking mode. Select File > Preferencesfrom the VMware Horizon View Client menu bar or the View desktop menu bar. You have three choices:n Never connect to untrusted servers. If any of the certificate checks fails, the client cannot connect to the

server. An error message lists the checks that failed.n Warn before connecting to untrusted servers. If a certificate check fails because the server uses a self-

signed certificate, you can click Continue to ignore the warning. For self-signed certificates, thecertificate name is not required to match the View Connection Server name you entered inHorizon View Client.

n Do not verify server identity certificates. This setting means that View does not perform any certificatechecking.

Chapter 3 Managing Server Connections and Desktops

VMware, Inc. 37

Switch DesktopsIf you are connected to a desktop, you can switch to another desktop.Procedureu Select a remote desktop from the same server or a different server.

Option ActionChoose a different remote desktopon the same server

Select Desktop > Disconnect from the menu bar.

Choose a remote desktop on adifferent server

Select File > Disconnect from server from the menu bar.

Log Off or Disconnect from a DesktopIf you disconnect from a remote desktop without logging off, applications remain open.Even if you do not have a remote desktop open, you can log off 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 Off.Proceduren Disconnect without logging off.

Option ActionAlso quit Horizon View Client Click the Close button in the corner of the window or select File > Quit

from the menu bar.Choose a different remote desktopon the same server

Select Desktop > Disconnect from the menu bar.

Choose a remote desktop on adifferent server

Select File > Disconnect from server from the menu bar. NOTE Your View administrator can configure your desktop to automatically log off whendisconnected. In that case, any open programs in your desktop are stopped.

n Log off and disconnect from a desktop.

Option ActionFrom within the desktop OS Use the Windows Start menu to log off.From the menu bar Select Desktop > Disconnect and Log off.

If you use this procedure, files that are open on the remote desktop will beclosed without being saved first.

n Log off when you do not have a remote desktop open.

a From the Home screen with desktop shortcuts, select the desktop and select Desktop > Log offfrom the menu bar.

b If prompted, supply credentials for accessing the remote desktop.If you use this procedure, files that are open on the remote desktop will be closed without being savedfirst.


38 VMware, Inc.

Roll Back a DesktopRolling back discards changes made to a virtual desktop that you checked out for use in local mode on aWindows PC or laptop.You can roll back a remote desktop only if your View administrator has enabled this feature and only if youchecked out the desktop.CAUTION If changes were made to the local mode desktop and those changes were not replicated back to theView server before rolling back, the changes are lost.

Prerequisitesn Obtain the credentials that you need to log in, such as Active Directory user name and password, RSA

SecurID user name and passcode, or RADIUS authentication user name and passcode.n Back up the desktop to the server to preserve data or files.

You can use View Administrator to replicate data to the server, or, if the policy is set to allow it, you canuse View Client with Local Mode on the Windows client where the desktop is currently checked out.

Procedure1 If the Horizon View Client Home screen displays the View Connection Server prompt, supply the

server name and click Continue.a If you are prompted for RSA SecurID credentials or RADIUS authentication credentials, enter the

user name and passcode and click Continue.b Enter your user name and password in the login dialog box.

2 On the Horizon View Client Home screen that displays remote desktop shortcuts, select the desktopand select Desktop > Rollback Desktop from the menu bar.

After the remote desktop is rolled back, you can log in to it from the Linux client.

Chapter 3 Managing Server Connections and Desktops

VMware, Inc. 39


40 VMware, Inc.

Using a Microsoft Windows Desktopon a Linux System 4

View Client for Linux supports some of the features included in View Client for Windows.This chapter includes the following topics:n Feature Support Matrix for Linux, on page 41n Internationalization, on page 42n Keyboards and Monitors, on page 42n Using the Real-Time Audio-Video Feature for Webcams and Microphones, on page 44n Set Printing Preferences for the Virtual Printer Feature, on page 47n Copying and Pasting Text, on page 48

Feature Support Matrix for LinuxSome features are supported on one type of View Client but not on another. For example, local mode issupported only on View Client for Windows.Table 41. Features Supported on Windows Desktops for Linux Clients

FeatureWindows 8.xDesktop

Windows 7Desktop

WindowsVista Desktop

Windows XPDesktop

Windows Server2008 R2 Desktop

RSA SecurID orRADIUS

X X X X X

Single sign-on X X X X XRDP displayprotocol

X X X X X

PCoIP displayprotocol

X X X X X

USB access Partner clientsystems only

Partner clientsystems only




Real-Time Audio-Video (RTAV)






Wyse MMR Partner clientsystems only,and only withRDP

Partner clientsystems only, andonly with RDP

Windows 7 MMRVirtual printing Partner client

systems onlyPartner clientsystems only



VMware, Inc. 41

Table 41. Features Supported on Windows Desktops for Linux Clients (Continued)

FeatureWindows 8.xDesktop

Windows 7Desktop

WindowsVista Desktop

Windows XPDesktop

Windows Server2008 R2 Desktop

Location-basedprinting

X X X X

Smart cards Partner clientsystems only, andonly with PCoIP





Multiple monitors X X X X XLocal mode

Features that are supported on Windows desktops for Linux View Client have the following restrictions.n Windows 8.x desktops are supported only if you have Horizon View 5.2 or later servers and desktops.n The real-time audio-video feature is supported only if you have Horizon View 5.2 with Feature Pack 2

or later.n Windows Server 2008 R2 desktops are supported only if you have Horizon View 5.3 or later servers and

desktops.For descriptions of these features and their limitations, see the VMware Horizon View Planning document.NOTE This feature support matrix applies to the View Client for Linux that VMware makes available onUbuntu. In addition, several VMware partners offer thin client devices for Horizon View deployments. Thefeatures that are available for each thin client device are determined by the vendor and model and theconfiguration that an enterprise chooses to use. For information about the vendors and models for thinclient devices, see the VMware Compatibility Guide at http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm.

InternationalizationThe user interface and documentation are available in English, Japanese, French, German, SimplifiedChinese, Traditional Chinese, and Korean.If you are using a Ubuntu 10.4 Linux client system and you want to display the View Client user interface ina language other than English, you must set the client system to use a locale that uses UTF-8 encoding.

Keyboards and MonitorsYou can use multiple monitors and all types of keyboards with a remote desktop. Certain settings ensure thebest possible user experience.

Best Practices for Using Multiple MonitorsFollowing are recommendations for successfully using multiple monitors with a remote desktop:n Define the primary monitor as the bottom-left-most monitor.n 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 appearon the right monitor because the right monitor is still the top-left-most monitor.

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


42 VMware, Inc.

To use more than 2 monitors to display your remote desktop on a Ubuntu client system, you mustconfigure the kernel.shmmax setting correctly. Use the following formula:max horizontal resolution X max vertical resolution X max number of monitors X 4For example, manually setting kernel.shmmax to 65536000 allows you to use four monitors with a screenresolution of 2560x1600.

n Horizon View Client uses the monitor configuration that is in use when Horizon View Client starts. Ifyou change a monitor from landscape to portrait mode or if you plug an additional monitor in to theclient system while Horizon View Client is running, you must restart Horizon View Client in order touse the new monitor configuration.

Horizon View Client supports the following monitor configurations:n 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 orlandscape mode.

n If you use more than 2 monitors, the monitors must be in the same mode and have the same screenresolution. That is, if you use 3 monitors, all 3 monitors must be in either portrait mode or landscapemode and must use the same screen resolution.

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

Screen ResolutionConsider the following guidelines when setting screen resolutions:n 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.n With PCoIP, if you use 2 monitors, you can adjust the resolution for each monitor separately, with a

resolution of up to 2560x1600 per display. If you use more than 2 monitors, the monitors must use thesame screen resolution.

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

Keyboard LimitationsFor the most part, keyboards work as well with a remote desktop as they do with a phy

Documents

Horizon View Client Linux Document