SCCM

Location of SMSTS log during SCCM OSD

Most of us might wonder about the location of SMSTS.log during SCCM OSD. SMSTS.log is one of the important log file which will help you in troubleshooting installation issues of your Windows images.

When you notice that your task sequence fails, the first thing that you check is smsts.log file. While the TS sequence runs, you can open the smsts.log file by pressing F8 key. Type CMTrace and you can view the smsts.log file.

So the next question would be where is SMSTS.log file located ?. The smsts.log file changes it location depending on the phase of the operating system installation you are in. Below is a list of the locations depending on which you can locate the smsts.log file.

Location of SMSTS log during SCCM OSD

Here is info about location of smsts.log during SCCM OSD.

Note – To get the command prompt window you have to press F8 key during the OSD.

You can check for the below two locations for smsts.log file during OSD.

Before your hard drive is formatted and partitioned –

x:\windows\temp\smstslog\smsts.log

After HDD format –

x:\smstslog\smsts.log

and then copied to

C:\_SMSTaskSequence\Logs\Smstslog\smsts.log

You can check for the below three locations for smsts.log file after OSD and when the OS is installed.

Before SCCM agent installed –

c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

If Windows OS is 32-bit, after SCCM agent installed –

c:\windows\system32\ccm\logs\Smstslog\smsts.log

If Windows OS is 64-bit, after SCCM agent installed –

c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log

You can check for the below two locations for smsts.log file after the task sequence is complete

If Windows OS is 32-bit, after Task Sequence has finished running –

c:\windows\system32\ccm\logs\smsts.log

If Windows OS is 64-bit, after Task Sequence has finished running  –

c:\windows\sysWOW64\ccm\logs\smsts.log

Prajwal Desai

Hi, I am Prajwal Desai. For last few years I have been working on multiple technologies such as SCCM / Configuration Manager, Intune, Azure, Security etc. I created this site so that I can share valuable information with everyone.

Related Articles

12 Comments

  1. hi, i am new to SCCM tool and getting the same error, i have updated and checked/boot image/OS/TS but getting same error.I am practicing below in home lab.

    SCCM 2019- V2020
    Deploying OS Win10-Home (in Hyper-V Environment) using PXE boot.

  2. hello,

    I am experiencing “error code 0x80004005 in the task sequence step ‘Enable BitLocker'” I am using SCCM 1906, SQL 2016 and WIndows Server 2016 standard all in Virtual Environment. The virtual client i have set up is able to successfully boot into PXE SCCM environment and is also able to download windows 10 image successfully but when it restarts and attempts to run install for configuration manager client agent it generates the above mentioned error. I have tried disabling bit locker in the task sequence settings and then trying again and it works but I want to actually fix the problem. Are you able to advise what I can do

  3. Why is copy paste disabled on this website? Pretty unhelpful displaying the file paths but then having to manually type them out.

  4. Hi Prajwal, Am trying to do a windows update in sccm 2012 R2, and the results in the deployment status pane shows “Client check passed/Inactive and Client check passed/Active – in the Unknown Tab

  5. Hi Prajwal,

    I’ve been trying to find out which directory in the SCCM 2012 Server the X:Windows referring to?

    Many thanks

  6. Another useful guide as ever. Might be worth pointing out you will need to make sure the “Enable Command Support” check box on the boot images is ticked and the boot image has been re-distributed with this enabled before it will work. (This might be on as default actually, I can’t remember 100%).

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button