Hello everyone, let’s discuss How to Troubleshoot ConfigMgr Task Sequence with Debug option. Using task sequence debug, an SCCM administrator can easily troubleshoot the OSD deployment. Let’s see how the Debug Option can help you to troubleshoot the Task Sequence.
Also, by applying Task Sequence Debug, you can control and troubleshoot any task sequence deployment. This task sequence debugger you can mainly use for testing purpose. But make sure when you’re using a task sequence debug, it deployed to a smaller group of device collections.
Task sequence debugger, a new troubleshooting tool, was introduced in SCCM CB version 1906. An administrator can deploy the task sequence debug into a small collection for troubleshooting the OSD.
By deploying this task sequence, debug will allow an administrator to control each step of the task sequence to troubleshoot and investigate the issue. Task sequence debugger can be run on the same device during the task sequence deployment, not into a remote device.
let’s discuss below the pre-requisites are required to use Task sequence debugger.
- Make sure ConfigMgr clients are upgraded to the above 1906 version.
- The task sequence debugger can be run if you’re login as an administrator on a particular device.
- If you’re deploying an OSD task sequence make sure your boot image updated with the latest ConfigMgr client.
How to Use Task Sequence Debug Tool
- In the ConfigMgr Console, go to Software Library, expand the Operating Systems and select Task Sequences.
- Select the task sequence which you wanted to deploy using the ‘Debug‘ tool.
- Then ‘Right-click‘ on the task sequence and select ‘Debug‘
- Select the collection for debug deployment and click ‘Next‘.
Note!- The task sequence debug deployment option only displays 10 or fewer members of device collections.
- According to my testing you cannot use debug for required deployment. The option was gyred out.
- Click ‘Next‘ -> schedule the deployment and click ‘Next‘
- In ‘User Experience‘ section I noticed that you cannot uncheck the option for “Show Task Sequence Progress“
- Click Next -> Next to finalize the deployment.
- Once the task sequence deployment started on the machine, Task Sequence Debugger window will open.
Below controls are included in the debugger tool.
- Step: You can run the next step of the task sequence from the current position.
- Run: If you set a break in any step of the task sequence then click on run to proceed.
- Set Current: Select a task sequence step then select Set Current. This action moves the current pointer to that step. This action allows you to skip steps or move backward.
- Set Break: Select a task sequence step in the debugger and then select Set Break. This action adds a break point to the debugger. When you run the task sequence, it stops at a break.
- Clear All Break: It will remove all breakpoints.
- Log File: It will open the task sequence log file smsts.log in the CMTrace tool.
- Cmd Prompt: If you deployed a task sequence that has WinPE, then it will open a command prompt.
- Cancel: It will close the debugger and the task sequence will be failed.
- Quit: It will also close the debugger, but the task sequence will continue normally.
Debug Task Sequence Related Queries
Debug Task Sequence Option is available for all SCCM?
Yes. The minimum client version should 1906
Where is Debug Task sequence option?
Operating System – Task Sequence node
Debug Tool is an additional Tool that needs to be installed separately?
No. It’s integrated into Console by default.
- Microsoft Docs – https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/debug-task-sequence
- SCCM OSD Troubleshooting using SMSTS Log with Vishal | ConfigMgr
- SCCM OSD SMSTS Log File Reading Tips | ConfigMgr | MEMCM