HP Xw460c HP Integrated Lights-Out 2 User Guide for Firmware 1.75 and 1.77 - Page 38

Terminal Services troubleshooting

Page 38 highlights

When using the Terminal Services pass-through option with Windows Server® 2003 and Windows Server® 2008, there is approximately a 30-second delay after the CTRL-ALT-DEL dialog box appears before the Terminal Services client launches. The 30-second delay represents how long it takes for the service to connect to the RDP client running on the server. If the server is rebooted from the Terminal Services client, the Remote Console screen turns grey or black for up to one minute while iLO 2 determines that the Terminal Services server is no longer available. If Terminal Services mode is set to Enabled, but you want to use the Remote Console, then launch the Terminal Services client directly from the Terminal Services client menu. Launching directly from the client menu enables simultaneous use of the Terminal Services client and the Remote Console. Terminal Services can be disabled or enabled at any time. Changing the Terminal Services configuration causes the iLO 2 firmware to reset. Resetting the iLO 2 firmware interrupts any open connections to iLO 2. When the Terminal Services client is launched by the Remote Console, Remote Console goes into a sleep mode to avoid consuming CPU bandwidth. Remote Console still listens to the Remote Console default port 23 for any commands from the iLO 2. iLO 2 passes through only one Terminal Services connection at a time. Terminal Services has a limit of two concurrent sessions. The Remote Console activates and becomes available if the Remote Console is in sleep mode and the Terminal Services client is interrupted by any of the following events: • The Terminal Services client is closed by the user. • The Windows® operating system is shut down. • The Windows® operating system locks up. Terminal Services troubleshooting To resolve problems with iLO 2 Terminal Services Passthrough: 1. Verify that Terminal Services is enabled on the host by selecting My Computer>Properties>Remote>Remote Desktop. 2. Verify that the iLO 2 pass-through configuration is enabled or automatic in the iLO 2 Global Settings. 3. Verify that iLO Advanced Pack is licensed. 4. Verify that the iLO 2 Management Interface Driver is installed on the host. To verify the driver, select My Computer>Properties>Hardware>Device Manager>Multifunction Adapters. 5. Verify that the Terminal Services Pass-Through service and iLO 2 Proxy are installed and running on the host. To verify these services, select Control Panel>Administrative Tools>Services and attempting to restart the service. 6. Verify that the Application Event Log is not full. The Terminal Services Pass-Through service might experience start-up problems when the operating system Application Event Log is full. To view the event log, select Computer Management>System Tools>Event Viewer>Application. 7. Verify that the Terminal Services port assignment is correct. 8. Verify that the Terminal Services client, mstsc.exe is located in \WINDOWS\SYSTEM32. If not, set the pass-through configuration to Enabled, and manually activate the terminal services client. Configuring iLO 2 38

  • 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

Configuring iLO 2 38
When using the Terminal Services pass-through option with Windows Server® 2003 and Windows
Server® 2008, there is approximately a 30-second delay after the CTRL-ALT-DEL dialog box appears
before the Terminal Services client launches. The 30-second delay represents how long it takes for the
service to connect to the RDP client running on the server. If the server is rebooted from the Terminal
Services client, the Remote Console screen turns grey or black for up to one minute while iLO 2
determines that the Terminal Services server is no longer available.
If Terminal Services mode is set to Enabled, but you want to use the Remote Console, then launch the
Terminal Services client directly from the Terminal Services client menu. Launching directly from the client
menu enables simultaneous use of the Terminal Services client and the Remote Console.
Terminal Services can be disabled or enabled at any time. Changing the Terminal Services configuration
causes the iLO 2 firmware to reset. Resetting the iLO 2 firmware interrupts any open connections to iLO 2.
When the Terminal Services client is launched by the Remote Console, Remote Console goes into a sleep
mode to avoid consuming CPU bandwidth. Remote Console still listens to the Remote Console default port
23 for any commands from the iLO 2.
iLO 2 passes through only one Terminal Services connection at a time. Terminal Services has a limit of
two concurrent sessions.
The Remote Console activates and becomes available if the Remote Console is in sleep mode and the
Terminal Services client is interrupted by any of the following events:
The Terminal Services client is closed by the user.
The Windows® operating system is shut down.
The Windows® operating system locks up.
Terminal Services troubleshooting
To resolve problems with iLO 2 Terminal Services Passthrough:
1.
Verify that Terminal Services is enabled on the host by selecting
My
Computer>Properties>Remote>Remote Desktop.
2.
Verify that the iLO 2 pass-through configuration is enabled or automatic in the iLO 2 Global Settings.
3.
Verify that iLO Advanced Pack is licensed.
4.
Verify that the iLO 2 Management Interface Driver is installed on the host. To verify the driver, select
My Computer>Properties>Hardware>Device Manager>Multifunction Adapters.
5.
Verify that the Terminal Services Pass-Through service and iLO 2 Proxy are installed and running on
the host. To verify these services, select
Control Panel>Administrative Tools>Services
and attempting
to restart the service.
6.
Verify that the Application Event Log is not full.
The Terminal Services Pass-Through service might experience start-up problems when the operating
system Application Event Log is full. To view the event log, select
Computer Management>System
Tools>Event Viewer>Application.
7.
Verify that the Terminal Services port assignment is correct.
8.
Verify that the Terminal Services client,
mstsc.exe
is located in
\WINDOWS\SYSTEM32.
If not, set the pass-through configuration to
Enabled
, and manually activate the terminal services
client.