Microsoft published the next Windows 10 build known as Fall Creators Update earlier this week on 17th October 2017. It is what you would install if you want to be on the Semi-Annual Channel (Targeted). Come February 2018 build 1709 will transition to CBB branch meaning your workplace should adopt it to stay supported around this time. Here are some notes on what is new in this build for IT Pros.
At my workplace I utilize SCCM servicing plans underpinned by WSUS to stage CB/CBB to different groups of computers. This allows me to loosely follow the Microsoft update ring strategy. We aren’t big enough to have more than two rings but it works for us.
I simply add computers into a device collection based on OU query for Semi-Annual Channel (Targeted) and another for Semi-Annual Channel. SCCM servicing still refers to CB and CBB but if you see the table below it illustrates what Microsoft is intending. We also use LTSC (Previously LTSB) for a small subset of machines which are in unique circumstances with custom hardware. Don’t forget to import the new build and update your task sequences used for OSD as well once you’re done.
|Servicing option||Version||OS build||Availability date|
|Semi-Annual Channel (Targeted)||1709||16299.19||10/17/2017|
|Current Branch (CB)||1703||15063.674||4/11/2017|
|Current Branch (CB)||1607||14393.1794||8/2/2016|
|Current Branch (CB)||1511||10586.1176||11/12/2015|
|Current Branch for Business (CBB)||1607||14393.1794||11/29/2016|
|Current Branch for Business (CBB)||1511||10586.1176||4/8/2016|
|Long-Term Servicing Branch (LTSB)||1607||14393.1794||8/2/2016|
|Long-Term Servicing Branch (LTSB)||1507 (RTM)||10240.17643||7/29/2015|
Sync the update to your DP
- Go to Software Library \ Windows 10 Servicing
- Right-click Windows 10 Servicing, select Synchronize Software Updates
- 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 in AD
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
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
Give it a title
I just use CB
To find the correct update I used the below filter. You may need to tweak the language.
I’ve had some great advice from @placebonocebo to add required >0 in order to filter out the retail update and only pull the volume license update. My screenshot will return two update files with the same name.
You can see which is which under properties in the Content Information tab of the update. Expand the source path, here you can see the filename of the update. Retail has *clientconsumer_ret* in its name, while volume has *clientbusiness_vol*.
So, at the moment, the required criteria is the only way to filter these.
Set your preferences for the deployment schedule:
I like my testers who get this first to see plenty of information about it so i show notifications.
Create a new package
Specify your distribution point(s)
Download the updates from the internet
Set your language(s)
Review the summary
You should now have a servicing plan, well done! It will eventually run. You can right click it to run it straight away if you like. It uses the ADR (Automatic Deployment Rule) engine so works the same way.
Review your device collection deployment tab to see if it is getting the new servicing plan deployment
From the servicing dashboard you should be able to monitor progress now. A future SCCM update should allow it to identify 1709 clients. You can create a device collection for 1709 clients with a query for now.
NOTE: 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.