Vmware – Horizon Client for Linux – User Manual

Category: Software and Application User Guides and Manuals

Download user manual for Vmware – Horizon Client for Linux – User Manual 
Preview: Below is a preview of the manual as extracted from the PDF file


Using VMware Horizon Client for Linux
September 2014
Horizon Client
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-001162-05Using VMware Horizon 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:
docfeedback@vmware.com
Copyright
©
2012–2014 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.comContents
Using VMware Horizon Client for Linux 5

1 System Requirements and Installation 7
System Requirements for Linux Client Systems 8
System Requirements for Real-Time Audio-Video 9
Supported Desktop Operating Systems 10
Requirements for Using Flash URL Redirection 10
Preparing View Connection Server for Horizon Client 11
Install Horizon Client for Linux 11
Horizon Client Data Collected by VMware 13

2 Configuring Horizon Client for End Users 17
Using URIs to Configure Horizon Client 18
Using the Horizon Client Command-Line Interface and Configuration Files 21
Configuring Certificate Checking for End Users 30
Configuring Advanced SSL Options 30
Configuring Specific Keys and Key Combinations to Send to the Local System 31
Using FreeRDP for RDP Connections 32
Enabling FIPS Mode on the Client 34
Configuring the PCoIP Client-Side Image Cache 35

3 Managing Remote Desktop and Application Connections 37
Connect to a Remote Desktop or Application for the First Time 37
Certificate Checking Modes for Horizon Client 39
Switch Desktops or Applications 41
Log Off or Disconnect 41

4 Using a Microsoft Windows Desktop or Application on a Linux System 43
Feature Support Matrix for Linux 43
Internationalization 44
Keyboards and Monitors 45
Using the Real-Time Audio-Video Feature for Webcams and Microphones 46
Saving Documents in a Remote Application 50
Set Printing Preferences for the Virtual Printer Feature on a Remote Desktop 50
Copying and Pasting Text 51

5 Troubleshooting Horizon Client 53
Reset a Remote Desktop or Application 53
Uninstalling Horizon Client 54

