Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM

Let’s learn the tricks to Optimize ConfigMgr Task Sequence OS Deployment. Microsoft introduced a new set of ConfigMgr Management Insights called Optimize for Remote Workers. The new set of management insights is only available with the SCCM production version 2006.

Management Insights

If you have not sure what is Management insights, this post shall give you a fair bit of idea about management insight. ConfigMgr Management Insights helps to gain valuable insights into the current state of the ConfigMgr environment. The Management insights are based on the analysis of data in the site database (SQL). 

  • Navigate to \Administration\Overview\Management Insights\All Insights
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM

Optimize ConfigMgr Task Sequence

It’s recommended to keep the size of the SCCM task sequence policy less than 32 MB. When the size of the ConfigMgr task sequence policy exceeds 32 MB, the failure rate of TS or OS deployment shall increase significantly.

The client fails to process large policies. The ConfigMgr client then fails to run the task sequence Operating System deployment.

Patch My PC
  • Click on the Operating System Deployment option
  • \Administration\Overview\Management Insights\All Insights\Operating System Deployment
  • Large task sequences may contribute to exceeding the maximum policy size
  • The total policy size for task sequences exceeds the policy limit
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM

Large Task Sequences may contribute to exceeding the maximum policy size

Let’s check whether your Task Sequences are very large and it could cause issues while deploying OS to Windows devices. You need to run the following Management Insight rule and confirm all your Task Sequences are in the correct state.

  • Large task sequences may contribute to exceeding the maximum policy size
  • Click on the Review Actions button (if you have any Task Sequence Listed)

If you have problematic task sequences in the ConfigMgr environment and those are deployed, those types of Task Sequences will be listed in the below list. In my SCCM lab environment, I don’t have any large Task Sequences with more than 32 MB policy size.

If you have those kinds of TSes in your environment that exceed the maximum policy size (32 MB) and cause client policy processing to fail. Reduce the size of the task sequence to prevent policy processing issues.

Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM

Total Policy Size for Task Sequences Exceeds the Policy Limit

This Management Insight rule helps SCCM admins to identify the task sequence policies that are too large to be successfully processed by clients. The action required from your side is to reduce the size of the Task Sequence to allow the deployment to run.

Adaptiva
  • Total Policy Size for Task Sequences Exceeds the Policy Limit
  • Click on the Review Actions button (if you have any Task Sequence Listed)
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM

Results

Let’s make sure to fix all the policy size-related issues with OS deployment Task Sequence and Optimize ConfigMgr Task Sequence. Once all the review actions are completed for your environment, the failure rate of OS deployment will be minimum.

  • You can see the progress status of management insights rules as COMPLETED.
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM
Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM

Resources

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…

2 thoughts on “Tricks to Optimize ConfigMgr Task Sequence OS Deployment SCCM”

  1. Hi Anoop,
    Thanks for sharing this post, we have upgraded 2006 recently and i am not seeing any difference after upgrading 2006 for OSD. Do we need to configure any rules ? because i am sure i have lot of un-used boot images. after evaluating insights its shows completed only. how to check my OSD Policy size any sql query could you give me idea..

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.