ConfigMgr Windows 10 20H2 Servicing Plan | SCCM | MEMCM
In this post we deep dive into ConfigMgr Windows 10 20H2 Servicing Plan. We will first create a Windows 10 20H2 servicing plan and then deploy it to our devices running Windows 10.
There are several ways to upgrade your Windows 10 builds to 20H2 and I have published few posts as well.
With SCCM servicing plans you ensure that all the Windows 10 devices are kept up-to-date when new builds are released. Creating a Windows 10 servicing plan and deploying it is very easy.

However before you deploy a ConfigMgr Windows 10 20H2 servicing plan in production, you must test the upgrade on few machines. If you know the build is stable and wish to roll-out, servicing plan makes it very easy to accomplish the task.
Before you create a new ConfigMgr Windows 10 20H2 servicing plan, ensure you have configured Software Update Point correctly. If you don’t see Windows 10 20H2 feature updates, you need to fix that first.
In addition, ensure you have enabled Heartbeat Discovery. All the other prerequisites are covered in SCCM Windows 10 Servicing Plans post.
Table of Contents
Software Updates – Windows 10 20H2
Before you deploy the servicing plan, make sure the Windows 10 20H2 updates appear under All Windows 10 Updates. Go to Software Library > Windows 10 Servicing > All Windows Updates.
Use a simple search criteria to find the Windows 10 20H2 updates. If you find the list of Windows 10 20H2 updates, proceed to next step.
Create ConfigMgr Windows 10 20H2 Servicing Plan
To create a new ConfigMgr Windows 10 20H2 Servicing Plan.
- Launch the ConfigMgr console.
- Go to Software Library\Overview\Windows 10 Servicing\Servicing Plans.
- Right click Servicing Plans and click Create Servicing Plan.

On the General page, specify the name of servicing plan. Click Next.
You must choose the target collection and deploy the servicing plan. Choose a device collection and click Next.
Specify the deployment ring. You see two options – Semi-Annual Channel (Targeted) and Semi-Annual Channel. Read the following post to understand the difference between the deployment rings. Click Next.
On the Upgrades window, use the property filters to refine the updates. Apart from the ones selected below, you may use other property filters as well.
Click the Preview button to view the updates that will be added to the deployment. Click Close and then click Next.
Define the deployment schedule for the servicing plan and click Next.
Specify the User Experience settings and click Next.
Create Windows 10 20H2 Deployment Package
Based on the property filters and search criteria, the updates will be downloaded and added to a deployment package. Hence this step is important. Create a new deployment package. Specify Name and package source. Click Next.
Specify the ConfigMgr distribution points to distribute the content. Click Next.
Select Download software updates from the internet. Click Next.
We have created the servicing plan. Click Close.
Upgrade to Windows 10 20H2 using Servicing Plan
Finally it’s time to test our ConfigMgr Windows 10 20H2 Servicing Plan. Right click Windows 10 20H2 servicing plan and click Run Now. Open the ruleengine.log to monitor the ADR progress.
On my Windows 10 1909 machine, Windows 10 20H2 feature update appeared under Updates tab in Software Center. The update installs automatically and the machine restarts after the upgrade. The total upgrade time should be least an hour or more.
After the upgrade, you may verify the Windows 10 version either by using the WinVer command or by clicking Start > About your PC.
on CM 2010 I noticed I have updates listed under “All Windows 10 Updates” and I can filter using Title contains 20H2 and language=English however if I add the Architecture column it’s empty. Then when creating the servicing plan if I preview the upgrades I don’t get any results. I tried removing the architecture but I am still not getting any results when just using Title contains 20H2 and language=English
I had the same issue. When I changed the Deployment Ring from Semi-Annual Channel to Targeted then the Preview showed updates.
Shared updates do not show up on the client.
I use WSUS at the company
Ive notice service plans runs into issues such third-party softwares like mcafee which makes it fail, can it be removed then reapplied like in task sequence?