Remote Console And Terminal Services Clients - HP Integrated Lights-Out User Manual

receive the warning message indicating the disconnection until approximately one minute later. During
this one-minute period, the first Terminal Services session is available or active. This is normal behavior,
but it is different than the behavior observed when both Terminal Services sessions are established by
Windows® administrators. In that case, the warning message is received by the first Terminal Services
session immediately.
Terminal Services button display
This version of the iLO firmware does not accurately display through the Terminal Services button whether
the host operating system is enabled for Terminal Services operation. Even if the operating system is not
enabled (for example, the host operating system is Linux, which does not support Terminal Services
operation), the Terminal Services button might not appear inactive and might inaccurately imply that
Terminal Services operation is available.

Remote Console and Terminal Services clients

Using the management network connection to the iLO, an iLO Remote Console session can be used to
display a Terminal Services session to the host. When the iLO Remote Console applet runs, it launches the
Terminal Services client based on user preference. The Sun JVM must be installed to obtain full
functionality of this feature. If the Sun JVM is not installed, then the dual-cursor Remote Console cannot
automatically launch the Terminal Services client.
If Terminal Services pass-through is enabled, and the Terminal Services server is available, switching
between iLO Remote Console and the Terminal Services client will be seamless as the server progresses
from pre-OS environment to OS-running environment, to OS-not available environment. The seamless
operation is available as long as the Terminal Services client is not started before Remote Console is
available. If Remote Console is available, and the Terminal Services client is available, Remote Console
will start the Terminal Services client when appropriate.
When using the Terminal Services pass-through option with Windows® 2000, there is approximately a
one-minute delay after the CTRL-ALT-DEL dialog box appears before the Terminal Services client launches.
On Windows® Server 2003, the delay is about 30 seconds. 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
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 the Terminal
Services client should be launched directly from the Terminal Services client menu. Launching directly from
the client menu allows 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 firmware to reset. Resetting the iLO firmware interrupts any open connections to iLO.
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.
iLO 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:
The Terminal Services client is closed by the user.
Configuring iLO 39