Create ConfigMgr Windows 10 2004 Servicing Plan

In this post I will show you how to create a Windows 10 2004 servicing plan in ConfigMgr. The goal is to create and deploy the SCCM servicing plan to upgrade Windows 10 to version 2004 using ConfigMgr 2002.

Using ConfigMgr servicing plan, you can ensure that all the Windows 10 systems are kept up-to-date when new builds are released.

If you know the build is stable and wish to roll-out, servicing plan makes it very easy to accomplish the task.

This is one of the method to upgrade your Windows 10 OS to the latest build in the setup.

However you can use alternate methods to deploy Windows 10 2004 using ConfigMgr such as – https://www.prajwaldesai.com/upgrade-to-windows-10-2004-using-sccm-configmgr-memcm/.

Most of all remember that you cannot use the servicing plans to upgrade Windows 7 or Windows 8.1 machines to Windows 10.

You shouldn’t be using Windows 7 anymore in the production because Windows 7 support already ended on January 14, 2020.

But the good news is you can use ConfigMgr to upgrade your Windows 7 computers to Windows 10.

Therefore the steps mentioned in this post strictly applies if you want to upgrade Windows 10 to latest builds.

In this post we will use the SCCM servicing plan feature to upgrade Windows 10 to Windows 10 version 2004.

ConfigMgr Servicing Plan Prerequisites

I have covered in-depth about the SCCM windows 10 servicing plans prerequisites in the following post – https://www.prajwaldesai.com/sccm-windows-10-servicing-plans/.

Go through the post and ensure all the prerequisite steps are done. I will be listing some of the important prerequisites here.

Configure ConfigMgr Software Update Point

Whenever you want to deploy software updates using Configuration Manager, your Software Update Point role must be configured properly.

So before you create Windows 10 servicing plan, ensure the Software Update Point role is installed and configured correctly.

First of all, if you want to deploy Windows 10 updates, the product “Windows 10” must be selected.

  • Launch Configuration Manager Console
  • Go to Administration > Site Configuration > Sites.
  • On top ribbon click Configure Site component and then click Software Update Point.
  • Click Products tab and select Windows 10, Windows 10 1903 and later.
Configure Software Update Point
Configure Software Update Point and Enable Windows 10 Product

Click Classifications tab and under Software update classifications, select Upgrades. Click OK.

Select Upgrades under Software update classifications,
Select Upgrades under Software update classifications,

Enable SCCM Heartbeat Discovery

When you install SCCM, the heartbeat discovery is enabled by default. However double-check if the Heartbeat discovery is enabled.

The data displayed in the Windows 10 servicing dashboard is found by using this discovery.

To enable Heartbeat discovery in SCCM

  • Launch the SCCM console.
  • Go Administration > Overview > Hierarchy Configuration > Discovery Methods.
  • Select Heartbeat Discovery and click Properties.
  • Under the properties window, ensure Enable Heartbeat Discovery option is enabled/checked.
Enable SCCM Heartbeat Discovery
Enable SCCM Heartbeat Discovery

Synchronize Windows 10 2004 Software Updates in SCCM

  • Go to Software Library > Overview > Windows 10 Servicing.
  • Right click All Windows 10 Updates and click Synchronize Software Updates.
  • To monitor the synchronization process, open wsyncmgr.log file.

After SUP sync, click All Windows 10 updates, ensure the results include Feature update to Windows 10 version 2004.

If you don’t find the update, you might probably want to check if there were any errors during software updates sync.

Enable Windows 10 2004 Updates in ConfigMgr
Enable Windows 10 2004 Updates in ConfigMgr

Create ConfigMgr Windows 10 2004 Servicing Plan

Use the below steps to create a Windows 10 2004 servicing plan in ConfigMgr.

  • In the SCCM console, go to Software Library > Overview > Windows 10 Servicing.
  • Right click Servicing Plans and click Create Servicing Plan for Windows 10 2004.
Create ConfigMgr Windows 10 2004 Servicing Plan
Create ConfigMgr Windows 10 2004 Servicing Plan

On the General page specify the servicing plan name such as Windows 10 2004 Servicing plan. Click Next.

Create ConfigMgr Windows 10 2004 Servicing Plan
Create ConfigMgr Windows 10 2004 Servicing Plan

On the Servicing plan page, click Browse and select the target device collection. I am going to select a Windows 10 device collection that has got 4 computers. Click Next.

Note – If you are doing this on your production setup, ensure you select a test device collection for the first time. You don’t want to apply this servicing plan to all your Windows 10 devices without proper testing.

Select the target device collection
Select the target device collection

On Specify the deployment ring page, specify the Windows readiness state to which this servicing plan should apply.

