I’m literately sitting in a meeting room, and the conversation is focused on OSD with SCCM 2012 R2 and some of the difficulties the deployment guys face when they are troubleshooting task sequences. They complained about the log file location (mainly the smsts.log) and how it keeps changing location. Truth is, it has to, because quite a few things happen during a task sequence, as Im sure you understand.
So here are the locations of the smsts.log during a typical deployment …
1. It will start here x:\windows\temp\smstslog\smsts.log during a PXE boot and will stay here until the disk is formatted.
2. Once the drive has been formatted, it changes location to here x:\smstslog\smsts.log and c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
3. Once you’re in Windows and the SCCM agent hasn’t been installed the log files are here c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
4. Once you’re in windows and SCCM agent is installed, but the task sequence inst complete the log file can be found here c:\windows\ccm\logs\Smstslog\smsts.log
5. Once everything is finished and your task sequence is complete you can find the log file here c:\windows\ccm\logs\smsts.log
If you’re using USMT keep and eye out for the scanstate.log (capture user data) and loadstate.log (restore user data) – it helps with those “you’ve lost my data!” conversations.
And another good log file is the TSAgent.log this will explain the outcomes of dependencies before the task sequence starts, so if your task sequence dies immediately, have a look in here and see what missing.