SCCM Windows 10 1709 to 1803 Upgrade Guide

Benoit LecoursSCCM19 Comments

Microsoft published the Windows 10 1803 feature update (aka April 2018 Update), in the Semi-Annual Channel on April 30th, 2018. 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.

This blog post will cover all the task needed to deploy the new Windows 10 1803 using SCCM:

  • Check if you have an SCCM Supported version
  • Upgrade your Windows ADK
  • Create a Servicing Plan to update your existing Windows 10
  • Import the OS in SCCM to use with your deployment Task Sequence
  • Create a Windows 10 Task Sequence for new computers
  • Create a Windows 10 Upgrade Task Sequence for Windows 10 (and Win 7 or 8.1 computers)
  • Update your Automatic Deployment Rules and Software Update groups
  • Import your ADMX

Check SCCM Version for SCCM Windows 10 1803 Upgrade

For Windows 10 1803 April 2018 Update, you need at least SCCM 1802 in order to support it as a client. See the following support matrix if you’re running an outdated SCCM version and make sure to update your site.

Windows ADK

Before capturing and deploying a Windows 10 1803 image, make sure that you’re running a supported version of the Windows ADK. Windows recommends using the Windows ADK that matches the version of Windows you’re deploying. If you’re already running an ADK version on your SCCM server, see our post on how to install a new version.

Upgrade Method – Task Sequence or Servicing Plan ?

In order to upgrade an existing Windows 10 (1709 and less) to Windows 1803 you have 2 choices. You can use an upgrade Task Sequence or you can use Servicing Plans. There a strong debate over which is the best methods. We prefer to use Upgrade Task Sequence for the simple reason that it’s more customizable. You can run pre-upgrade and post-upgrade task which will be mandatory if you have any sort of customization to your Windows 10 deployments.

For example, Windows 10 is resetting pretty much anything related to regional settings, keyboard, start menu and taskbar customization. Things are getting better from one version to another but if you’re upgrading from an older build, let’s say 1511, expect some post-configuration tasks… and the only way to do that is using a task sequence.

Servicing Plan has the simplicity, you set your option and forget, as for Automatic Deployment Rules does for Software Updates. We yet did not have any client that doesn’t want any control over Windows 10 upgrade in their organization. We totally understand the point of Servicing Plan and they’ll be useful in a couple of releases when Windows 10 upgrades will be an easy task… but for now, it’s not, unfortunately.

Using Upgrade Task Sequence and for new Windows 10 Computer (Operating System Deployment)

As stated in the previous paragraph, it’s possible to upgrade an existing Windows 10 computer using an upgrade task sequence. This method is useful if you need to run pre and post actions in your upgrade process.

If you need to upgrade older operating system (Windows 7,8.1) refer to the Create SCCM Task Sequence Upgrade Windows 7 to Windows 10 1803 section

You will also probably want to create or modify your existing task sequence deployed to new computers to receive the latest Windows 10 1803 version.

Import Windows 10 1803 Operating System

We will now import the Windows 10 1803 WIM file for Operating System Deployment.

We will be importing the default Install.wim from the Windows 10 media for a “vanilla” Windows 10 deployment. You could also import a WIM file that you’ve created through a build and capture process. This WIM wile will be used for new computers, to upgrade an existing Windows 10, you need to import an Operating System Upgrade Packages. We will cover this in the next section.

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Operating System Images
  • Right-click Operating System Images and select Add Operating System Image

SCCM Windows 10 1803 Upgrade

  • On the Data Source tab, browse to your WIM file. The path must be in UNC format

SCCM Windows 10 1803 Upgrade

  • In the General tab, enter the Name, Version and Comment, click Next
    • It’s normal that you see Windows 10 Education even if you are importing Enterprise edition as this WIM contains multiple indexes. You’ll need to choose the right one in your deployment Task Sequence

SCCM Windows 10 1803 Upgrade

  • On the Summary tab, review your information and click Next. Complete the wizard and close this window

