User manual

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.
Configuring 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 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 49.
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.
Using VMware Horizon Client for Linux
38 VMware, Inc.