05.03.2013 Views

MCSA/MCSE Self-Paced Training Kit (Exam 70-270): Installing ...

MCSA/MCSE Self-Paced Training Kit (Exam 70-270): Installing ...

MCSA/MCSE Self-Paced Training Kit (Exam 70-270): Installing ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

21-42 Chapter 21 <strong>Installing</strong> Windows XP Professional (1.0)<br />

Objective 1.5<br />

Troubleshoot Failed Installations<br />

Setting up an operating system is an extremely complex procedure. The rich variety of<br />

hardware components provides an unlimited number of combinations that the setup<br />

routine must be able to accommodate. To make these procedures even more complex,<br />

Windows XP Professional is often installed on hardware that was designed after the<br />

release of the operating system.<br />

These complexities lead to occasional failures of the setup routine. Although these failures<br />

are challenging to resolve, Windows XP Professional makes this a much simpler<br />

process by providing detailed logging and debugging information. Understanding how<br />

to interpret these log files is critical to quickly resolving failed installations. If you find<br />

that these log files are not providing enough information to effectively troubleshoot a<br />

failed installation, detailed debugging can be enabled.<br />

The setup routine has three installation phases: the Setup Loader phase, the Text-<br />

Mode Setup phase, and the GUI-Mode Setup phase. Understanding which installation<br />

steps occur during each of these three stages is critical to troubleshooting a failed<br />

install.<br />

Throughout these setup phases, text-based log files are written to the local hard disk<br />

for later reference. These log files are located in the %systemroot% directory and end<br />

with a log file extension. After every successful and unsuccessful step of the installation<br />

routine, a detailed description of the action is appended to the various log files<br />

for later reference. Referring to these log files will uncover the nature of any problems<br />

experienced, even if the installation routine could complete successfully. If the<br />

installation routine fails, identifying the last log entries written helps isolate the<br />

nature of the failure.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!