oeltayeb.com · Configuration Manager (SCCM) Toolkit

Checklist

Task sequence (smsts.log) troubleshooting checklist

Based on the article: Reading smsts.log: troubleshooting Configuration Manager task sequence failures · 5 min read

When a task sequence fails, the device shows an error code and a countdown, then restarts. The code alone rarely tells you much: the reason is in smsts.log, which moves as the deployment progresses. In this post I'll show where to find the log in each phase, how to keep the device on the error, and how to fix the usual failure areas: drivers, network access, content and domain join.

Symptoms to confirm

  • A Task Sequence … has failed with the error code dialog, often with 0x80004005 or 0x80070002, then a restart.
  • Failed to Run Task Sequence before any step runs, saying files for a package can't be located on a distribution point.
  • WinPE loads and restarts within seconds, or disk steps fail on new hardware.
  • Windows finishes, but the device is in a workgroup instead of the domain.

Likely causes

The task sequence engine runs steps in order.

Phasesmsts.log location
WinPE, before formatting the diskX:\Windows\Temp\SMSTSLog
WinPE, after formatting the diskX:\SMSTSLog, copied to C:\_SMSTaskSequence\Logs\Smstslog
Full OS, before the client installsC:\_SMSTaskSequence\Logs\Smstslog
Full OS, after the client installsC:\Windows\CCM\Logs\SMSTSLog
After the task sequence finishesC:\Windows\CCM\Logs
  • Drive letters can differ in WinPE, and a full log rolls over to smsts-<date>-<time>.log, so search each drive: dir /s /b C:\smsts*.log.

Checklist

  1. 1

    Keep the device on the error

    Turn on Enable command support (testing only) on the Customization tab of the boot image properties, then update its distribution points. In WinPE, press F8 for a command prompt; the device won't restart while that window is open. First checks:

    cmd
    ipconfig /all
nslookup cm01.contoso.com
diskpart
list disk
  2. 2

    Read the log from the failure upwards

    Open the log in CMTrace if your boot image includes it, otherwise Notepad. Search for Failed to run the action, which names the failed step, then read upwards to the first error:

    Failed to run the action: Apply Driver Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
The execution of the group (Drivers) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)

    CMTrace's Tools › Error Lookup gives the description.

    CodeMeaningUsual cause
    0x80070002File not foundWrong path in a command line, or content that didn't download
    0x80070005Access deniedThe account used for content or a share lacks rights
    0x80072EE7, 0x80072EFDName not resolved; can't connectDNS, network driver, firewall or certificates
    0x80091007Hash value isn't correctContent changed or corrupt on the distribution point
    0x80070070Not enough disk spaceThe content cache volume is full
  3. 3

    Drivers and storage

    If WinPE has no IP address or no disk, add the network or storage driver (newer devices often need one for Intel VMD) on the Drivers tab of the boot image properties and update its distribution points. Keep boot images lean: network and storage drivers only.

  4. 4

    Content and network access

    Failed to resolve selected task sequence dependencies with 0x80040104, logged before the first step, means referenced content has no location the device may use. The lines above it name the package ID; match it on the task sequence's References tab, check its content status and distribute it, or run Distribute Content on the task sequence itself.

  5. 5

    Domain join

    Apply Network Settings only writes the join details into the unattend file; Windows Setup joins later, so the sequence can succeed while the device stays in a workgroup. Read C:\Windows\debug\NetSetup.LOG and C:\Windows\Panther\UnattendGC\setupact.log:

    StatusMeaningFix
    0x52eWrong user name or passwordRe-enter the join account
    0x54bDomain not found or unreachableDNS, or a missing network driver in Windows
    0x5Access deniedGrant rights on the OU and existing computer objects
    0x216dMachine account quota exceededDelegate create-computer rights on the OU
  6. 6

    Capture logs automatically

    Put the main steps in a group with Continue on error. Add a second group with the condition _SMSTSLastActionSucceeded equals false: a Connect to Network Folder step mapping Z:, a Run Command Line step with the command below, and a final cmd.exe /c exit 1 so the deployment still reports failure.

    cmd
    cmd.exe /c xcopy "%_SMSTSLogPath%" "Z:\%_SMSTSMachineName%\" /E /I /Y /C

Verify

  • Rerun the sequence on a test device: the final C:\Windows\CCM\Logs\smsts.log has no Failed to run the action lines, and the device shows Success in Monitoring › Deployments.
  • For domain join, Test-ComputerSecureChannel returns True and the computer object is in the expected OU.
  • Device Manager shows no unknown devices.

Prevent it next time

  • Check references and distribute everything to distribution point groups before deploying; pilot new hardware models first.
  • Apps used in Install Application steps must allow installation from a task sequence without being deployed; their failures are in AppEnforce.log (see application deployment failures).
  • After a site upgrade or new Windows ADK, update and redistribute boot images (see upgrading current branch).

Microsoft Learn references