HP Integrated Lights-Out 2 - Manual (Page 37)

You must comply with Microsoft license requirements which are the same as connecting through
the server's NIC. For instance, when set for administrative access, Terminal Services does not allow
more than two connections, regardless of whether the connections are through the server's NIC,
or iLO 2, or both.
Terminal Services warning message
Terminals Services users operating on Windows 2003 Server might notice the following when
using the Terminal Services passthrough feature of iLO 2. If a Terminal Services session is established
through iLO 2 and a second Terminal Services session is established by a Windows administrator
(Console mode), the first Terminal Services session is disconnected. However, the first Terminal
Services session does not 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 Passthrough option display
The iLO 2 firmware might not accurately display the Terminal Services Passthrough option. The
Terminal Services Passthrough option might appear active even if the operating system is not
Terminal Services enabled (for example, if the host operating system is Linux, which does not
support Terminal Services operation).
Remote Console and Terminal Services clients
Using the management network connection to the iLO 2, an iLO 2 Remote Console session can
be used to display a Terminal Services session to the host. When the iLO 2 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 Remote
Console cannot automatically launch the Terminal Services client.
If Terminal Services passthrough is enabled, and the Terminal Services server is available, switching
between iLO 2 Remote Console and the Terminal Services client will be seamless as the server
progresses from pre-operating system environment to operating system-running environment, to
operating system-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 passthrough option with Windows Server 2003 and Windows
Server 2008, a 30-second delay occurs 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 iLO 2.
The iLO 2 firmware passes through only one Terminal Services connection at a time. Terminal
Services has a limit of two concurrent sessions.
Configuring iLO 2 access 37