This article details where to find the smsts.log file and instructions on how to copy the log for review or sending to another team. The log file provides information on the imaging process and can be useful when trying to figure out why the imaging process failed.
In this article:
- Opening the Command Prompt Window
- Mapping a Network Drive
- Log File Location by Stage
- Copying the Log
- Common Failure Situations
- Additional Information
Opening the Command Prompt Window
During the imaging process, the Windows PE environment allows you to open the Command Prompt (cmd.exe) window for troubleshooting and other tasks.
- Press the F8 key on the keyboard. The Command Prompt window opens.
Note: While the Command Prompt window is open, any reboot started by the Task Sequence will be paused. If a reboot is paused, it will continue automatically when you close the Command Prompt window.
Mapping a Network Drive
Follow these steps to map a network drive before copying the log file.
- Press the F8 key on the keyboard.
- The Command Prompt window opens.
- Enter the following command to map a network drive:
net use N: \\files.umn.edu\<dept>\<share>\<folder> /USER:AD.UMN.EDU\<InternetID>
- Enter your password when prompted.
- A message that the command completed successfully will appear.
- If you are unsuccessful, make sure you entered the correct file path, username, and password then try again.
Log File Location by Stage
The smsts.log file can be found in different locations depending on where in the imaging process the failure happened. You will use the file path when copying the log to a mapped network drive, USB drive, etc.
Stage |
Step |
Log File Path |
---|---|---|
During OS Deployment |
Before the hard drive is formatted and partitioned |
X:\windows\temp\smstslog |
During OS Deployment |
After the hard drive is formatted and partitioned |
X:\smstslog |
Within Windows |
Before the ConfigMgr agent is installed |
C:\_SMSTaskSequence\logs\smstslog |
Within Windows |
After the ConfigMgr agent is installed |
C:\windows\ccm\logs\smstslog |
Within Windows |
When the Task Sequence completes |
C:\windows\ccm\logs |
Copying the Log
- Press the F8 key on the keyboard.
- The Command Prompt window opens.
- Using the Log File Location by Stage table in this document, determine where the smsts.log file is.
- Copy the smsts.log file to the applicable drive letter (mapped network drive, USB drive, etc.):
copy <Log File Path>\smsts.log <Drive>:\[NewFilename.log]
Example:copy X:\windows\temp\SMSTSLog\smsts.log N:\samplesmsts.log
- A message that the file was copied appears.
- If you are unsuccessful, make sure you entered the correct file paths and try again.
Common Failure Situations
These are a few common scenarios that you might encounter and the steps you can take to get the smsts.log file.
- The Task Sequence Wizard password was accepted but no policy could be found for the device
- Press the F8 key on your keyboard to open the Command Prompt window before the computer reboots.
- Map a network drive.
- Copy the Log file from: X:\windows\temp\smstslog\
- Task sequence failed at some random point before the computer reboots
- Press the F8 key on your keyboard to open the Command Prompt window before the computer reboots.
- Map a network drive.
- Copy the Log file from one of the applicable C: drive locations using the Log File Location by Stage table in this document.
- Task sequence failed at some random point and the computer rebooted
- Boot from media (USB, ISO, CD, etc.) or Preboot Execution Environment (PXE).
- Do not enter the Task Sequence Wizard password, leave the window up.
- Press the F8 key on your keyboard to open the Command Prompt window.
- Map a network drive.
- Copy the Log file from one of the applicable C: drive locations using the Log File Location by Stage table in this document.
Additional Information
SCCM OSD Task Sequence Troubleshooting Steps by Step Ultimate Guide with SMSTS.log