You can either choose Semi-Annual Channel (Targeted) or Semi-Annual Channel. To know the difference between them, read Windows 10 servicing deployment rings.

Click Next.

Specify the Windows 10 deployment ring
Specify the Windows 10 deployment ring

Windows 10 2004 Updates Search Criteria

Specify the search criteria and be precise because you will find lot of updates in the next step if you don’t specify a proper one.

So here is my search criteria to find or filter Windows 10 2004 updates (English).

  • Architecture – x64
  • Language – English
  • Title – 2004

Click Preview button.

Specify Property Filters and search criteria
Specify Property Filters and search criteria

Finally after you specify the criteria, the Preview Updates window shows all the relevant Windows 10 2004 updates. Click Close.

Windows 10 2004 preview updates
Windows 10 2004 preview updates

Next, specify the ConfigMgr deployment schedule for the Windows 10 2004 servicing plan.

If you are performing this step on the production server, select Specific time and apply the update with proper planning.

Click Next.

Specify Deployment Schedule
Specify Deployment Schedule

Specify the User Experience settings for this deployment and click Next.

User Experience settings
User Experience settings

Create Windows 10 2004 Deployment Package

In this step, we will create a Windows 10 2004 deployment package. Select Create a new deployment package. Specify Name and package source. Click Next.

Create Windows 10 2004 Deployment Package
Create Windows 10 2004 Deployment Package

Add the distribution points to host the content. Click Next.

Specify distribution points
Specify distribution points

Select Download software updates from the internet. Click Next.

Specify the Download location for ADR
Specify the Download location for ADR

Specify the update languages for the products. Click Next.

Specify the update languages for the products
Specify the update languages for the products

On the Summary page, verify the settings and click Next. On the Completion page, click Close.

Create ConfigMgr Servicing Plan

Deploy Windows 10 2004 using ConfigMgr Servicing Plan

The servicing plan that you just created is now displayed under Servicing plans. To deploy this servicing plan.

  • In the ConfigMgr console, go to Software Library > Overview > Windows 10 Servicing.
  • Click Servicing Plans.
  • Right click Windows 10 2004 Servicing plan and click Run Now.
  • When you click Run Now, the deployment begins to specified Windows 10 collection.
Deploy Windows 10 2004 using ConfigMgr Servicing Plan
Deploy Windows 10 2004 using ConfigMgr Servicing Plan

Click OK to run the rule. The ADR now runs based on the criteria that you have specified and on the Windows 10 device collection.

Run Windows 10 2004 servicing plan
Run Windows 10 2004 servicing plan

Monitoring the Windows 10 2004 Deployment

As I mentioned earlier, I have got 4 computers within the Windows 10 device collection. Two computers are already installed with Windows 10 2004 feature update.

Go to Monitoring > Overview > Deployments > Windows 10 2004 Servicing plan.

I can see two devices are listed under Compliant tab. These are the two computers that have the update 2004 already installed.

Monitoring Windows 10 2004 deployment
Monitoring Windows 10 2004 deployment

While under the Unknown tab, I see two devices that are still running Windows 10 version 1909. The servicing plan will apply to these two computers and install Windows 10 2004 feature update.

Monitoring Windows 10 2004 deployment
Monitoring Windows 10 2004 deployment

Logging in to one of the computers and launching software center shows that feature update to Windows 10 version 2004 is installed.

To complete the update installation you must restart the computer.

Windows 10 2004 feature update installed
Windows 10 2004 feature update installed

So click on the update and click Restart. On the Confirmation box, click Restart.

Restart computer to apply Windows 10 2004 update
Restart computer to apply Windows 10 2004 update

The Windows 10 2004 feature update installation is in progress.

Feature update installation in progress
Feature update installation in progress

Notice that all my computers now show up under Compliant tab. And yes all these computers are now running Windows 10 version 2004.

Windows 10 2004 update installed
Windows 10 2004 update installed

In conclusion, upgrading your Windows 10 to the latest version is very easy with ConfigMgr servicing plan. All you need is a proper testing and planning to roll-out the feature updates.

Related Posts
guest
3 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Paulo Sergio Pereira

Hi Prajwal,

Thanks for this post, very helpful.

I’m trying to deploy Build 2004. In some machines Windows 10 Feature Update showing as Compliant when not installed.

sccm.jpg
Ather Khan

Hello Prajwal
 
Thanks for posting this method
 
I already deployed windows 10 2004 through Servicing Plan method same process in my test collection of windows 10 but i notice one thing it will take a very long time to install update no error was found installation successfully but it will takes lot of time to to finish installation …do u have any idea whats was the reason ????? ..i monitor WUAhandler.log no error appear but it will take 2 TO 3 hours to finish installation then restart  Confirmation box notification appear ..please advise

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More