Task sequence error– How to copy smsts.log from client

Using SCCM to deploy operating systems to client machines is a cool feature of SCCM. If your operating system deployment fails you may need to get the smsts.log file from the client machine you are trying to image. This will help you troubleshoot why the OSD is failing. I am going to detail this process in this post.

- Error –

During operating system deployment WinPE loads up…formats the hard drive…. then goes to “Apply Operating System” after about a minute, the following error pops up “Task Sequence: Windows 7 Image has failed with the error code (0×80070002). For more information, contact your system administrator or helpdesk operator. The computer will automatically restart in 15 minutes.

- How to get the smsts.log -

  • When the Task Sequence: error code (0×80070002) pops up on the screen press the F8 key on your keyboard to pull up command line.

Run the following set of commands in the command prompt to copy the smsts.log to your SCCM Server.

  • Map a drive from your SCCM server:

net use M: \\SCCMSERVERNAME\C$

You will be prompted for your username and password. Enter them and continue.

  • Change directory to X:\windows\temp using the following syntax:

cd X:\windows\temp

NOTE: The smsts.log file is typically located in X:\windows\temp. If for some reason the log file is not on your system in the temp folder run this syntax to list where the log file is on your system.

dir /s smsts*.log

  • Run the below syntax to copy the log file to the root of your SCCM server:

copy smstslog.log M:

Now you can go to your SCCM Server and analyze the smsts.log file using CMtrace.exe.

More on smstslog.log file: http://blog.danovich.com.au/2010/03/11/sccm-task-sequence-log-file-locations/

More on SCCM Logs: http://blogs.msdn.com/b/lxchen/archive/2009/04/03/a-list-of-sccm-log-files.aspx

More on SCCM OSD troubleshooting: http://hayesjupe.wordpress.com/sccm-osd-basic-troubleshooting/

email

Written by , Posted .