Active Directory Integration HP ThinPro - Technical white paper

3
• root/domain/loginAtStart
– Default Value: 1
– Description: If set to 1 and the thin client has been added to the domain, the thin client boots to a login screen.
Otherwise, it boots to the legacy HP ThinPro shared desktop.
• root/domain/allowSmartcard
– Default Value: 1
– Description: This key is currently unused.
• root/domain/retainUserRegistry
– Default Value: 1
– Description: If set to 1, any custom settings changes made by the user (such as the mouse-handedness) are retained
between login sessions.
• root/domain/enableDomainUsers
– Default Value: 0
– Description: If set to 1, only members of the group listed in root/domain/domainUserGroup can log in to the
domain. If set to zero, any valid domain credential can be used to log in to the thin client.
• root/domain/domainUsersGroup
– Default Value: Domain Users
– Description: If enableDomainUsers is set to 1, domain logins are limited to direct members of this group. Nested
groups are not supported for this feature.
• root/domain/enablePasswordChange
– Default Value: 1
– Description: If set to 1, the user can change their domain password directly from the thin client.
• root/domain/enableDomainAdmin
– Default Value: 1
– Description: If set to 1, members of the group listed in domainAdminGroup can switch between user mode and
administrator mode. If set to 0, the local root account must be used to perform local administrative tasks.
• root/domain/domainAdminGroup
– Default Value: Domain Admins
– Description: If enableDomainAdmin is set to 1, members of this group switch between user mode and
administrator mode.
• root/domain/enableSSO
– Default Value: 1
– Description: If set to 1, encrypted current credentials are cached in the memory and can be reused when starting
remote connections.
• root/domain/cacheDomainLogin
– Default Value: 0
– Description: If set to 1, the domain login credentials are saved to the disk as a hash, enabling subsequent logins to
occur even if the Active Directory server is inaccessible.
Active Directory domain profiles
Several tools can use an XML profile to manage HP ThinPro settings, including HP ThinState, HP Smart Client Services, and
HP Device Manager (HPDM). The following considerations for the profile apply when the profile is used to manage a thin
client on an Active Directory domain.
• Profiles that are intended for devices that authenticate against a domain database or join to a domain must contain the
appropriate values for the registry keys in root/domain.
An HP ThinPro profile must contain the complete state of registry values required. Registry keys not present in a profile
are set to their default values. Because of this behavior, the contents of root/domain in the profile must match the
desired state of the thin client.
In particular, if you use HP Smart Client Services to construct a profile for a thin client, it is essential that the profile
contain the full state of registry keys required, and not just the changes. You can import a profile into HP Smart Client
Services and then edit it. HP recommends this procedure if some thin client configuration has already been performed.