Resolving Boot Failure Problems


Occasionally, a Windows Server 2003 system can suffer a service or application startup problem that could leave a server unable to complete a normal bootup sequence. Because the operating system cannot be accessed in this case, the system would remain unavailable until this problem can be resolved.

Windows Server 2003 includes a few alternative bootup options to help administrators restore a server to a working state. Several advanced bootup options can be accessed by pressing the F8 key when the boot loader screen is displayed. If the Recovery Console was previously installed, it is listed as an option in the boot loader screen. The Advanced boot options include:

  • Safe Mode This mode starts the operating system with only the most basic services and hardware drivers and disables networking. This allows administrators to access the operating system in a less functional state to make configuration changes to service startup options, some application configurations, and the System Registry.

  • Safe Mode with Networking This option is the same as Safe Mode, but networking drivers are enabled during operation. This mode also starts many more operating system services upon startup.

  • Safe Mode with Command Prompt This option is similar to the Safe Mode option; however, the Windows Explorer shell is not started by default.

  • Enable Boot Logging This option boots the system normally, but all the services and drivers loaded at startup are recorded in a file named ntbtlog.txt located in the %systemroot% directory. The default location for this file is c:\Windows\ntbtlog.txt. To simplify reading this file, the administrator needs to delete the existing file before a bootup sequence is logged so that only the information from the last bootup is logged.

  • Enable VGA Mode This mode loads the current display driver, but it displays the desktop at the lowest resolution. This mode is handy if a server is plugged in to a different monitor that cannot support the current resolution.

  • Last Known Good Configuration This mode starts the operating system using Registry and driver information saved during the last successful logon.

  • Directory Services Restore Mode This mode is only for domain controllers and allows for maintenance and restore of the Active Directory database or the SYSVOL folder.

  • Debugging Mode This mode sends operating system debugging information to other servers through a serial connection. This requires a server on the receiving end with a logging server that is prepared to accept this data. Most likely, standard administrators will never use this mode.

  • Start Windows Normally As the name states, this mode loads the operating system as it would normally run.

  • Reboot This option reboots the server.

  • Return to OS Choices Menu This option returns the screen back to the boot loader page so the correct operating system can be chosen and started.

The Recovery Console

The Recovery Console provides an option for administrators to boot up a system using alternate configuration files to perform troubleshooting tasks. Using the Recovery Console, the bootup sequence can be changed, alternate boot options can be specified, volumes can be created or extended, and service startup options can be changed. The Recovery Console has only a limited number of commands that can be used, making it a simple console to learn. If Normal or Safe mode bootup options are not working, the administrator can use the Recovery Console to make system changes or read the information stored in the boot logging file using the type command. The boot logging file is located at C:\Windows\ntbtlog.txt by default and exists only if someone tried to start the operating system using any of the Safe mode options or the boot logging option.




Microsoft Windows Server 2003 Unleashed(c) R2 Edition
Microsoft Windows Server 2003 Unleashed (R2 Edition)
ISBN: 0672328984
EAN: 2147483647
Year: 2006
Pages: 499

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net