VMware, Inc. 36 Configuring USB Redirection on the Client 55
Setting USB Configuration Properties 56
USB Device Families 59
Index 61
Using VMware Horizon Client for Linux
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 written for experienced system administrators who are familiar with
virtual machine technology and datacenter operations.
NOTE This document pertains mostly to the Horizon Client for Linux that VMware makes available on
Ubuntu. In addition, several VMware partners offer thin client devices for View deployments. The features
that are available for each thin client device, and the operating systems supported, are determined by the
vendor, the 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.
VMware, Inc. 5Using 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.
n System Requirements for Linux Client Systems on page 8
The Linux PC or laptop on which you install Horizon Client, and the peripherals it uses, must meet
certain system requirements.
n System Requirements for Real-Time Audio-Video on page 9
Real-Time Audio-Video works with standard webcam, USB audio, and analog audio devices, and
with standard conferencing applications like Skype, WebEx, and Google Hangouts. To support Real-
Time Audio-Video, your View deployment must meet certain software and hardware requirements.
n Supported Desktop Operating Systems on page 10
Administrators create virtual machines with a guest operating system and install View Agent in the
guest operating system. End users can log in to these virtual machines from a client device.
n Requirements for Using Flash URL Redirection on page 10
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.
n Preparing View Connection Server for Horizon Client on page 11
Administrators must perform specific tasks to enable end users to connect to remote desktops and
applications.
n Install Horizon Client for Linux on page 11
End users open Horizon Client to connect to remote desktops from a physical machine. Horizon Client
for Linux runs on Ubuntu 12.04 systems, and you install it by using the Synaptic Package Manager.
n Horizon Client Data Collected by VMware on page 13
If your company participates in the customer experience improvement program, VMware collects data
from certain Horizon Client fields. Fields containing sensitive information are made anonymous.
VMware, Inc. 7System 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.
NOTE These system requirements pertain to the Horizon Client for Linux that VMware makes available on
Ubuntu. In addition, several VMware partners offer thin client devices for View deployments. The features
that are available for each thin client device, and the operating systems supported, 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 computer
Memory At least 2GB of RAM
Operating systems
n Horizon Client 3.1 and later: 32-bit Ubuntu Linux 12.04 or 14.04
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.04
n View Client 1.5: 32-bit Ubuntu Linux 10.04 or 10.10
OpenSSL requirement If the version of OpenSSL on the client system is not 1.0.1h, update the
verison of OpenSSL on the client system to OpenSSL 1.0.1h.
IMPORTANT If you download the source code for OpenSSL 1.0.1h from the
OpenSSL Web site or some other site, compile, and install it, you might get
libraries with the extension 1.0.0 or 1.0.1h, but Horizon Client looks for
libraries with the extension 1.0.1. Specifically, the client looks for files named
libssl.so.1.0.1 and libcrypto.so.1.0.1 in system`s library path. To work
around this issue, you can create a symbolic link by linking libssl.so.1.0.1
to libssl.so.1.0.1h or libssl.so.1.0.0, as appropriate, and linking
libcrypto.so.1.0.1 to libcrypto.so.1.0.1h or libcrypto.so.1.0.0.
If you do not have OpenSSL 1.0.1h, Horizon Client might not start, might
exit unexpectedly, or might not be able to connect to the server.
View Connection
Server, Security Server,
and View Agent
Latest maintenance release of VMware View 4.6.x and later releases
If client systems connect from outside the corporate firewall, VMware
recommends that you use a security server. With a security server, client
systems will not require a VPN connection.
Remote applications are available only on Horizon 6.0 View servers.
Display protocol for
View
PCoIP or RDP
IMPORTANT Although Horizon Client for Linux supports the RDP display
protocol, the particular RDP client that ships with your distribution of
Ubuntu might not work with Horizon Client.
Screen resolution on
client system
Minimum: 1024 X 768 pixels
Hardware Requirements
for PCoIP
n x86-based processor with SSE2 extensions, with a 800MHz or higher
processor speed.
Using VMware Horizon Client for Linux
8 VMware, Inc.n 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
n x86-based processor with SSE2 extensions, with a 800MHz or higher
processor speed.
n 128MB RAM.
Software Requirements
for Microsoft RDP
n For Ubuntu 12.04, use rdesktop 1.7.0.
Software Requirements
for FreeRDP
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 Configure
FreeRDP,” on page 34.
Other Software
Requirements
Horizon Client also has the following dependencies:
n To support idle session timeouts: libXsso.so.1
n To support Flash URL redirection: libexpat.so.1 (The libexpat.so.0
file is no longer required.)
n To support USB redirection and Real-Time Audio-Video: libudev0
NOTE By default, libudev0 is not installed in Ubuntu 14.04.
System Requirements for Real-Time Audio-Video
Real-Time Audio-Video works with standard webcam, USB audio, and analog audio devices, and with
standard conferencing applications like Skype, WebEx, and Google Hangouts. To support Real-Time Audio-
Video, your View deployment must meet certain software and hardware requirements.
View remote desktop
The desktops must have View Agent 5.2 or later installed. The desktops must
also have the corresponding Remote Experience Agent installed, if
applicable. For example, if View Agent 5.3 is installed, you must also install
the Remote Experience Agent from View 5.3 Feature Pack 1. See the
View Feature Pack Installation and Administration document for View. If you
have View Agent 6.0 or later, no feature pack is required.
Horizon Client computer
or client access device
n Real-Time Audio-Video is supported on x86 devices. This feature is not
supported on ARM processors. The client system processor must have at
least two cores.
n Horizon Client requires the following libraries:
n Video4Linux2
n libv4l
n Pulse Audio
Chapter 1 System Requirements and Installation
VMware, Inc. 9The plug-in file /usr/lib/pcoip/vchan_plugins/libmmredir_plugin.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 files 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.
n 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 View Agent is installed.
Display protocol for
View
PCoIP
Real-Time Audio-Video is not supported in RDP desktop sessions.
Supported Desktop Operating Systems
Administrators create virtual machines with a guest operating system and install View Agent in the guest
operating 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 View 4.6., 5.x, or 6.x installation documentation.
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.
This feature is available when used in conjunction with the correct version of the agent software. For View
5.3 and earlier releases, this feature was included in the Remote Experience Agent, which was part of the
View Feature Pack. For View 6.0 and later releases, this feature is included in View Agent.
n Multicast support requires View 5.2 Feature Pack 2 or later.
n Unicast support requires 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 meet
certain software requirements:
n
NOTE This feature is supported only on the version of Horizon Client provided by partners and only
on x86 thin client devices. This feature is not supported on ARM processors.
Using VMware Horizon Client for Linux
10 VMware, Inc.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 the
appropriate 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.1 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 operating
system.
c Install the wget program, or verify that the program file is already installed.
For a list of the remote desktop requirements for Flash URL redirection, and for instructions about how to
configure a Web page to provide a multicast or unicast stream, see the View documentation.
Preparing View Connection Server for Horizon Client
Administrators must perform specific tasks to enable end users to connect to remote desktops and
applications.
Before end users can connect to View Connection Server or a security server and access a remote desktop or
application, 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 View Installation document.
n If you plan to use a secure tunnel connection for client devices and if the secure connection is
configured with a DNS host name for View 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
Settings dialog box and use the check box called Use secure tunnel connection to desktop.
n 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 View Connection Server 5.3 and earlier, see the topics about creating
desktop pools in the View Administration document. For View Connection Server 6.0 and later, see the
topics about creating desktop and application pools in the Setting Up Desktop and Application Pools in
View document.
n To use two-factor authentication with Horizon Client, such as RSA SecurID or RADIUS authentication,
you must enable this feature on View Connection Server. RADIUS authentication is available with View
5.1 or later View Connection Server. For more information, see the topics about two-factor
authentication in the View Administration document.
Install Horizon Client for Linux
End users open Horizon Client to connect to remote desktops from a physical machine. Horizon Client for
Linux runs on Ubuntu 12.04 systems, and you install it by using the Synaptic Package Manager.
IMPORTANT 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
n Verify that the client system uses a supported operating system. See “System Requirements for Linux
Client Systems,” on page 8.
Chapter 1 System Requirements and Installation
VMware, Inc. 11n Verify that OpenSSL 1.0.1h is installed on the client system.
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 for Linux Client Systems,” on page 8.
n If you have a View Client 1.x or 2.x installed on the Linux client system, uninstall that application
before installing Horizon Client 3.1 or later. See “Uninstalling Horizon Client,” on page 54.
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 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.
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.
3 If you have Ubuntu 10.04, download and install the package from the Ubuntu Software Center, as
follows.
a From the Ubuntu menu bar, select System > Administration > Synaptic Package Manager
b 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 10.04, View Client for Linux 1.7 is installed.
e To determine that installation succeeded, verify that the VMware Horizon View application icon
appears in the Applications > Internet menu.
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 for the First Time,” on page 37.
Using VMware Horizon Client for Linux
12 VMware, Inc.Horizon Client Data Collected by VMware
If your company participates in the customer experience improvement program, VMware collects data from
certain Horizon Client fields. Fields containing sensitive information are made anonymous.
NOTE This feature is available only if your View deployment uses View Connection Server 5.1 or later.
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 identifies your organization is collected. Horizon Client information is sent first to View
Connection Server and then on to VMware, along with data from View servers, desktop pools, and remote
desktops.
Although the information is encrypted while in transit to View Connection Server, the information on the
client system is logged unencrypted in a user-specific directory. The logs do not contain any personally
identifiable information.
The administrator who installs View Connection Server can select whether to participate in the VMware
customer experience improvement program while running the View Connection Server installation wizard,
or an administrator can set an option in View Administrator after the installation.
Table 1‑1. Data Collected from Horizon Clients for the Customer Experience Improvement Program
Description
Is This Field
Made
Anonymous
? Example Value
Company that produced the
Horizon Client application
No VMware
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
number and yyyyyy is the build number.)
Client binary architecture No Examples include the following:
n i386
n x86_64
n arm
Client build name No Examples include the following:
n VMware-Horizon-View-Client-Win32-Windows
n VMware-Horizon-View-Client-Linux
n VMware-Horizon-View-Client-iOS
n VMware-Horizon-View-Client-Mac
n VMware-Horizon-View-Client-Android
n VMware-Horizon-View-Client-WinStore
Host operating system No Examples include the following:
n Windows 8.1
n Windows 7, 64-bit Service Pack 1 (Build 7601 )
n iPhone OS 5.1.1 (9B206)
n Ubuntu 10.04.4 LTS
n Mac OS X 10.8.5 (12F45)
Chapter 1 System Requirements and Installation
VMware, Inc. 13Table 1‑1. Data Collected from Horizon Clients for the Customer Experience Improvement Program
(Continued)
Description
Is This Field
Made
Anonymous
? Example Value
Host operating system kernel No Examples include the following:
n Windows 6.1.7601 SP1
n Darwin Kernel Version 11.0.0: Sun Apr 8 21:52:26 PDT
2012; root:xnu-1878.11.10~1/RELEASE_ARM_S5L8945X
n Darwin 11.4.2
n Linux 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24
17:27:10 UTC 2012
n unknown (for Windows Store)
Host operating system architecture No Examples include the following:
n x86_64
n i386
n armv71
n ARM
Host system model No Examples include the following:
n Dell Inc. OptiPlex 960
n iPad3,3
n MacBookPro8,2
n 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.00GH
n Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GH
n unknown (for iPad)
Number of cores in the host system`s
processor
No For example: 4
MB of memory on the host system No Examples include the following:
n 4096
n unknown (for Windows Store)
Number of USB devices connected No 2 (USB device redirection is supported only for Linux,
Windows, and Mac OS X clients.)
Maximum concurrent USB device
connections
No 2
USB device vendor ID No Examples include the following:
n Kingston
n NEC
n Nokia
n Wacom
USB device product ID No Examples include the following:
n DataTraveler
n Gamepad
n Storage Drive
n Wireless Mouse
Using VMware Horizon Client for Linux
14 VMware, Inc.Table 1‑1. Data Collected from Horizon Clients for the Customer Experience Improvement Program
(Continued)
Description
Is This Field
Made
Anonymous
? Example Value
USB device family No Examples include the following:
n Security
n Human Interface Device
n Imaging
USB device usage count No (Number of times the device was shared)
Chapter 1 System Requirements and Installation
VMware, Inc. 15Using VMware Horizon Client for Linux
16 VMware, Inc.Configuring Horizon Client for End
Users 2
Horizon Client provides several configuration mechanisms to simplify the login and desktop selection
experience for end users, and also to enforce security policies.
The following table shows only some of the configuration settings that you can set in one or more ways.
Table 2‑1. Common Configuration Settings
Setting Mechanisms for Configuring
View Connection Server address URI, Configuration File Property, Command Line
Active Directory user name URI, Configuration File Property, Command Line
Domain name URI, Configuration File Property, Command Line
Desktop display name URI, Configuration File Property, Command Line
Window size URI, Configuration File Property, Command Line
Display protocol URI, Configuration File Property, Command Line
Configuring certificate checking Configuration File Property
Configuring SSL protocols and
cryptographic algorithms
Configuration File Property, Command Line
This chapter includes the following topics:
n “Using URIs to Configure Horizon Client,” on page 18
n “Using the Horizon Client Command-Line Interface and Configuration Files,” on page 21
n “Configuring Certificate Checking for End Users,” on page 30
n “Configuring Advanced SSL Options,” on page 30
n “Configuring Specific Keys and Key Combinations to Send to the Local System,” on page 31
n “Using FreeRDP for RDP Connections,” on page 32
n “Enabling FIPS Mode on the Client,” on page 34
n “Configuring the PCoIP Client-Side Image Cache,” on page 35
VMware, Inc. 17Using URIs to Configure Horizon Client
Using uniform resource identifiers (URIs), you can create a Web page or an email with links that end users
click to launch Horizon Client, connect to View Connection Server, and launch a specific desktop or
application with specific configuration 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 of the following
information, so that your end users do not need to supply it:
n View Connection Server address
n Port number for View Connection Server
n Active Directory user name
n Domain name
n Desktop or application display name
n Window size
n Actions including reset, log off, and start session
n Display protocol
To construct a URI, you use the vmware-view URI scheme with Horizon Client specific path and query parts.
NOTE You can use URIs to launch Horizon Client only if the client software is already installed on end
users` 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 configuration 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 for launching 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.
IMPORTANT In all parts, non-ASCII characters must first 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
http://www.utf8-chartable.de/.
authority-part Specifies the server address and, optionally, a user name, a non-default port
number, or both. Note that 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
Using VMware Horizon Client for Linux
18 VMware, Inc.Note that 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 Specifies the desktop or application. Use the desktop display name or
application display name. This name is the one specified 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 Specifies the configuration 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 conflict 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‑2. Values That Can Be Used with the action Query
Value Description
browse Displays a list of available desktops and applications hosted on the
specified server. You are not required to specify a desktop or
application when using this action.
start-session Launches the specified desktop or application. If no action query is
provided and the desktop or application name is provided,
start-session is the default action.
reset Shuts down and restarts the specified desktop. Unsaved data is
lost. Resetting a remote desktop is the equivalent of pressing the
Reset button on a physical PC. In Horizon Client 3.0, if you specify
an application, the action will be ignored.
In Horizon Client 3.1, if you specify an application, the end user is
prompted to confirm quitting all remote applications.
logoff Logs the user out of the guest operating system in the remote
desktop. If you specify an application, the action will be ignored or
the end user will see the warning message “Invalid URI action.”
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 ‑3. Valid Values for the desktopLayout Query
Value Description
fullscreen Full screen on one monitor. This is the default.
multimonitor Full screen on all monitors.
windowLarge Large window.
Chapter 2 Configuring Horizon Client for End Users
VMware, Inc. 19Table 2‑3. Valid Values for the desktopLayout Query (Continued)
Value Description
windowSmall Small window.
WxH Custom resolution, where you specify the width by height,
in pixels. An example of the syntax is
desktopLayout=1280×800.
desktopProtocol For remote desktops, valid values are RDP and PCoIP. For example, to specify
PCoIP, use the syntax desktopProtocol=PCoIP. For remote applications,
regardless of the setting, the application sessions use PCoIP.
domainName The domain associated with the user who is connecting to the remote
desktop or application.
Examples of vmware-view URIs
You can create hypertext links or buttons 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, launch 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.
1 vmware-view://view.mycompany.com/Primary%20Desktop?action=start-session
Horizon Client is launched 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.
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 Horizon Client Command-Line Interface and
Configuration Files,” on page 21.
2 vmware-view://view.mycompany.com:7555/Primary%20Desktop
This URI has the same effect as the previous example, except that it uses the nondefault port of 7555 for
View Connection Server. (The default port is 443.) Because a desktop identifier is provided, the desktop
is launched even though the start-session action is not included in the URI.
3 vmware-view://fred@view.mycompany.com/Finance%20Desktop?desktopProtocol=PCoIP
Horizon Client is launched 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.
4 vmware-view://fred@view.mycompany.com/Finance%20Desktop?domainName=mycompany
Horizon Client is launched 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.
Using VMware Horizon Client for Linux
20 VMware, Inc.5 vmware-view://view.mycompany.com/
Horizon Client is launched, and the user is taken to the login prompt for connecting to the
view.mycompany.com server.
6 vmware-view://view.mycompany.com/Primary%20Desktop?action=reset
Horizon Client is launched 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 confirm the reset operation for Primary Desktop. After the reset
occurs, depending on the type of client, the user might see a message indicating whether the reset was
successful.
NOTE This action is available only if the View administrator has enabled this feature for end users.
7 vmware-view://
Horizon Client is launched, and the user is taken to the page for entering the address of a View
Connection Server instance.
HTML Code Examples
You can use URIs to make hypertext links and buttons to include in emails or on Web pages. The following
examples 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 Horizon Client Command-Line Interface and Configuration
Files
You can configure Horizon 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 default
values your users see in Horizon Client or to suppress some dialog boxes from prompting users for
information. You can also specify settings that you do not want users to change.
Processing Order for Configuration Settings
When Horizon Client starts up, configuration settings 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
Chapter 2 Configuring Horizon Client for End Users
VMware, Inc. 21If 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 in
the /etc/vmware/view-mandatory-config file.
To set default values that users can change, use the /etc/vmware/view-default-config file. After users
change a setting, when they exit Horizon Client, any changed settings are saved in the ~/.vmware/view-
preferences file.
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 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 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.
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 for
the proxy. If you do not perform this action, the proxy exception setting does not take effect in
Horizon Client. You configure a proxy exception for the View Connection Server instance.
Horizon Client Configuration Settings and Command-Line Options
For your convenience, almost all configuration settings have both a key=value property and a corresponding
command-line option name. For a few settings, there is a command-line option but no corresponding
property you can set in a configuration file. For a few other settings, you must set a property because no
command-line option is available.
IMPORTANT Some command-line options and configuration keys, such as the ones for USB redirection and
MMR, are available only with the version of Horizon Client provided by third-party vendors. For more
information about VMware thin-client and zero-client partners, see the VMware Compatibility Guide at
http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm.
Using VMware Horizon Client for Linux
22 VMware, Inc.Table 2‑4. Horizon Client Command-Line Options and Configuration File Keys
Configuration Key Command-Line Option Description
view.allMonitors –allmonitors Hides the host operating system and opens the
Horizon Client user interface in full screen mode across
all monitors that are connected when the client is
launched.
If you are setting the configuration key, specify “TRUE”
or “FALSE”. Default is “FALSE”.
view.allowDefaultBroker -l, –lockServer Using this command-line option, or setting the property
to “FALSE”, disables the Server field unless the client
has never connected to any server, and no server
address is provided in the command line or the
preferences file.
Example of using the command-line option:
–lockServer -s view.company.com
view.autoConnectBroker None Automatically connects to the last View server used
unless the view.defaultBroker configuration property
is set or unless the –serverURL= command-line option
is used.
Specify “TRUE” or “FALSE”. Default is “FALSE”.
Setting this property and the
view.autoConnectDesktop property to “TRUE” is the
equivalent of setting the view.nonInteractive
property to “TRUE”.
view.autoConnectDesktop None Automatically connects to the last View desktop used
unless the view.defaultDesktop configuration
property is set or unless the –desktopName=
command-line option is used.
Specify “TRUE” or “FALSE”. Default is “FALSE”.
Setting this property and the
view.autoConnectBroker property to “TRUE” is the
equivalent of setting the view.nonInteractive
property to “TRUE”.
view.autoDisconnectEmptyAppSession None 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 setting used in View
Administrator, which by default would be to disconnect
after one minute.
view.defaultAppHeight None Specifies 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”.
Chapter 2 Configuring Horizon Client for End Users
VMware, Inc. 23Table 2‑4. Horizon Client Command-Line Options and Configuration File Keys (Continued)
Configuration Key Command-Line Option Description
view.defaultAppSize –appSize= Sets the default size of the window for remote
applications:
n To use all monitors, specify “1”.
n To use full screen mode on one monitor, specify
“2”.
n To use a large window, specify “3”.
n To use a small window, specify “4”.
n To set a custom size, specify “5”and then also set
the view.defaultAppWidth and
view.defaultAppHeight properties.
Default is “1”.
view.defaultAppWidth None Specifies 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”.
view.defaultBroker -s, –serverURL= Adds the name that you specify to the Server field in
Horizon Client. Specify a fully qualified 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
view.defaultDesktop -n, –desktopName= Specifies 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.
view.defaultDesktopHeight None Specifies 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”).
view.defaultDesktopSize –desktopSize= Sets the default size of the window for the View
desktop:
n To use all monitors, set the property to “1” or use
the command-line argument “all”.
n To use full screen mode on one monitor, set the
property to “2” or use the command-line argument
“full”.
n To use a large window, set the property to “3” or
use the command-line argument “large”.
n To use a small window, set the property to “4” or
use the command-line argument “small”.
n 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=”1280×800″
–desktopSize=”all”
Using VMware Horizon Client for Linux
24 VMware, Inc.Table 2‑4. Horizon Client Command-Line Options and Configuration File Keys (Continued)
Configuration Key Command-Line Option Description
view.defaultDesktopWidth None Specifies the default width of the window for the View
desktop, in pixels. Use this property in conjunction with
view.defaultDesktopHeight when specifying a
custom desktop size (view.defaultDesktopSize
property is set to “5”).
view.defaultDomain -d, –domainName= Sets the domain name that Horizon Client uses for all
connections and adds the domain name that you specify
to the Domain Name field in the authentication dialog
box.
view.defaultLogLevel None Sets the log level for Horizon Client logs. Set the
property to one of the following values:
n “0” means include all log events.
n “1” means include trace-level events and events
captured for settings 2 though 6.
n “2” means include debug events and events
captured for settings 3 through 6.
n “3” (the default) means include info-level events
and events captured for settings 4 through 6.
n “4” means include warning, error, and fatal events.
n “5” means include error and fatal events.
n “6” means include fatal events.
Default is “3”.
view.defaultPassword -p “-“, –password=”-” For PCoIP and rdesktop connections, 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
field in the authentication dialog box if View Connection
Server accepts password authentication.
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 values are case-sensitive. For example,
if you enter rdp the protocol used will be the default.
Default is the setting specified in View Administrator,
under pool settings for the pool.
If you use RDP and you want to use FreeRDP rather
than rdesktop, you must also use the rdpClient
setting.
view.defaultUser -u, –userName= Sets the user name that Horizon Client uses for all
connections and adds the user name that you specify to
the User Name field 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
prefix string, such as custom-.
view.disableMaximizedApp –disableMaximizedApp If set to “FALSE” (the default), the application is
launched in full screen mode.
view.fullScreen –fullscreen Hides the host operating system and opens the
Horizon Client user interface in full screen mode on one
monitor. This option does not affect the screen mode of
the desktop session.
If you are setting the configuration key, specify “TRUE”
or “FALSE”. Default is “FALSE”.
Chapter 2 Configuring Horizon Client for End Users
VMware, Inc. 25Table 2‑4. Horizon Client Command-Line Options and Configuration File Keys (Continued)
Configuration Key Command-Line Option Description
view.kbdLayout -k, –kbdLayout= Specifies which locale to use for the keyboard layout.
NOTE 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”
view.kioskLogin –kioskLogin Specifies that Horizon Client is going to authenticate
using a kiosk mode account.
If you are setting the configuration key, specify “TRUE”
or “FALSE”. Default is “FALSE”.
For examples, see the kiosk mode example that follows
this table.
view.mmrPath -m, –mmrPath= (Available only with distributions from third-party
vendors) Specifies the path to the directory that contains
the Wyse MMR (multimedia redirection) libraries.
Example of using the command-line option:
–mmrPath=”/usr/lib/altmmr”
view.nomenubar –nomenubar Suppresses the Horizon Client menu bar when the client
is in full screen mode, so that users cannot access menu
options to log off of, reset, or disconnect from a View
desktop. Use this option when configuring kiosk mode.
If you are setting the configuration key, specify “TRUE”
or “FALSE”. Default is “FALSE”.
view.nonInteractive -q, –nonInteractive Hides unnecessary UI steps from end users by skipping
the screens that are specified in the command line or
configuration properties.
If you are setting the configuration key, specify “TRUE”
or “FALSE”. Default is “FALSE”.
Setting this property to “TRUE” is the equivalent of
setting 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″
view.once –once Specifies 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 find it difficult to kill the vmware-
view process remotely.
If you are setting the configuration key, specify “TRUE”
or “FALSE”. Default is “FALSE”.
Using VMware Horizon Client for Linux
26 VMware, Inc.Table 2‑4. Horizon Client Command-Line Options and Configuration File Keys (Continued)
Configuration Key Command-Line Option Description
view.rdesktopOptions –rdesktopOptions= (Available if you use the Microsoft RDP display
protocol) Specifies 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”
None -r, –redirect= (Available if you use the Microsoft RDP display
protocol) Specifies 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”
view.rdpClient –rdpclient= (Available if you use the Microsoft RDP display
protocol) Specifies which type of RDP client to use. The
default is rdesktop. To use FreeRDP instead, specify
xfreerdp.
NOTE To use FreeRDP, you must have the correct
version of FreeRDP installed, along with any applicable
patches. For more information, see “Install and
Configure FreeRDP,” on page 34.
None –save 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.
view.sendCtrlAltDelToLocal None (Available if you use the PCoIP 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”.
NOTE 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 setting in
the /etc/vmware/view-keycombos-config file.
view.sendCtrlAltDelToVM None (Available if you use the PCoIP 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 setting in
the /etc/vmware/view-keycombos-config file.
view.sendCtrlAltInsToVM None (Available if you use the PCoIP 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”.
NOTE To use this feature, you must also set the agent-
side GPO policy called “Use alternate key for sending
Secure Attention Sequence,” available in the pcoip.adm
template. See the topic called “View PCoIP Session
Variables for the Keyboard” in the “Configuring Policies”
chapter of the Setting Up Desktop and Application Pools in
View document.
This option has a lower priority than the setting in
the /etc/vmware/view-keycombos-config file.
Chapter 2 Configuring Horizon Client for End Users
VMware, Inc. 27Table 2‑4. Horizon Client Command-Line Options and Configuration File Keys (Continued)
Configuration Key Command-Line Option Description
view.sslCipherString –sslCipherString= Configures the cipher list to restrict the use of certain
cryptographic algorithms before establishing an
encrypted SSL connection.
For a list of cipher strings, see
http://www.openssl.org/docs/apps/ciphers.html .
Default is “AES:!aNULL:@STRENGTH”.
view.sslProtocolString –sslProtocolString= Configures 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.
Default is “TLSv1.0:TLSv1.1”.
view.sslVerificationMode None Sets the server certificate verification mode.
Specify “1” to reject connections when the certificate
fails any of the verification checks, “2” to warn but
allow connections that use a self-signed certificate, or
“3” to allow unverifiable connections. If you specify “3”
no verification checks are performed. Default is “2”.
view.xfreerdpOptions –xfreerdpOptions= (Available if you use the Microsoft RDP display
protocol) Specifies command-line options to forward to
the xfreerdp program. For information about
xfreerdp options, see the xfreerdp documentation.
NOTE To use FreeRDP, you must have the correct
version of FreeRDP installed, along with any applicable
patches. For more information, see “Install and
Configure FreeRDP,” on page 34.
None –enableNla (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 32.
NLA is turned off 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 Configure FreeRDP,” on
page 34.
NOTE The rdesktop program does not support NLA.
None –printEnvironmentInfo 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
None –usb= (Available only with distributions from third-party
vendors) Specifies which options to use for USB
redirection. See Chapter 6, “Configuring USB
Redirection on the Client,” on page 55.
None –version Displays version information about Horizon Client.
Using VMware Horizon Client for Linux
28 VMware, Inc.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 configuration 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=
Omitting any of these configuration settings 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.
NOTE If you set the view.sslVerificationMode configuration key, be sure to set it in
the /etc/vmware/view-mandatory-config file. When the client runs in kiosk mode, the client does not look in
the view-preferences file.
The command shown in this example runs Horizon Client on a Linux client system and has the following
characteristics:
n The user account name is based on the client`s MAC address.
n Horizon Client runs in full screen mode without a Horizon 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 display
an out-of-order screen or might wait a certain amount of time before attempting 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”
IMPORTANT If a pre-login message has been configured 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.
Chapter 2 Configuring Horizon Client for End Users
VMware, Inc. 29Configuring Certificate Checking for End Users
Administrators can configure the certificate verification mode so that, for example, full verification is always
performed.
Certificate checking occurs for SSL connections between View Connection Server and Horizon 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 Horizon
Client,” on page 39.
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.allowSslVerificationMode
property to “False” in the /etc/vmware/view-mandatory-config file on the client system. See “Horizon
Client Configuration Settings and Command-Line Options,” on page 22.
Configuring Advanced SSL Options
You can select the security protocols and cryptographic algorithms that are used to encrypt communications
between Horizon Client and View Connection Server and View Agent in the remote desktop.
These options are also used to encrypt the USB channel (communication between the USB service daemon
and View Agent).
The default setting includes cipher suites that use either 128-bit or 256-bit AES encryption, except for
anonymous DH algorithms, and sorts them by strength. By default, TLS v1.0 and TLS v1.1 are enabled. (SSL
v3.0, SSL v2.0, and TLS v1.2 are disabled.)
NOTE In Horizon Client 3.1 and later, the USB service daemon adds RC4 (:RC4-SHA: +RC4) to the end of
the cipher control string when it connects to a remote desktop.
You should change the security protocols in Horizon Client only if your View server does not support the
current settings. If you configure a security protocol for Horizon Client that is not enabled on the View
server to which the client connects, an SSL error occurs and the connection fails.
IMPORTANT If the only

Leave a Comment