HP 232664-006 manual Terminal Services pass-through option, Terminal Services Client requirements

The Windows® EMS Console, if enabled, provides the ability to perform EMS in cases where video, device drivers, or other operating system features have prevented normal operation and normal corrective actions from being performed.

The Windows® EMS serial port must be enabled through the host system RBSU. The configuration allows for the enabling or disabling of the EMS port, and the selection of the COM port. The RILOE II system will automatically detect whether the EMS port is enabled or disabled, and the selection of the COM port.

To obtain the SAC> prompt, typing Enter might be required after connecting through the Virtual Serial Port console.

For more information on using the EMS features, refer to the Windows® Server 2003 Server documentation.

Terminal Services pass-through option

Terminal Services is provided by the Microsoft® Windows® operating systems. The RILOE II Terminal Services pass-through option provides a connection between the Terminal Services server on the host system and the Terminal Services client on the client system. When the Terminal Services pass-through option is enabled, RILOE II firmware sets up a socket, listening by default on port 3389. All data received from the Terminal Services on this port is forwarded to the server and all data it receives from the server is forwarded back to the socket. The firmware assumes anything received on this port is in an RDP packet. RDP packets are exchanged between the RILOE II firmware and the server's Terminal Services (RDP) server through the localhost address on the server. A service is provided to facilitate communications between the RILOE II firmware and the RDP server, such that the RDP server believes that an external RDP connection has been established. For more information on RDP service, refer to the "Windows® RDP Pass- Through service (on page 42)" section.

A Terminal Services session provides a performance-enhanced view of the host system console. When the operating system is unavailable (or the Terminal Services server or client is unavailable), the traditional RILOE II remote console provides the view of the host system console. For more information on Remote Console and Terminal Services, refer to the "Remote Console and Terminal Services clients (on page 44)" section.

To configure the Terminal Services pass-through option, refer to "Terminal Services Client requirements (on page 41)" and "Terminal Services Pass Through installation ("Terminal Services pass-through installation" on page 42)."

Terminal Services Client requirements

The Terminal Services client is available on Microsoft® Windows® client machines running:

•Windows® 2000

Microsoft® Windows® 2000 servers require the installation of Microsoft® .NET Framework to support the use of Terminal Services. After .NET Framework is installed, the Terminal Services client must be installed from diskettes created by the Terminal Services server. Consult your Windows® operating guides or help files for instructions. When installing the Terminal Services client on Windows® 2000, use the default installation location. The Terminal Services client in Windows® 2000 generates a dialog box asking for which target Terminal Services server to use.

•Windows® Server 2003

On Windows® Server 2003 servers, the Terminal Services client and RDP connection is built in. The client is an integral part of the operating system and is activated using Remote Desktop sharing. To activate desktop sharing allow, select My Computer>Properties>Remote>Remote Desktop. The Terminal Services client in Windows® Server 2003 provides command line options and seamless launches from the Remote Console applet.

•Windows® XP

Using the RILOE II 41