Choosing Out-of-Band Management Tools
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
If you cannot manage a server by using conventional in-band tools for some reason, an out-of-band connection is the only way to remotely manage it. If you configure your servers for remote administration, and you cannot access them by using your in-band tools, an out-of-band connection is the only way to manage them.
To configure a server for out-of-band management, you need to consider software, firmware, and hardware. Emergency Management Services, which is included with Windows Server 2003, is the principal out-of-band component. With only Emergency Management Services and a serial port, you can manage most Windows Server 2003 operating states. When you combine Emergency Management Services with supporting firmware and hardware components, you can also perform tasks ranging from powering up computers to recovering unresponsive systems — everything, in fact, except for replacing and installing hardware.
The additional components you choose depend on which tasks you want to perform remotely, how much you are willing to spend for extra features, and how many servers you have to manage. The following tools and components work with Emergency Management Services to support out-of-band remote management:
Firmware — BIOS for x86-based computers or EFI for Itanium-based computers — that provides console redirection
Serial ports and modems
Terminal concentrators
Service processors
Intelligent UPSs or intelligent power switches
By selecting the optional components that best meet your remote management requirements, you can capitalize on the full range of out-of-band management capabilities supported by Emergency Management Services.
For more information about selecting hardware components, see "Best practices for selecting and configuring hardware" in Help and Support Center for Windows Server 2003.
Table 5.3 shows which out-of-band tools support various operating states and remote management tasks.
Table 5.3 Components Required for Out-of-Band Situations
| Operating State or Task | Type of Tool |
|---|---|
Windows Server 2003 is starting |
Emergency Management Services |
Server fails to fully initialize |
Emergency Management Services |
Administrator needs to run Recovery Console |
Emergency Management Services |
Server is not functioning due to stop message |
Emergency Management Services |
System is low on resources, resulting in slow or no response to requests |
Emergency Management Services |
Network stack has malfunctioned or failed |
Emergency Management Services |
System is not responding on the network |
Emergency Management Services |
System is not responding on the network or to Emergency Management Services |
Service processor |
System is powered down |
Wake-on-LAN network adapter*, intelligent UPS, intelligent power switch, or service processor |
BIOS is conducting POST |
Redirecting firmware or service processor |
Change firmware configuration settings |
Redirecting firmware or service processor |
Operating system installation by using RIS |
Emergency Management Services (see "Selecting the Installation Method" later in this chapter |
* Wake-on-LAN is a combined hardware and software technology that allows you to remotely turn on Advanced Configuration and Power Interface (ACPI)–compliant computers. Several vendors provide Wake-on-LAN remote management solutions. Some vendors support this functionality across a local area network (LAN) or wide area network (WAN), while some support it over the Internet. For more information about Wake-on-LAN technology, use a Web search engine and search using the keyword "Wake-on-LAN."
Some trade-offs you might experience with out-of-band components include:
Limited maximum throughput.
No GUI support.
Optionally, additional hardware requirements.