Troubleshooting during OSD process

Thanks to Dave ( my collegue from Indy) for this!

Anytime the OSD process is in the WinPE state (up to the reboot to OS that displays the Win7 logo), you can hit the F8 key and a DOS window will appear. As long as the window is open, the imaging process will not reboot.
That means you can read logs and/or copy files off to a network share.

Create a network share: In the DOS window run the command net use q: \\server\share

Read logs: In the DOS window first type cd\ , then trace32 , click Yes. Now use the mouse to open a log file.

NOTE: See below for log file locations during OSD. They move around a lot depending upon where in the task sequence you are. Alternatively, map a drive as described above then copy and read the files off line.

The root of all Task Sequence troubleshooting is called smsts.log -- and this log is always the first step to troubleshooting any TS issue -- if you have an issue, look in here first!

Unfortunately, the smsts.log can be stored in one of 7 locations, depending on the stage of the build and the architecture of the OS:

WindowsPE, before HDD format:
x:\windows\temp\smstslog\smsts.log

WindowsPE, 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 x64 windows, 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


Checking Variable values: in the DOS window first type cd\ then type printtest.vbs .
Map a drive as described about and copy the file x:\osdvariables.txt off the computer to read. Alternatively, run the file test.vbs and read the variable one at a time in a pop up window, clicking OK or hitting Enter to go to the next one. NOTE: there are a LOT! This takes a while.

It is suggested that to read SCCM logs, you use the file trace32.exe.

http://www.experts-exchange.com/articles/OS/Microsoft_Operating_Systems/Server/Systems_Management_Server/SCCM-OSD-Basic-troubleshooting.html