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.
In operating system deployment, task sequences are crucial in assembling source computers, capturing an operating system image, transferring user and computer settings, and deploying the image to a group of target computers.
If you are unsure what management is, this post will give you a fair idea about management insights. ConfigMgr Management Insights helps you gain valuable insights into the current state of the ConfigMgr environment. The Management insights are based on data analysis in the site database (SQL).
These insights empower you to understand your environment better, enabling you to make informed decisions and take proactive measures based on the information provided.
- Easy Guide To Deploy Windows 10 21H1 Using SCCM Task Sequence | ConfigMgr | Step By Step
- SCCM OSD Task Sequence Ultimate Guide 5 Understand Process
- SCCM Deployment Failed To Resolve Task Sequence Dependencies 0X80040102
Index |
---|
Management Insights |
Optimize ConfigMgr Task Sequence |
Large Task Sequences and Exceeding the Maximum Policy Size |
Total Policy Size for Task Sequences Exceeds the Policy Limit |
Results |
Management Insights
To effectively manage the Operating System deployment using System Center Configuration Manager (SCCM), gaining insights from the ConfigMgr Task Sequence is essential. This can be done by navigating to \Administration\Overview\Management Insights\All Insights.
- Navigate to \Administration\Overview\Management Insights\All Insights
Optimize ConfigMgr Task Sequence
It’s recommended that the SCCM task sequence policy be kept under 32 MB. When the ConfigMgr task sequence policy size exceeds 32 MB, the failure rate of TS or OS deployment increases significantly.
The client fails to process extensive policies. The ConfigMgr client then fails to run the task sequence for the Operating System deployment.
- 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.
Large Task Sequences and Exceeding the Maximum Policy Size
Large Task Sequences may contribute to exceeding the maximum policy size. Let’s check whether your Task Sequences are extensive, 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 below. In my SCCM lab environment, I don’t have large task sequences with a policy size of more than 32 MB.
If you have 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.
Total Policy Size for Task Sequences Exceeds the Policy Limit
This Management Insight rule helps SCCM admins identify the task sequence policies 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.
- Total Policy Size for Task Sequences Exceeds the Policy Limit
- Click on the Review Actions button (if you have any Task Sequence Listed)
Results
Let’s fix all the policy size-related issues with the 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 minimal.
- You can see the progress status of management insights rules as COMPLETED.
Resources
- Deploy Windows 10 20H2 Using SCCM Task Sequence | ConfigMgr
- ConfigMgr Management Insights – https://docs.microsoft.com/en-us/sccm/core/servers/manage/management-insights
- Configuration Manager production version 2006
We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin 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 primary focus is Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
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..
Run those rules from the management insights node. It should give you a result whether your task sequences are ok or not