User manual

Table 3‑5. Horizon Client Configuration Template: Security Settings (Continued)
Setting Description
Certificate verification mode
(Computer Conguration seing)
Congures the level of certicate checking that is performed by Horizon Client.
You can select one of these modes:
n
No Security. Horizon does not perform certicate checking.
n
Warn But Allow. A self-signed certicate is provided by Horizon. In this
case, it is acceptable if the certicate name does not match the Connection
Server name provided by the user in Horizon Client.
If any other certicate error condition occurs, Horizon displays an error
dialog and prevents the user from connecting to Connection Server.
Warn But Allow is the default value.
n
Full Security. If any type of certicate error occurs, the user cannot
connect to Connection Server. Horizon displays certicate errors to the user.
When this group policy seing is congured, users can view the selected
certicate verication mode in Horizon Client but cannot congure the seing.
The SSL conguration dialog box informs users that the administrator has
locked the seing.
When this seing is not congured or disabled, Horizon Client users can select a
certicate verication mode.
To allow a server to perform checking of certicates provided by
Horizon Client, the client must make HTTPS connections to the Connection
Server or security server host. Certicate checking is not supported if you o-
load SSL to an intermediate device that makes HTTP connections to the
Connection Server or security server host.
If you do not want to congure this seing as a group policy, you can also
enable certicate verication by adding the CertCheckMode value name to one
of the following registry keys on the client computer:
n
For 32-bit Windows: HKEY_LOCAL_MACHINE\Software\VMware,
Inc.\VMware VDM\Client\Security
n
For 64-bit Windows: HKLM\SOFTWARE\Wow6432Node\VMware,
Inc.\VMware VDM\Client\Security
Use the following values in the registry key:
n
0 implements No Security.
n
1 implements Warn But Allow.
n
2 implements Full Security.
If you congure both the group policy seing and the CertCheckMode seing in
the Windows Registry key, the group policy seing takes precedence over the
registry key value.
N In a future release, conguring this seing using the Windows registry
might not be supported. A GPO seing must be used.
Default value of the 'Log in
as current user' checkbox
(Computer and User Conguration
seing)
Species the default value of the Log in as current user check box on
theHorizon Client connection dialog box.
This seing overrides the default value specied during Horizon Client
installation.
If a user runs Horizon Client from the command line and species the
logInAsCurrentUser option, that value overrides this seing.
When the Log in as current user check box is selected, the identity and
credential information that the user provided when logging in to the client
system is passed to the Connection Server instance and ultimately to the remote
desktop. When the check box is deselected, users must provide identity and
credential information multiple times before they can access a remote desktop.
This seing is disabled by default.
The equivalent Windows Registry value is LogInAsCurrentUser.
Using VMware Horizon Client for Windows
48 VMware, Inc.