Partager via

Respond if SAC and !SAC become unavailable

  • Article

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

To respond if SAC and !SAC become unavailable

Depending on the remote computer's hardware configuration, one or more of the following approaches can be helpful if Special Administration Console (SAC) and !SAC become unavailable. For more information, see your hardware manufacturer's documentation.

  • Perform diagnostic procedures using the service processor's out-of-band tools if a service processor is present, and if the tools are available.

  • Restart the remote computer by using the interface supplied by a service processor, if one is present.

  • Restart the remote computer by using the interface supplied by a power switch or an uninterruptible power supply (UPS) with remote computer management capabilities, if one is present.

  • If none of these approaches is appropriate, start the remote computer by pressing the power button.

Note

  • If you restart the remote computer using a power switch or UPS, its firmware must be configured to turn on when power is restored.

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also

Concepts

System-state diagram
Emergency Management Services Resources
Troubleshooting Emergency Management Services