HP t420 Administrator Guide 8 - Page 51

Active Directory integration, Login screen, Single sign-on, Desktop

Page 51 highlights

6 Active Directory integration By using Active Directory integration, you can force users to log in to the thin client using domain credentials. Optionally, those credentials can be encrypted and stored and then later supplied to remote connections as they start, which is a process known as single sign-on. NOTE: Enabling authentication requires no special domain permissions. There are two modes in which Active Directory integration can operate. By simply enabling authentication against the domain, domain credentials can be used for the following operations: ● Logging in to the thin client ● Starting a connection using Single Sign-On ● Switching to administrator mode using administrative credentials ● Unlocking a locked screen using the login credentials ● Overriding a locked screen using administrative credentials The thin client can also be formally joined to the domain. This adds the thin client to the domain's database and might enable dynamic DNS, where the thin client informs the DNS server of changes in its IP address or hostname association. Unlike domain authentication, a formal join requires credentials of a domain user authorized to add clients to the domain. Joining to the domain is optional. All domain functions except dynamic DNS are available without joining. Login screen When domain authentication is enabled, ThinPro displays a domain login screen upon startup. The login screen also includes options that might be necessary to configure before logging in. The background desktop layout, login dialog style, login dialog text, and which buttons are available can all be adjusted via registry settings and/or configuration file settings. For more information, see the HP ThinPro white paper Login Screen Customization (available in English only). If the system detects that the user tried to log in with expired credentials, they are prompted to update their credentials. Single sign-on After a domain user has logged in, the credentials that were used can also be presented at startup to any connection configured to use them. This allows a user to sign in to the thin client and start Citrix, VMware Horizon View, and RDP sessions without having to enter their credentials again, for as long as they are logged in to the thin client. Desktop Once the user has successfully logged in using domain credentials, an Active Directory icon is available on the taskbar. The user can select the icon to perform the following functions: Login screen 39

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184

6
Active Directory integration
By using Active Directory integration, you can force users to log in to the thin client using domain credentials.
Optionally, those credentials can be encrypted and stored and then later supplied to remote connections as
they start, which is a process known as single sign-on.
NOTE:
Enabling authentication requires no special domain permissions.
There are two modes in which Active Directory integration can operate. By simply enabling authentication
against the domain, domain credentials can be used for the following operations:
Logging in to the thin client
Starting a connection using Single Sign-On
Switching to administrator mode using administrative credentials
Unlocking a locked screen using the login credentials
Overriding a locked screen using administrative credentials
The thin client can also be formally joined to the domain. This adds the thin client to the domain’s database
and might enable dynamic DNS, where the thin client informs the DNS server of changes in its IP address or
hostname association. Unlike domain authentication, a formal join requires credentials of a domain user
authorized to add clients to the domain. Joining to the domain is optional. All domain functions except
dynamic DNS are available without joining.
Login screen
When domain authentication is enabled, ThinPro displays a domain login screen upon startup. The login
screen also includes options that might be necessary to
configure
before logging in.
The background desktop layout, login dialog style, login dialog text, and which buttons are available can all be
adjusted via registry settings and/or
configuration
file
settings. For more information, see the HP ThinPro
white paper
Login Screen Customization
(available in English only).
If the system detects that the user tried to log in with expired credentials, they are prompted to update their
credentials.
Single sign-on
After a domain user has logged in, the credentials that were used can also be presented at startup to any
connection
configured
to use them. This allows a user to sign in to the thin client and start Citrix, VMware
Horizon View, and RDP sessions without having to enter their credentials again, for as long as they are logged
in to the thin client.
Desktop
Once the user has successfully logged in using domain credentials, an Active Directory icon is available on the
taskbar. The user can select the icon to perform the following functions:
Login screen
39