vortitronic.blogg.se

#VMWARE HORIZON CLIENT ONLINE LOGIN WINDOWS#

Disabled: The user has to enter login information if the client did not receive logon credentials.

For information on nested mode, see the VMware Horizon Client for Windows Installation and Setup Guide. For example, in a nested mode, True SSO is used to log on to a nested client and then a secondatry desktop logon was performed.

True SSO Integration: Enable this setting on Connection Server to allow SSO to the desktop using True SSO.

For more information, see the Microsoft documentation Note: If channel binding is enabled, confirm that NTLMv2 is turned on using the LMCompatibilityLevel switch and that the security level 3 or higher in the user environment.

On the Connection Server instance, enable the Accept logon as current user setting to allow the Connection Server instance to accept the user identity and credential information that is passed when users select Log in as current user in the Options menu in Horizon Client.

The session object resides in volatile memory and is not stored in Horizon LDAP or in a disk file. The session object is destroyed when the user logs out, the session times out, or authentication fails.

The credentials are added when authentication occurs and are purged when the session object is destroyed. On the Connection Server instance, user credentials are encrypted and stored in the user session along with the username, domain, and optional UPN.To support this feature, user credentials are stored on both the Connection Server instance and on the client system.

No further user authentication is required.

With Horizon Client for Windows, when users select Log in as current user in the Options menu, the credentials that they provided when logging in to the client system are used to authenticate to the Horizon Connection Server instance and to the remote desktop using Kerberos.

#VMWARE HORIZON CLIENT ONLINE LOGIN WINDOWS#