Implementing disaster recovery would not be complete without a thorough discussion of Windows Server 2003 startup problems and issues. A successful startup includes the following segments:
Startup problems that occur after you select the operating system from the boot loader menu ( boot.ini file), or after you see the Please select the operating system to start message are usually the result of missing or corrupt startup files. You can use Safe Mode, the Recovery Console, or the Windows Server 2003 Repair feature to replace missing or corrupt files. Windows Server 2003 comes with a variety of startup troubleshooting tools and utilities. In the sections that follow, you'll learn the purpose of each utility and how to use each tool for troubleshooting the startup boot process. Using the System Information UtilityThe System Information utility displays a complete list of your computer's hardware resources, system hardware components , and software environment. To open and use the System Information utility, perform the following steps:
If you have forced hardware, conflict/sharing, problem device, or startup conflicts, use Device Manager to uninstall or disable the device. Device Manager is discussed next. Using Device ManagerYou can use Device Manager along with the System Information utility to identify and resolve device conflicts and incompatibilities related to startup problems. Device Manager provides a graphical view of all the hardware installed on your computer. To open and use Device Manager, perform the following steps:
Using Event ViewerYou should always be using Event Viewer to check, troubleshoot, and diagnose server startup problems. The System and Application event logs types depict general information with a blue I icon, warnings with a yellow icon containing an exclamation point, and errors with a red circle icon with an X inside. System events display Windows Server 2003 startup processes and services. Application events display startup network-related application events such as Backup and Exchange Server services. Double-clicking a warning or error displays the source, category, event ID, and description of the error or warning. Most error and warning events can be researched using Microsoft's Knowledge Base and searching for the event ID number.
Using Safe ModeStarting Windows Server 2003 in safe mode loads generic and basic drivers. You use safe mode to identify, troubleshoot, and resolve problems caused by corrupt or faulty drivers, programs, or services that automatically load at startup. If your computer does not successfully start in normal mode but does start in safe mode, hardware resource incompatibilities with programs, services, device drivers, or the Registry exist. To disable or uninstall the offending device, use Device Manager. To stop an errant service, open the Services utility, double-click the offending service, and choose Stop. To repair the Registry, use the Registry editor, Regedit. To remove a program, use the System Information tool that was just discussed. To troubleshoot startup problems using safe mode, perform the following steps:
You can also use the boot log file, Ntbtlog.txt , as a tool for troubleshooting drivers and services that did not load when you started your computer in safe mode. The log file is located in the %SystemRoot% folder and is viewed by using Notepad.
Using Last Known Good ConfigurationIf you make a change to your Windows Server 2003, such as installing a device driver, and the problem occurs immediately, you should try to start your server using the Last Known Good Configuration option in the Advanced Option menu. Using the Last Known Good Configuration feature restores the previous settings in the Registry key \HKLM\system\CurrentControlSet . If using the Last Known Good Configuration option solves your problem, you should either remove or update the offending driver. To troubleshoot startup problems using the last known good configuration, perform the following steps:
Using the Recovery ConsoleThe Recovery Console is a command-line tool that you can use to fix startup problems. Using the Recovery Console, you can access drives and directories, enable or disable errant drivers and services, copy files from a Windows 2003 installation disk or a manufacturer's disk, and create a new boot sector or a master boot record (MBR). Use the Recovery Console after you've unsuccessfully tried using the last known good configuration and safe mode recovery tools. To use the Recovery Console, perform the following steps:
The Recovery Console is also very useful for detecting and repairing hard drive problems. Use the command-line utility chkdsk with the f (fix) parameter switch to check or repair hard drives.
Using Automated System RecoveryUsing Automated System Recovery (ASR) for restoring failed Windows Server 2003 was discussed in detail at the beginning of this chapter. Remember, when all other recovery methods fail, ASR is your last choice.
Using the Repair OptionDamaged, corrupt, or missing installation files can sometimes be repaired using the Windows 2003 Repair feature. To utilize this feature, perform the following steps:
|