Console Redirection by Firmware

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Console redirection provided by system firmware (either BIOS for x86-based computers or EFI for Itanium-based computers) provides out-of-band access to server information before the Windows Server 2003 operating system starts. Firmware console redirection works together with Emergency Management Services console redirection to provide out-of-band support for any operating state.

If your firmware does not provide console redirection — and you do not have a service processor that provides console redirection, as described later in this chapter — you cannot remotely manage servers during the time between system restart and the initial loading of the Windows Server 2003 operating system.

If you configure your servers for remote administration, you need to have either firmware console redirection or a service processor with console redirection so that you can access the servers when the Windows Server 2003 operating system is not functioning.

Note

  • Firmware console redirection typically redirects only during text mode, not during GUI mode.

By using firmware console redirection, you can perform the following out-of-band tasks from a remote computer:

  • View server status before the operating system starts up. For example, you can view POST status or disk-related error messages. Firmware console redirection typically allows the POST to complete without a local keyboard, mouse, or monitor.

  • View and make modifications to firmware settings, such as disabling a peripheral device or changing boot sequence, with the built-in firmware configuration program.

  • View master boot record (MBR) errors.

  • Start a RIS-based setup by responding to the F12 network boot prompt. This support is required only if the F12 prompt is presented by the firmware.

  • Boot the computer from the CD drive by responding to the Press Any Key to Boot from CD prompt.

When assessing firmware console redirection for use in conjunction with Emergency Management Services, verify that the firmware meets the following criteria:

  • Shares the serial port with Emergency Management Services and releases control to Emergency Management Services after the Windows operating system starts.

  • Supports VT-UTF8, VT100+, or, at minimum, VT100 terminal emulator conventions. For more information, see "Management Software for Out-of-Band Connections" later in this chapter.

  • Preferably, supports the Serial Port Console Redirection (SPCR) table.

An SPCR table is provided with some ACPI-compliant system firmware for specifying how the out-of-band management port is used. For example, if the out-of-band port is a serial port, the SPCR table contains information such as serial port number, baud rate, terminal type, and other settings used for out-of-band communication. When this table exists, Emergency Management Services uses the information in it to ensure a consistent transition between firmware console redirection and Emergency Management Services console redirection. The SPCR table is recommended for use with both 32-bit and 64-bit versions of Windows Server 2003. For more information about the SPCR table and Emergency Management Services, see the Storage Technologies Collection of the Windows Server 2003 Technical Reference (or see the Storage Technologies Collection on the Web at https://www.microsoft.com/reskit).