Distribute your Windows 10 1803 Operating System Image

We now need to send the Operating System Image (WIM file) to our distribution points.

  • Right-click your Operating System Image, select Distribute Content and complete the Distribute Content wizard

SCCM Windows 10 1803 Upgrade

Add Operating System Upgrade Packages

We will now import the complete Windows 10 media in Operating System Upgrade Packages. This package will be used to upgrade an existing Windows 10 or a Windows 7 (or 8.1) device to Windows 10 using an Upgrade Task Sequence.

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Operating System Upgrade Packages
  • Right-click Operating System Upgrade Packages and select Add Operating System Upgrade Packages

SCCM Windows 10 1803 Upgrade

  • In the Data Source tab, browse to the path of your full Windows 10 media. The path must point to an extracted source of an ISO file. You need to point at the top folder where Setup.exe reside
  • In the General tab, enter the Name, Version, and Comment, click Next

SCCM Windows 10 1803 Upgrade

  • On the Summary tab, review your information and click Next and complete the wizard

Distribute your Operating System Upgrade Packages

We now need to send the Operating System Upgrade Package to your distribution points.

  • Right-click your Operating System Upgrade Package, select Distribute Content and complete the Distribute Content wizard

SCCM Windows 10 1803 Upgrade

Create SCCM Task Sequence Upgrade for Windows 10 1803

Let’s create an SCCM task sequence upgrade for a computer running a Windows 10 device. Once again, this Task Sequence could be used for Windows 7 or 8.1.

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click Task Sequences and select Upgrade an operating system from upgrade package

SCCM Windows 10 1803 Upgrade

  • In the Task Sequence Information tab, enter a Task Sequence Name and Description

SCCM Windows 10 1803 Upgrade

  • On the Upgrade the Windows Operating System tab, select your upgrade package by using the Browse button
  • Select your Edition Index depending on the edition you want to deploy

SCCM Windows 10 1803 Upgrade

  • On the Include Updates tab, select the desired Software Update task
    • All Software Updates will install the updates regardless of whether there is a deadline set on the deployment (on your OSD collection)
    • Mandatory Software Updates will only install updates from deployments that have a scheduled deadline (on your OSD collection)
    • Do not install any software updates will not install any software update during the Task Sequence

SCCM Windows 10 1803 Upgrade

  • On the Install Applications tab, select any application you want to add to your upgrade process

SCCM Windows 10 1803 Upgrade

  • On the Summary tab, review your choices and click Next and click Close

Edit the SCCM Windows 10 1803 Task Sequence Upgrade

Now that we have created the upgrade task sequence, let’s see what it looks like under the hood. SCCM 1802 brings new built-in checks to improve deployment success.

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click your upgrade task sequences and select Edit

As you can see, it’s fairly simple. SCCM will take care of everything in a couple of steps :

SCCM Windows 10 1803 Upgrade

  • The Upgrade Operating System step contains the important step of applying Windows 10
  • Ensure to choose the right Edition since the WIM file contains multiple indexes

SCCM Windows 10 1803 Upgrade

Deploy the SCCM Windows 10 1803 Upgrade Task Sequence

We are now ready to deploy our task sequence to the computer we want to upgrade. In our case, we are targeting a Windows 7 computer.

  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click Task Sequences and select Deploy

SCCM Windows 10 1803 Upgrade

  • On the General pane, select your collection. This is the collection that will receive the Windows 10 upgrade. For testing purposes, we recommend putting only 1 computer to start

SCCM Windows 10 1803 Upgrade

  • On the Deployment Settings tab, select the Purpose of the deployment
    • Available will prompt the user to install at the desired time
    • Required will force the deployment at the deadline (see Scheduling)
  • You cannot change the Make available to the following drop-down since upgrade packages are available to clients only

SCCM Windows 10 1803 Upgrade

  • On the Scheduling tab, enter the desired available date and time. On the screenshot, we can’t create an Assignment schedule because we select Available in the previous screen

