The first step to troubleshoot SCCM OSD Task Sequence issues to is check out the log file – this is called smsts.log.
This can be found in one of several locations depending on the progress of the build and the architecture of the OS:
- Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log
- Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
- Full version Windows before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
- Full version Windows after SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log
- Full version Windows (x64) after SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
- After Task Sequence has finished running: c:\windows\system32\ccm\logs\smsts.log
- After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log
Of course, don’t even bother trying to open these with notpead, make sure you use the Trace32 tool found in the ConfigMgr 2007 Toolkit.
Whilst we are talking about SCCM logs, there is a great article here (http://blogs.msdn.com/lxchen/archive/2009/04/03/a-list-of-sccm-log-files.aspx) outlining a list of all SCCM log files.