ConfigMgr Console

Collection of Task Sequence Tips

Topics: ConfigMgr Console

Task Sequence Tips

This is going to be a random collection of things I find interesting and want to document / share, but not really worth an entire page. This will be a pretty fluid page and continue to update as I find more things, so check back randomly.

Feel free to submit tips as well, DM me on twitter @gwblok and I’ll check out your tip.

TS Log Locations

  • WinPE: %temp%SMSTSLog (%temp% is typically X:WindowsTemp)
  • Full OS: C:_SMSTaskSequenceLogs
    • I never use this location
  • Full OS (After CM Client Installed): C:WindowsCCMLogsSMSTSLog
  • Post OSD: C:SMSTSLog
    • The Intial OSD Task Sequence logs are copied there, all future TS Logs will go to the normal C:WindowsCCMLogs location

IMPORTANT: In Windows, during an ACTIVE TS, the log will be in C:WindowsCCMLogsSMSTSlogssmsts.log, but once the TS is done, it merges into the parent folder: c:WindowsCCMLogssmsts.log

TIP: During an Active TS, you can have a step that deletes or renames c:windowsccmlogssmsts.log, so after the TS, when your current TS merges into the parent folder, it will only have information from the last TS deployment, instead of having to weed out the other ts deployments. Helpful when troubleshooting, not really a great idea to have set as default.

GPO Processing Paused during TS

Ever wonder why during OSD, Group Policy Doesn’t apply, it’s how the Task Sequence leverages SetupComplete.cmd to keep the TS alive.

Check out this page to go deeper about SetupComplete.cmd, where it explains why GPO doesn’t run while SetupComplete.cmd is active.

Check out this Recast Doc for Setup Windows and ConfigMgr step to see how it works:

NOTE: OSDSetupWindows.exe then calls OSDSetupHook.exe /Install:c:windows
This creates the folder: c:windowssetupScripts
setupcomplete.cmd (Runs at the end of Windows Setup)
Contents: “%windir%system32osdsetuphook.exe /execute

Task Sequence Tip Posts (Recast Software Blog)

Trigger Task Sequence from Command Line

Assumptions, the Task Sequence has been deployed to the machine and in Policy.

  • WMI: This leverages WMI Methods to trigger the Task Sequence. I wrote a function to do this and have it on GitHub
  • Command Line Tool: New EXE in CM 2002: TSPLaunch.exe (Limited Use available)
    • Syntax: TSPLaunch.exe /TSDeploymentID:PS100011
    • This gets used when triggering a Task Sequence during the ccmsetup.exe install using the PROVISIONTS option
    • Task Sequence (Non IPU / OSD) must be deployed to the Provisioning Collection

Task Sequence Step info in Registry (DebugMode)

Check out Key:

HKLMSoftwareMicrosoftSMSTask SequenceTSD

However, you have to have the TS Debugger enabled for that data.
TS Tips 1

TS Tips 2

Community Version on GitHub

TS Tips 3

Delete Execution History for Task Sequence

Ever want to clear out the “Failed” status in Software Center, or just reset it, so it shows as “Available”?
Delete Key:

HKLMSOFTWAREMicrosoftSMSMobile ClientSoftware DistributionExecution HistorySystem(IPU Package ID)

I have a 3 Functions on GitHub to Get, Set, Remove the Execution History.


Common issues, besides the ones listed below, there are also some listed on the related steps, in the Task Sequence Steps section.

  • Content Related
    • Boundary Groups, the machine doesn’t have a DP in the boundary group to pull content from, or a fall back wasn’t enabled for the content.
    • Content wasn’t distributed, or in the middle of distribution.
  • Typos
    • This has been the number 1 issue for me personally, bad syntax, wrong “quotes” or typos.
  • Good Practices
    • Use a Hyper-V VM to test a Task Sequence
      • Removes the variables created by hardware
      • Easy to test both Legacy BIOS and UEFI
    • Keep a Simple Default CM TS that is proven to work, and test your problematic steps there while in debug mode.
  • Issues during Setup Windows & ConfigMgr Step
    • Swap your WIM for Native MS WIM
    • Create a Default CM OSD TS and test your WIM
    • Check your settings on the following Steps
      • Apply OS Image
      • Apply Windows Settings
      • Apply Network Settings
      • Setup Windows & ConfigMgr Step
  • Issues during WinPE
    • Make sure your WinPE supports the action
      • If you’re calling a PowerShell Script, make sure you’ve enabled PowerShell… etc.
      If something in WinPE fails on Physical, test same process in HyperV VM. Rule out DriversADKs have had their share of issues lately, so check Twitter / Reddit for other with same issue, or check the ADK known issues. ADK What’s NewUnable to set Static IP. I’ve seen where if you’ve tried to set a valid address on a NIC on a machine that has several NICs, then you noticed that it was the wrong NIC, and you tried to set the IP on the right NIC, it gives you invalid IP Address. If you find you accidentally set the IP on wrong NIC, reboot, and try again, don’t try to fix it with rebooting.

About Recast Software

1 in 3 organizations using Microsoft Configuration Manager rely on Right Click Tools to surface vulnerabilities and remediate quicker than ever before.

Download Free Tools
Request Pricing

Back to Top