Microsoft published the next 1703 feature update (aka Creator Update), as Current Branch Update on 11th April 2017. Four months after the Current Branch for Business will be published (planned for August 2017) and you may need to deploy it to your Windows 10 computer to stay supported or to benefits from the new features.
Before deploying a new Windows 10 feature upgrade, you need to have a good plan. Test it in a lab environment, deploy it to a limited group and test all your business applications before broad deployment. Do not treat a feature upgrade as normal monthly software updates. Treat it as a new operating system as if you were upgrading Windows 7 to Windows 10.
SCCM Windows 10 1703 Servicing Plans Requirements
If it’s the first time you are using Windows 10 servicing plans, follow our previous post that explains the requirements to setup your Software Update Point. This post also explains the difference between Features Updates and Upgrades in update classifications. Be sure to read that to understand the difference between both.
We’ll start by making sure that the latest Feature Upgrade is synchronized on our server:
- Go to Software Library \ Windows 10 Servicing
- Right-click Windows 10 Servicing, select Synchronize Software Updates
- As for any Software Update synchronization process, follow the progress in Wsyncmgr.log in your SCCM installation directory
- Once completed, go to Software Library \ Windows 10 Servicing \ All Windows 10 Updates
- You should have your Windows 10 1703 Upgrade packages listed
Once again, if you are seeing Feature Upgrade and Upgrades read this post to understand the difference. TL;DR : Feature Upgrade = CB, Upgrades = CBB
Create Windows 10 1703 Servicing Plans
Now that we have Windows 10 1703 upgrade packages synchronized in SCCM, we can create a servicing plan for our Windows 10 devices. Servicing Plan and Automatic Deployment Rules shares the same engine so you won’t be disoriented by servicing plans.
WarningServicing plans are designed to upgrade Windows 10 from one build to another build only. You can’t use that to upgrade Windows 7 to Windows 10. If you need to upgrade your Windows 7 to Windows 10 use an Upgrade Task Sequence instead.
Looking at the Windows 10 Servicing dashboard ( Software Library \ Windows 10 Servicing), you can see your Windows 10 expiration statistics :
- Go to Software Library \ Windows 10 Servicing \ Servicing Plan
- Right-click Servicing Plan and select Create Servicing Plan
- In the General pane, give a Name and Description, click Next
- On the Servicing Plan tab, click Browse and select your Target Collection
- In the Deployment Ring tab:
- Specify the Windows readiness state to which your servicing plan should apply
- Specify how many days you want to wait before deploying
- In the Upgrade tab, specify the Language, Required and Title of the upgrade packages you want to deploy. The language feature is available in SCCM 1602+.
- Use the Preview button to ensure that you are targeting the right version (We are targeting Windows 10 1703 Enterprise en-us devices that are Required)
- In the Deployment Schedule tab, select the desired behavior
- In the User Experience tab, select the desired options
- In the Deployment Package tab, select Create a new deployment package and enter your Package Source path
- In the Distribution Points tab, select your distribution point
- In the Download Location tab, select Download software updates from the Internet
- In the Language Selection tab, select your language
- In the Summary tab, review your settings and close the Create Servicing Plan wizard
- Right-click your newly created Servicing Plan and select Run Now
- Check the RuleEngine.log file to see the progress. This process takes a while.
- A Software Update Group and Deployment Package will be created. The size of the package will be around 2-3gb per language
- You can also see that the deployment gets created in the Monitoring / Deployments section
Windows 10 1703 Servicing Plan Deployment
Now that the deployment is triggered for clients, we will launch the installation manually using software center.
- Log on your Windows 10 computer
- We verify that we are running Windows 10 Enterprise version 1607 (Build 14393.1480)
- Initiate a Software Update Deployment Evaluation Schedule using the Configuration Manager icon in Control Panel
- Open the Software Center, under Updates, Feature Update to Windows 10 Enterprise 1703 is listed
- Select it and select Install
- Accept the warning by clicking Install Operating System. (Your data won’t be lost)
- The computer will restart after about 5 minutes
- The whole upgrade process takes about 30 to 45 minutes and your device will be rebooted multiple time
- Once completed, log on the computer using your account. Windows is happy to tell you that it’s updated
- We are now running Windows 10 Enterprise version 1703(Build 15063.483)
- Back in the Software Library \ Windows 10 Servicing \ Servicing Plan node
- Our machine is now listed as Windows 10 version 1703 and is no longer listed as Expire Soon in the Windows 10 Servicing node
- The Service Plan Monitoring section can be used to monitor compliance and you can use the Deploy Now button to deploy the same service plan to a new collection
Use the comment section to tell how you’re planning to upgrade your outdated Windows 10 versions.
We upgrade windows10 OS Ent 1607 to 1703 after upgrade i am facing so many issue. Laptop get stuck & hang so many issue. is it related to that or patch issue.If you give the solution much help for me.
Hi Benoit- I followed the entire process, but when I hit manual download policy from the machine it is not showing in the software center…. any thoughts?
Wonderful step by step explanation Benoit. Thanks!!
Pingback: Service Cannot Start Error 1607 Windows
Hi, thank you for the great post. I decided to go with the servicing method to upgrade our 1607 machines to 1709. So far the upgrades takes but, there seems to be a weird error. In the Deployment Status, in the “Last Enforcement” tab says “Failed to install update(s). When I right click for more details I received “error code =0x00000000″ I’ve tried everything from checking that the new client is installed since we are now running SCCM 1710. I also ran all the actions in the client with in the machines, but no luck. It’s been about a week now since I deployed this and there seems to be no answer. I pulled the log (updateHandler) from the local machine and I see a message stating ” Failed to start WSUSupdate, Error = 0x87d00698″.
Any help would be greatly appreciated.
I’ve been trying to figure out how to use offline servicing to update my captured image from Windows 10 – 1511 to Windows 10 – 1607, but haven’t found a way to do it. Is it possible with the new branch design, or will I need to do a new build and capture for each new feature release? I upgraded to SCCM 1706 thinking that would let me do it, but still no luck.
This is good, but what about when you have an entire desktop infrastructure at multiple locations? Going to each computer one by one and installing from the software center isn’t practical. How can this be accomplished without having to do that?
I meet an problem with error as below:
Upgrade installation result indicates that commit cannot be done.
Installation job encountered some failures. Error = 0x80240022. Commit Result = 0x00000001.
Could you please help us ?
Thank you so much
Did you resolve the 0x80240022 as IM getting the same issue on 1607 to 1703 Enterprise ?
Tried reseting wsus with no success
Im assuming you can but can you use a service plan to go directly from 1511 to 1703? Or do you have to upgrade in order from 1511 to 1607 then to 1703?
You can go directly. I would suggest that you install 1709 that was out this week instead of 1703. A blog post is coming on the subject.
I have followed this and it worked perfectly, thanks. However, I have now lost all my customizations from 1607 e.g. removal of XBOX , customized start menu. I had these set up via task sequences during the initial 1607 install. Is it possible to put them on during servicing or do I have to start again and do a clean 1703 installtion with my tasks?
Have you fix this issue? I’m running into the same problem.
I do not see the feature updates in Dutch or other languages, even if I select Dutch, English and French. Only the one with English US and English GB appear in the “All Windows 10 Updates”. I checked the tree languages in sccm update point and in WSUS console as well. What could I be missing?
Benoit, do you have time to do an update on this with Semi-Annual in mind? I have SCCM 1706 and am trying to create a servicing plan for Semi-Annual Channel. When I select CBB under Deployment Ring then I get nothing in the Preview under Upgrades.
I have followed the recommended practice of creating 3 collections:
Pre-Pilot to which I will assign Semi-Annual (Targeted)
Pilot to which I will assign Semi-Annual
Production to which I will assign Semi-Annual with 120 day delay
Now I just need to figure out how to assign it properly.
Yes, a blog post will be released on the topic soon.
Nice post. All steps are well defined and it worked for me in one attempt.
I tried to upgrade the 1607 to 1703 using the service plan but it is reporting that the PC’s with 1607 is complaint. How to rectify this issue
Ali, I am having the same issue. All W10 machines are reporting compliant. How do I “force” the 1703 update on these machines?
I have a question. In my Envirement, I have a English installed 1607 Windows 10 Device with a German Language Pack. So my Windows 10 is in German with English basis OS. How I can Deploy the Windows 10 1703 Services Plan in German? in SCCM only the English Version is shown as required.
Ok, any ideas why I cannot find this update on Servicing Plan? I do exactly the same, but in preview tab I don’t see update. On “All Windows 10 Updates” I see this update.
I was having the same issue. I flipped the deployment ring to Current Branch for Business and the update became available in the Preview. I have not completely wrapped my head around this Current Branch terminology but I can now deploy 1703.
I have setup a service plan and started testing. 1607 to 1703.
Just wondering what are the logs i can read to monitor and troubleshoot on the client and server side?
Also i have notices that after the upgrade custom setting are gone. Custom task bar, branding and registry settings.
How would you go about retaining those or maybe create a TS with those custom setting and run that?
I have followed your post, But do not see anything in the software center available.
And i do not have in Software Center, Updates, Feature Update to Windows 10 Enterprise 1703.
What version of SCCM are you running?
Maybe i missed something?
Is it normal that 1703 disappeared from the current branch ring? I created a servicing plan using this blog for both the current branch and current branch for business and noticed this behavior once 1703 became available as CB • Semi-Annual Channel a few days ago.
I ran into this, as well, and I could no longer preview the feature update with the filters I had in place. I was also having trouble getting the servicing plan to filter the correct version when configuring for CBB, but that started working yesterday. Since I created that new servicing plan, I am still unable to update any 1607 systems to 1703. When my servicing plan runs, 1607 systems come back as compliant when checking the deployment status. I have an open ticket with Microsoft support, and I haven’t had a resolution since I opened the request back at the end of June. I have the necessary prerequisites in-place. Does anyone have any ideas regarding compliance inaccuracies with Windows 10?
I’m also unable to get ADRs to deliver quality updates for Windows 10, even though they seem to get added to the Software Update Groups that get created. However, our Office 365 updates, as well as Windows 7 updates, are installing via ADRs. The Office 365 updates are installing on Windows 10 systems, so they can accept these types of updates at the very least. Additionally, I can see Windows 10-related updates under All Software Updates, and I was able to successfully create a deployment package for the 1703 servicing plan. Files for the 1703 deployment package are definitely getting added to the source directory.
Any help is appreciated, as this has me stumped.
Please let me know if you have resolved this as I am having the same issue.
Thank you for the post. Servicing plans for Office 365 is the same logic? Do you guys have a guide? I wasn’t able to find one.
No Office 365 doesn’t work with the same logic. it uses the Windows Update feature.
Look at our post here. It is still accurate.
You have tagged this post as SCCM 2007 instead of 2012, otherwise good write up
Updated, thanks for your comment