HP Z620 HP Remote Graphics Software 5.4.7 - Page 85

Chaining custom GINA modules for Easy Login (Windows XP Professional only)

Page 85 highlights

Chaining custom GINA modules for Easy Login (Windows XP Professional only) If it is determined in step 3 above that the GinaDLL registry key does exist, and the value of the key is not msgina.dll, then a custom GINA module is currently loaded and being used by WinLogon. Custom GINA modules provide custom authentication dialogs or even custom user authentication methods. If it is determined that functionality of both the RGS Easy Login and a custom GINA module is required, the hprgina.dll needs further configuration. The hprgina.dll module needs to be set up to load the custom GINA module rather than the default msgina.dll as described above. There are three ways to enable the hprgina.dll module to load a custom GINA module: Install time specification of the custom GINA module A custom GINA module can be chained by the hprgina.dll at install time. This is the preferred method. The installer will bring up a GUI that allows the Easy Login GINA module (hprgina.dll) to be enabled, as well as provides a text box to enter the name of the custom GINA module. The name of the custom module is all that is needed, provided it is installed in the C:\WINDOWS\system32 directory. If the custom module is installed elsewhere, the full file path needs to be entered. Using the rgadmin tool to specify a custom GINA module The rgadmin tool can be used to chain a custom GINA module. When Enable Easy Login is selected, the associated text entry box Chained GINA Dll is not grayed out. Enter the name of the custom GINA module in the text box, and click Apply. Using the rgadmin tool to specify a custom GINA module is preferred over the manual method, described next. Manually enabling hprgina.dll to load a custom GINA module To manually enable the hprgina.dll module to load a custom GINA module, create a new registry key, ChainedGinaDLL, with the value of the key containing the name of the chained custom GINA module. Perform steps 1-6 shown above (the restart will be done below) plus the following three steps to chain custom modules: 1. Create the ChainedGinaDLL registry key. Create the key as type REG_SZ (a string type). The full path of the key is: HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\Remote Graphics Sender \ChainedGinaDLL 2. Set the value of the new ChainedGinaDLL key to the name of the custom GINA module. For example, if the name of the custom GINA module is foogina.dll, then the value of the key should be foogina.dll. The value should match the string originally discovered in the registry key GinaDLL. Confirm the spelling before closing. 3. Restart the computer. When the RGS hprgina.dll is loaded by WinLogon, hprgina.dll will load the chained GINA module foogina.dll. The hprgina module then chains all GINA requests to the foogina.dll module. If the custom foogina.dll is also a chaining GINA module, foogina.dll, in turn, chains itself to the msgina.dll module. Three GINA DLLs will be loaded as part of the WinLogon.exe process: (1) hprgina.dll, (2) foogina.dll, and (3) msgina.dll. Installing RGS on Windows 69

  • 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
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247

Chaining custom GINA modules for Easy Login (Windows XP Professional
only)
If it is determined in step 3 above that the GinaDLL registry key does exist, and the value of the key is
not msgina.dll, then a custom GINA module is currently loaded and being used by WinLogon. Custom
GINA modules provide custom authentication dialogs or even custom user authentication methods. If it
is determined that functionality of both the RGS Easy Login and a custom GINA module is required, the
hprgina.dll needs further configuration. The hprgina.dll module needs to be set up to load the custom
GINA module rather than the default msgina.dll as described above. There are three ways to enable
the hprgina.dll module to load a custom GINA module:
Install time specification of the custom GINA module
A custom GINA module can be chained by the hprgina.dll at install time. This is the preferred method.
The installer will bring up a GUI that allows the Easy Login GINA module (hprgina.dll) to be enabled,
as well as provides a text box to enter the name of the custom GINA module. The name of the custom
module is all that is needed, provided it is installed in the C:\WINDOWS\system32 directory. If the
custom module is installed elsewhere, the full file path needs to be entered.
Using the rgadmin tool to specify a custom GINA module
The rgadmin tool can be used to chain a custom GINA module. When
Enable Easy Login
is
selected, the associated text entry box
Chained GINA Dll
is not grayed out. Enter the name of the
custom GINA module in the text box, and click
Apply
. Using the rgadmin tool to specify a custom
GINA module is preferred over the manual method, described next.
Manually enabling hprgina.dll to load a custom GINA module
To manually enable the hprgina.dll module to load a custom GINA module, create a new registry key,
ChainedGinaDLL, with the value of the key containing the name of the chained custom GINA module.
Perform steps 1–6 shown above (the restart will be done below) plus the following three steps to chain
custom modules:
1.
Create the ChainedGinaDLL registry key. Create the key as type REG_SZ (a string type). The full
path of the key is:
HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\Remote Graphics Sender
\ChainedGinaDLL
2.
Set the value of the new ChainedGinaDLL key to the name of the custom GINA module. For
example, if the name of the custom GINA module is foogina.dll, then the value of the key should
be foogina.dll. The value should match the string originally discovered in the registry key GinaDLL.
Confirm the spelling before closing.
3.
Restart the computer.
When the RGS hprgina.dll is loaded by WinLogon, hprgina.dll will load the chained GINA
module foogina.dll. The hprgina module then chains all GINA requests to the foogina.dll module.
If the custom foogina.dll is also a chaining GINA module, foogina.dll, in turn, chains itself to the
msgina.dll module. Three GINA DLLs will be loaded as part of the WinLogon.exe process: (1)
hprgina.dll, (2) foogina.dll, and (3) msgina.dll.
Installing RGS on Windows
69