SCCM Windows 10 1803 Upgrade

  • In the User Experience pane, select the desired options

SCCM Windows 10 1803 Upgrade

  • In the Alerts tab, check Create a deployment alert when the threshold is higher than the following check-box if you want to create an alert on the failures

SCCM Windows 10 1803 Upgrade

  • On the Distribution Point pane, select the desired Deployment options. We will leave the default options

SCCM Windows 10 1803 Upgrade

  • Review the selected options and complete the wizard

SCCM Windows 10 1803 Upgrade

Launch the Upgrade Process on a Windows 10 1709 computer

Everything is now ready to deploy to our Windows 10 computers. For our example, we will be upgrading a Windows 10 1709 to Windows 10 1803. This task sequence can also be used on a Windows 7 or 8.1 devices to install Windows 10 1803.

  • Log on our Windows 10 computer and launch a Machine Policy Retrieval & Evaluation Cycle from Control Panel / Configuration Manager Icon

SCCM Task Sequence Upgrade

  • Open the new Software Center from the Windows 10 Start Menu
  • You’ll see the SCCM upgrade task sequence as available. We could have selected the Required option in our deployment schedule, to launch automatically without user interaction at a specific time
  • When ready, click on Install

SCCM Windows 10 1803 Upgrade

  • On the Warning, click Install

SCCM Windows 10 1803 Upgrade

  • The update is starting, the task sequence Installation Progress screen shows the different steps

SCCM Windows 10 1803 Upgrade

  • The WIM is downloading on the computer and saved in C:\_SMSTaskSequence
  • You can follow task sequence progress in C:\Windows\CCM\Logs\SMSTSLog\SMSTS.log
  • After downloading, the system will reboot
  • The computer restart and is loading the files in preparation for the Windows 10 upgrade

SCCM Windows 10 1803 Upgrade

  • WinPE is loading

SCCM Task Sequence Upgrade

  • The upgrade process starts. This step should take between 60-90 minutes depending on the device hardware
  • Windows 10 is getting ready, 2-3 more minutes and the upgrade will be completed

SCCM Task Sequence Upgrade

  • Once completed the SetupComplete.cmd script runs. This step is important to set the task sequence service to the correct state

SCCM Task Sequence Upgrade

  • Windows is now ready, all software and settings are preserved

SCCM Windows 10 1803 Upgrade

Danger
If you’re happy with the results and don’t want to use servicing plans, stop reading here. If you want to know more about servicing plans, keep reading.

Use SCCM Windows 10 1803 Servicing Plans

If you’re already running Windows 10 in your organization, Servicing plans is a simple method to upgrade to an up-to-date Windows 10 version. If it’s the first time you are using Windows 10 servicing plans, follow our previous post that explains the requirements to set up your Software Update Point.

We’ll start by making sure that the latest Windows 10 1803 Feature Upgrade is synchronized on our server:

  • Go to Software Library \ Windows 10 Servicing
  • Right-click Windows 10 Servicing, select Synchronize Software Updates

SCCM Windows 10 1803 Upgrade

  • 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 1803 Upgrade packages listed

SCCM Windows 10 1803 Upgrade

Create Windows 10 1803 Servicing Plans

Now that we have Windows 10 1803 upgrade packages synchronized in SCCM, we can create a servicing plan for our “outdated” Windows 10 devices (1511,1607,1703,1709). Servicing Plan and Automatic Deployment Rules shares the same engine so you won’t be disoriented by servicing plans if you’re familiar with ADRs.

Warning
Servicing 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 :

SCCM Windows 10 1803 Upgrade

  • Go to Software Library \ Windows 10 Servicing \ Servicing Plan
  • Right-click Servicing Plan and select Create Servicing Plan

SCCM Windows 10 1803 Upgrade

  • In the General pane, give a Name and Description, click Next

SCCM Windows 10 1803 Upgrade

  • On the Servicing Plan tab, click Browse and select your Target Collection

SCCM Windows 10 1803 Upgrade

  • In the Deployment Ring tab:
    • Specify the Windows readiness state to which your servicing plan should apply. Refer to the Microsoft documentation if you are unfamiliar with servicing channels.
    • Specify how many days you want to wait before deploying

SCCM Windows 10 1803 Upgrade

  • 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 and later.
    • Language : English (will contain en-us AND en-gb)
    • Title : 1803 or 1803, en-us (if you want en-us only)

SCCM Windows 10 1803 Upgrade

  • Use the Preview button to ensure that you are targeting the right version (We are targeting Windows 10 1803 Enterprise en-us devices)

SCCM Windows 10 1803 Upgrade

  • In the Deployment Schedule tab, select the desired behavior

SCCM Windows 10 1803 Upgrade

  • In the User Experience tab, select the desired options

SCCM Windows 10 1803 Upgrade

  • In the Deployment Package tab, select Create a new deployment package and enter your Package Source path

SCCM Windows 10 1803 Upgrade

  • In the Distribution Points tab, select your distribution point

SCCM Windows 10 1803 Upgrade

  • In the Download Location tab, select Download software updates from the Internet

SCCM Windows 10 1803 Upgrade

  • In the Language Selection tab, select your language

SCCM Windows 10 1803 Upgrade

  • In the Summary tab, review your settings and close the Create Servicing Plan wizard

SCCM Windows 10 1803 Upgrade

  • Right-click your newly created Servicing Plan and select Run Now

SCCM Windows 10 1803 Upgrade

  • Check the RuleEngine.log file to see the progress. This process takes a while.

SCCM Windows 10 1709 Upgrade

  • 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
  • Ensure that your Deployment Package (specified in the Servicing Plan) has been distributed to your Distribution Points

SCCM Windows 10 1803 Upgrade

Windows 10 1803 Servicing Plan Deployment

Now that the deployment is triggered for clients, we will launch the installation manually using software center.

SCCM Windows 10 1803 Upgrade

  • Initiate a Software Update Deployment Evaluation Schedule using the Configuration Manager icon in Control Panel
  • Open the Software Center / Updates, Feature Update to Windows 10 Enterprise 1803, en-us is listed
  • Select it and select Install
  • Accept the warning by clicking Install

SCCM Windows 10 1803 Upgrade

  • The computer will restart after about 5 minutes
  • The whole upgrade process takes about 60 to 90 minutes and your device will be rebooted multiple time

SCCM Windows 10 1709 Upgrade

  • Once completed, log on the computer using your account. Windows is happy to tell you that it’s updated

SCCM Windows 10 1709 Upgrade

  • We are now running Windows 10 Enterprise version 1803 (Build 17134)

  • Back in the Software Library \ Windows 10 Servicing \ Servicing Plan node
  • Our machine is now listed as Windows 10 version 1709 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

SCCM Windows 10 1803 Upgrade

Create Software Update Group

One important thing in any OSD project is to make sure that every machines deployment are up to date. Before deploying Windows 10 1803, make sure that your Software Update Point is configured to include Windows 10 patches.

Once Windows 10 is added to your Software Update Point, we will create a Software Update Group that will be deployed to our Windows 10 deployment collection. This way, all patches released after the Windows 10 media creation (or your Capture date) will be deployed during the deployment process.

To create a Windows 10 Software Update Group :

  • Open the SCCM Console
  • Go to Software Library / Software Updates / All Software Updates
  • On the right side, click Add Criteria, select Product, Expired and Superseded
    • Product : Windows 10
    • Expired  : No
    • Superseded : No
    • Title contains 1803
  • Select only the latest Cumulative Updates that apply  (x64 or x86) and select Create Software Update Group

SCCM Windows 10 1803 Upgrade

  • Once created, go to Software Library / Software Updates / Software Update Groups
  • Right-click your Windows 10 SUG and deploy it to your OSD deployment collection

Import ADMX File

If you’re responsible for managing group policy in your organization. Ensure that you import the latest Windows 10 1803 ADMX file on your domain controller. See our SCCM Windows 10 1803 Resources for more information about this.

Bonus Ressources

Need a report to track your Windows 10 devices? We developed a report to help you achieve that :

Asset – Windows 10 SCCM Report

 

Share this Post

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 5 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.

19 Comments on “SCCM Windows 10 1709 to 1803 Upgrade Guide”

  1. Hi,
    When i try to update 1709 to 1803 I keep getting this message

    HardwareItem HardwareType=”Setup_LanguagePackDetected”>

    <Action ResolveState="NotRun" Link="wsc:setup:Setup_DismissLanguagePackBlock" DisplayStyle="Link" Name="Setup_DismissLanguagePackBlock"/

    How do I make sure that my OS and ISO source language is the same

  2. I am trying to deploy the upgrade with a TS but I get the following error:

    Set command line: “C:\_SMSTaskSequence\Packages\SCD0020F\SETUP.EXE” /ImageIndex 3 /auto Upgrade /quiet /noreboot /postoobe “C:\WINDOWS\SMSTSPostUpgrade\SetupComplete.cmd” /postrollback “C:\WINDOWS\SMSTSPostUpgrade\SetupRollback.cmd” /DynamicUpdate Disable OSDUpgradeWindows 10/15/2018 6:26:00 PM 11000 (0x2AF8)
    Executing command line: “C:\_SMSTaskSequence\Packages\SCD0020F\SETUP.EXE” /ImageIndex 3 /auto Upgrade /quiet /noreboot /postoobe “C:\WINDOWS\SMSTSPostUpgrade\SetupComplete.cmd” /postrollback “C:\WINDOWS\SMSTSPostUpgrade\SetupRollback.cmd” /DynamicUpdate Disable OSDUpgradeWindows 10/15/2018 6:26:00 PM 11000 (0x2AF8)
    Process completed with exit code 2147942487 OSDUpgradeWindows 10/15/2018 6:44:31 PM 11000 (0x2AF8)
    Windows Setup completed with exit code hexadecimal 0x80070057 (decimal 2147942487) OSDUpgradeWindows 10/15/2018 6:44:31 PM 11000 (0x2AF8)
    Saving exit code of Windows upgrade – hexadecimal 0x80070057 (decimal 2147942487) – to Task sequence environment variable ‘_SMSTSOSUpgradeActionReturnCode’, as decimal string OSDUpgradeWindows 10/15/2018 6:44:31 PM 11000 (0x2AF8)
    Windows Setup failed with hexadecimal exit code 0x80070057 (decimal 2147942487). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online. OSDUpgradeWindows 10/15/2018 6:44:31 PM 11000 (0x2AF8)
    Failing this task sequence step OSDUpgradeWindows 10/15/2018 6:44:31 PM 11000 (0x2AF8)

    Need help!

  3. Got a random one, we have 1709 deployed across the estate atm, but in my SCCM windows 10 update console, i have two versions of the feature upgrade, one called windows 10 1803 and another one exactly the same, but with x64 on the end, both say they are applicable to the same number of machines (required).

    If i deploy the standard one, some machines pick it up, but some not… so i removed that and added the x64 one, then some other machines picked it up, but again not all… so i now added both, and my machine shows both in software center, but others are just showing either one or the other… any ideas ?

  4. Regarding Feature Update to windows 10 version 1803: is it possible to deploy this as required and have it automatically upgrade any machines in the collection it is deployed to or does a user have to actually kick it off? I have a bunch of machines on older versions of Windows 10 and I need to get them upgraded to 1803 and I can’t seem to get the Feature Update to install when set to required, it just says “past due – will be installed”

  5. As someone new to SCCM I am missing where you get the ISO for the upgrade task sequence. I am in the same boat as Scott as my .wim/.iso files that I captured are not been seen by SCCM. though informative, your step by step is missing a key to understanding what needs to be done to create the upgrade package.

  6. I am updating my windows 10 1511 version to 1607 version via Upgrade ask sequence. Upgrade was not completed succesfully due to improper shutdown/reboot. but in software Center it is still showing as Installing status for long time
    I am not able reinitiate the upgrade again.

  7. During a Servicing Upgrade the SetupAct.log attempts to download ‘Dynamic Updates’.

    ‘Executing download operation: Download OS Updates (DU) to keep installation up-to-date’ (There are multiple types. IE Critical, Drivers, etc)

    How does this work? We have a SCCM CB and WSUS with Windows Updates blocked at the firewall.

  8. Im having an unusual problem where I am able to perform the in-place upgrade through software center when I am on the office network, but when I try to perform the in-place upgrade over the internet via DMZ I get the message “The software could not be found on any servers at this time”.

    Checking the execmgr.log file, I find additional errors
    Content is not available on the DP for this program, The program cannot be run now. Error code 0X87D01106. I confirmed that the content has been deployed to our DMZ distribution point. I can install other applications to the computer through software center.

  9. Hi

    We’re trying to upgrade our workstations with an In-place on-demand type of upgrade, to let the user chose when he wants to upgrade to Windows 10 from Software Center. We’re planning on upgrading Windows 7 x64 SP1 to Windows 10 1803 x64.

    Currently we’re on SCCM 1710. Could be the SCCM outdated version that is causing the in-place upgrade to fail? I’ve tested and modified the TS extensively but to avail.

    Thanks.

  10. I try to deploy using TS.
    When everything is done the mascine reboots, and the boóts to X:\Windows\system32

    The first line in the CMD-Windows tell me:
    There is a winpeshl.ini-file, but no commands are activated.

    If I write exit and type enter the machine reboots and rolls back windows.

    Do you know about that?

  11. Hello webmaster, i’ve been reading your articles for some time and I really like coming back here.

    I can see that you probably don’t make money on your blog.
    I know one cool method of earning money, I think you will like it.

    Search google for: dracko’s tricks

  12. I am finding that using the task sequence to upgrade on a few test machines , that it is wiping out user settings and things like bookmarks, FTP settings, etc. I did not see a setting in the “Upgrading OS” that provides a way of setting the upgrade to “Keep user files and setting” , as you do when you do a hand upgrade process. This is very disconcerting as this will impact over 5000 users in my Enterprise.

    I have not tried to test the servicing yet and am in the process of doing that now.

    Any Advice?

  13. Just a clarification:
    Now that we have created the upgrade task sequence, let’s see what it looks like under the hood. SCCM 1802 brings new built-in checks to improve deployment success.
    •Open the SCCM Console
    •Go to Software Library \ Operating Systems \ Task Sequences
    •Right-click your upgrade task sequences and select Edit

    As you can see, it’s fairly simple. SCCM will take care of everything in a couple of steps :

    I was almost sure that the “steps” builted-in are only FOLDERS, but that they’re doing nothing.
    You will have to put something under it.
    It’s more a guideline of what you can implement as check before upgrading… or am I mistaken, and really SCCM does with a “folder”, a check of the battery, network, not compatible sw,…. ?

    Cheers

  14. When it comes to Windows 10 Servicing I am unable to find the feature update package even after running a sync. I am, as of recently, running SCCM 2012 v 1802. All I can see are consumer and business editions, but I need to enterprise edition of 1803.

  15. What about windows as a service? I haven’t had very much success with it. I’ve received false positives after it was installed. Meaning that it installs but the software center shows failed due to the logs showing it was waiting for a reboot that already happened.

    1. I had the same experience using the builtin WAAS process with system center (The error disapeared after the patch detection cycled). I find the task sequence still gives us more control and visibility on the upgrades. I also tried upgrading some machines using the windows update for business process and it worked without giving any errors…

Leave a Reply

Your email address will not be published. Required fields are marked *