Home > ConfigMgr 2007 > Where is the SMSTS.log located?

Where is the SMSTS.log located?

As we all have had to troubleshoot our task sequences before we need to refer to the smsts.log file troubleshooting. However depending on what stage of the task sequence you are at the log file will move on you.

Below are the locations the log file will be in depending on the stage you are at.

During OS Deployment


Before your hard drive is formatted and partitioned             



After your hard drive is partitioned formatted                 

X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\


Within Windows

Within Windows before the SCCM agent is installed:        



Within Windows after the SCCM agent installed:            



When the Task Sequence completes on a x86            



For x64 Systems


Categories: ConfigMgr 2007
  1. Tom
    April 11, 2011 at 1:26 pm

    Something worth noting (that I was going to ask, but then remembered) is that in order to access these logs you need to press F8 to bring up the cmd prompt.

  2. Tom
    April 13, 2011 at 12:14 pm

    Here’s another tidbit of helpfulness for those who may need to troubleshoot the smsts.log and need to copy it off that machine.

    net use \\somefolderonyournetwork
    enter your credentials
    copy smsts.log \\somefolderonyournetwork

  3. Robert
    April 4, 2016 at 1:50 pm

    And another one is that you need to enable the command prompt option on the boot image. I know you know that I just wanted to be complete for the post. Thanks for this post by the way, it’s very good!

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: