Upgrade Windows 10 from 1709 to 1803 using SCCM Servicing Plans

As in the past it is now possible to deploy the feature update version 1803 using SCCM servicing plans. Check out this list of new features relevant to enterprise and business. I recommend upgrading your test group of users as soon as practical to ensure you do not get left behind by the servicing lifecycle outlined below. From my experience with this update it is pain free and worked more smoothly than 1703-1709 last year.

Before you begin there are a few Pre-Reqs to tick off:

  1. Make Sure SSCM is running the 1802 release (guides).
  2. Update the ADK for Windows 10 1802.
  3. Update your GPO template store with the updated ADMX files.
  4. Set the security baselines if you like.
  5. You may also want to import the volume license media into your SCCM server for new builds if you use PXE deployments (just for consistency).
  6. Enable Windows 10 product and Upgrade classification in your software update point.
  7. If you are on Server 2012 R2 or older for SCCM make sure you have done the prepatory upgrades to support Windows 10 feature updates also this update to fix encryption issues.

Windows 10 current versions by servicing option

Windows 10 version history Date of availability End of service
Windows 10, version 1803 April 30, 2018 November 12, 2019
Windows 10, version 1709 October 17, 2017 April 9, 20192
Windows 10, version 1703 April 5, 2017 October 9, 20182

Sync the update to your DP

  1. Go to Software Library \ Windows 10 Servicing
  2. Right-click Windows 10 Servicing, select Synchronize Software Updates1.PNG
  3. You can check the sync progress by opening cmtrace and then browsing to the log file “wsyncmgr.log” in your SCCM directory

Query to build device collection based on OU

Create a new device collection referencing an AD OU where computers can be put to target. There are lots of different ways to group a test set of machines together. Do what suits your needs. This uses a query, update the ou at the end and your domain:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemOUName = "domain.com/ou/ou”

Setting up the servicing plan to target the collection created above OU

The servicing dashboard (if prereqs are met) will show you the summary of your Windows 10 install base. It also allows you to launch the wizard to create a servicing plan. It is a cut down GUI if you run it from here. Instead you want to right click on Servicing Plans and click Create Servicing Plan:


Create the Servicing Plan

  1. Give it a title
  2. Target the collection you created based on OU or other method earlier:
  3. Choose a deployment ring. I am aggressive with my schedule because this is for my pilot users
  4. Set the three criteria per below. This will return the english version of 1803 and for volume license media built machines only (not retail)
  5. Define the schedule for deploymentschedule.PNG
  6. Define the User Experience settings for the plan. I like to give my pilot users lots of notice and flexibility
  7. Create a new deploymnt package for the update and put it in your source folder where you prefer, for me that is inside an OS folder
  8. Set where to download it from, for me I got it from the internet
  9. Set your language, for me English
  10. Review the summary and click next. You will b e finished the creation of the plan. Now we need to wait for it to say success
  11. You can now run a Software Update Scan and eval Cycle from one of the PCs in your target collection to force it to pickup the update. The update will show up in software centre.
  12. After the update is complete you should see version 1803 on the client when you run start > Winver

Monitoring the version distribution in your environment

From the servicing dashboard you should be able to monitor progress now.



I recommend changing the maximum run time for software updates to 90 minutes or maybe more if you have some slow machines. Otherwise it will rollback if it can’t finish in time. Unfortunately this is a manual process where you have to find the update and changes its max run time value.

2017-10-20 09_59_43-BNEICT02 - Remote Desktop Connection

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s