When Things go wrong during MDT Deployment (Part 2) October 23, 2009

Posted by keithga in MDT 2010, Troubleshooting.
Tags: Logs, MDT, Troubleshooting
trackback

Other Log files…

In a continuation of my last post on debugging Litetouch failures by viewing the bdd.log file. Let me also discuss some of the *other* log files that may appear during a Litetouch Deployment.

• During WinPE bootup, there may be problems with the WinPE itself, for example the network driver may fail to load. Look in x:\windows\system32\WPEInit.log, for details
• During Windows Vista and Windows 7 setup, any setup errors should be logged in the panther directory. A good description of these files, and where they are located can be found here: http://support.microsoft.com/kb/927521.
• When performing a domain join, Windows will write logging information to: c:\windows\debug\netsetup.log.
• During a State Capture and State Restore (USMT), MDT will write to the standard MDT log file locations to the files: USMTEstimate.log, USMTCapture.log, USMTRestore.log.
• Finally, in Litetouch scenarios, when processing the tasks defined in the task sequence list, the SCCM Stand Alone Task Sequencer will write to a file called smsts.log. Typically this file is located at %Temp%\smsts.log. However, you can also tell by searching within the bdd.log file. If Litetouch sees where the smsts.log file is located then it will log the path. Just search for smsts.log. Also, when complete, Litetouch will archive the smsts.log file to the c:\windows\temp\deploymentlogs\smsts.log location like bdd.log.

Keith

Keith Garner is a Deployment Specialist with Xtreme Consulting Group