Shutdown Event Tracker Best practices

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

Best practices

Plan to use Shutdown Event Tracker as a best practice.

Consider security when assigning shutdown user rights.

Use standard reasons instead of custom reasons.

  • Using the standard restart and shutdown reasons provided by Microsoft enables you to remotely browse event logs, and to use automated tools that will be available. in the future. In addition, using predefined reasons is a simpler approach than defining your own reasons. For guidance on how to define custom reasons, as well as a comprehensive list of the standard reasons, see "Tools for Troubleshooting" at the Microsoft Windows Resource Kits Web site.

Establish guidelines across your organization for choosing reasons and making comments.

  • Users should consistently use the restart and shutdown reasons displayed in the graphical user interface (GUI) to ensure the validity of the data collected. As a system administrator, you should establish and communicate specific guidelines for using each reason. You should also provide standards for information that users type in the Comment box, including when a comment is required, what information it should contain, and what form that information should take.

    For example, you may want to establish guidelines such as these:

    • If installing new software involves restarting a computer, use the reason Application: Installation (Planned). Always supply the name of the new software in the Comment box.

    • If repairing hardware forces you to immediately restart or shut down a computer, use the reason Hardware: Maintenance (Unplanned). Always supply the name of the hardware in the Comment box.