How to copy SMSTS log file during Task Sequence Failure – When you are deploying OS using SCCM there are chances that your deployment might fail. You see that your task sequence fails with an error code. The next step that you do is find out why the deployment failed. The error code is always important to understand why the deployment failed.
But unfortunately not all error codes reveal the exact issue. You need to dig in much deeper and look at the log files to understand why your Task Sequence failed. One of the basic log file that helps you in OSD troubleshooting is SMSTS.log file. This file changes it’s location as the task sequence progresses. Here is a list of all the SCCM log files.
How to copy SMSTS log file during Task Sequence Failure
Once you find out the location of SMSTS log file, the next step is to open it and check for the errors. You could bring up command prompt by pressing F8 key during OSD. Then use the cmtrace command to bring up the log viewer. However it would be cool to copy the SMSTS log file during the task sequence failure. You could copy the log files to a shared folder on a remote computer. This will make your task easier as you get time to analyze the log files and it is much faster (compared to accessing the same file during OSD).
So in the below screenshot my task sequence has failed with error code 0x80070002. I have brought up the command prompt by pressing F8 key. I can now launch the cmtrace tool from the command prompt and read the log files. But instead of that we will see how to copy those to a shared location.
net use letter: \\servername\drive$ /user:domain\username password