User manual

If you congure a security protocol for Horizon Client that is not enabled on the server to which the client
connects, a TLS/SSL error occurs and the connection fails.
I At least one of the protocols that you enable in Horizon Client must also be enabled on the
remote desktop. Otherwise, USB devices cannot be redirected to the remote desktop.
On the client system, you can use either conguration le properties or command-line options for these
seings:
n
To use conguration le properties, use the view.sslProtocolString and view.sslCipherString
properties.
n
To use command-line conguration options, use the --sslProtocolString and --sslCipherString
options.
For more information, see “Using the Horizon Client Command-Line Interface and Conguration Files,” on
page 26 and look up the property and option names in the table in “Horizon Client Conguration Seings
and Command-Line Options,” on page 27.
Configuring Specific Keys and Key Combinations to Send to the Local
System
Starting with Horizon Client, if you use PCoIP, or, starting with Horizon Client 4.0, it you use VMware Blast
or PCoIP, you can create a view-keycombos-config le to specify which individual keys and key
combinations should not be forwarded to the remote desktop.
You might prefer to have some keys or key combinations handled by your local client system when working
in a remote desktop. For example, you might want to use a particular key combination to start the screen
saver on your client computer. You can create a le located at /etc/vmware/view-keycombos-config and
specify the key combinations and individual keys.
Place each key or key combination on a new line using the following format:
<modName>scanCode
scanCode
The rst example is for a key combination. The second example is for a single key. The scanCode value is the
keyboard scan code, in hexadecimal.
In this example, modName is one of four modier keys: ctrl, alt, shift, and super. The Super key is
keyboard-specic. For example, the Super key is usually the Windows key on a Microsoft Windows
keyboard but is the Command key on a Mac OS X keyboard. You can also use <any> as a wildcard for
modName. For example, <any>0x153 species all combinations of the Delete key, including the individual
Delete key for the US keyboard. The value you use for modName is not case-sensitive.
Specifying the Scan Code for a Key
The scanCode value must be in hexadecimal format. To determine which code to use, open the appropriate
language- and keyboard-specic le in the lib/vmware/xkeymap directory on your client system. In addition
to the key codes listed in that le, you can also use the following codes:
Table 2‑5. Multimedia Keys
Key Name Scan Code
PREVIOUS_TRACK 0x110
NEXT_TRACK 0x119
MUTE 0x120
CALCULATOR 0x121
Using VMware Horizon Client for Linux
42 VMware, Inc.