Step-by-Step SCCM 1802 Upgrade Guide

Benoit LecoursSCCM25 Comments

Consulting Services
Need help to upgrade or migrate your site ? Consult our fixed price consulting plans to see our rates !

Microsoft has released a new version of SCCM Current Branch. It’s now time to stay current and upgrade your environment! This post is a complete step-by-step SCCM 1802 upgrade guide. If you’re looking for a comprehensive SCCM installation guide, see our blog series which covers it all. You will be able to install 1802 if you are running SCCM 2012, this new version is a new baseline version.

To install SCCM 1802 as an update, you must have SCCM 1702 installed.

Keeping your infrastructure up to date is essential. You can benefit from the new features and fixes issues, which some of them can be related to your SCCM. It’s also easier to upgrade to the latest version since Microsoft has implemented the new model of update servicing which is the in-console upgrade.

SCCM 1802 New Features and Fixes

SCCM 1802 includes lots of new features and enhancements in the site infrastructure, management insights, client management, co-management, compliance settings, application management, operating system deployment, software center, software updates, reporting, protect devices, configuration manager console.

You can consult the What’s new in version 1802 of System Center Configuration Manager Technet article for a full list of changes.

Here’s our list of favorite features:

Support for SCCM Current Branch Versions

Ensure to apply this update before you fall into an unsupported SCCM version. Read about the support end date of the prior version of the following Technet article.

Windows and SQL Support

Before installing, make sure that you are running a supported Operating System and SQL version. Older SCCM version was giving a warning during Prerequisite check but 1802 is giving an error which prevents the installation from continuing.

1802 supports only Windows 2012+ and SQL 2012 SP3+.

Before you Begin

Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear on your console once the Service Connection Point is synchronized.

If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. After the CAS upgrade, you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site. Until all sites in your hierarchy are upgraded, your hierarchy operates in a mixed version mode.

Before applying this update, we strongly recommend that you go through the upgrade checklist provided on Technet. Most importantly, initiate a site backup before your upgrade.

In this post, we will update a stand-alone primary site server, consoles, and clients. Before installing, check if your site is ready for the update:

  • Open the SCCM console
  • Go to Administration \ Updates and Servicing
  • In the State column, ensure that the update Configuration Manager 1802 is Available

  • If it’s not available, right-click Updates and Servicing and select Check for Updates

The SCCM 1802 update is not yet available for everyone. If you need it right away you can run the Fast-Ring script and the update will show up.

  • If the update is not downloading, click on the button Download on the upper node. The update state will change to Downloading
  • You can follow the download in Dmpdownloader.log or by going to Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status

  • The process will first download the .CAB file and will then extract the file in the EasyPayload folder in your SCCM installation directory.
    • GUID : c78e7992-75db-4cd2-b89e-8024fc99884b
  • It can take up to 15 minutes to extract all files.

SCCM 1802 Upgrade Guide

Step 1 | SCCM 1802 Prerequisite Check

Before launching the update, we recommend launching the prerequisite check first. To see the prerequisite checklist, see the Microsoft Documentation

  • Open the SCCM console
  • Go to Administration \ Updates and Servicing
  • Right-click the Configuration Manager 1802 update and select Run prerequisite check

  • Nothing will happen, the prerequisite check runs in the background and all menu are unavailable during the check
  • One way to see progress is by viewing C:\ConfigMgrPrereq.log

  • You can also monitor prerequisite check by going to Monitoring / Update and Servicing Status, right-click your Update Name and select Show Status

  • When completed the State column will show Prerequisite check passed

Step 2 | Launching the SCCM 1802 update

We are now ready to launch the SCCM 1802 update. At this point, plan about 45 minutes to install the update.

  • Right-click the Configuration Manager 1802 update and select Install Update Pack

  • On the General tab, click Next

  • On the Features tab, checkboxes on the features you want to enable during the update

  • Don’t worry, if you don’t select one of the features now and want to enable it later, you’ll be able to so by using the console Administration \ Updates and Servicing \ Features

SCCM 1710 Upgrade Guide

  • In the Client Update Options, select the desired option for your client update

  • On the License Terms tab, accept the license terms and click Next

  • On the Summary tab, review your choices, click Next and close the wizard on the Completion tab

The whole process took a minute but the installation begins on the back end.

  • During installation, the State column changes to Installing

  • We suggest you monitor the progress, by navigating to Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status

Unfortunately, the status is not updated in real time. Use the Refresh button to update.

  • Open the SCCM log SCCM Installation Directory\Logs\CMUpdate.log with CMTrace

Important Info
We’ve done numerous SCCM upgrades. Some installation start a couple of minutes after you complete the wizard but we’ve seen some installation starts after a 10 minutes delay. Do not reboot or restart any services during this period or your update can be stuck in “Prerequisite check passed” status. There’s actually no officially documented methods by Microsoft to fix that. Patience is the key!
  • When completed, you’ll notice the message There are no pending update package to be processed in the log file
  • Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status, the last step will be Installation Succeeded

  • Refresh the Updates and Servicing node in Administration, the State column will be Installed

Updating the Outdated Consoles

As a previous Cumulative update, the console has an auto-update feature. At console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.

  • Since all updates operations were initiated from the console, we didn’t close it during the process. We received a warning message when clicking certain objects. You will have the same message when opening a new console

  • Click OK,  console update will start automatically

SCCM 1710 Upgrade Guide

SCCM 1710 Upgrade Guide

  • Wait for the process to complete. You can follow the progress in C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open and you’ll be running the latest version



After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be X and the version is now Version 1802.

Beginning with 1802, this is a new version nomenclature for the console. The console will no longer include the main build number (8634). The last 2 numbers refer to the admin console build number. For example, in Configuration Manager version 1802 the initial site version is 5.0.8634.1000, and the initial console version is 5.1802.1082.1700. The build (1082) and revision (1700) numbers may change with future hotfixes to the 1802 release.


  • Go to Administration \ Site Configuration \ Sites
  • Right-click your site and select Properties
  • Verify the Version and Build number

SCCM 1802 Upgrade Guide


The client version will be updated to 5.00.8634.1007 (after updating, see section below)

SCCM 1802 Client Package distribution

You’ll see that the 2 client packages are updated:

  • Navigate to Software Library \ Application Management \ Packages

SCCM 1710 Upgrade Guide

  • Check if the update is successful, otherwise, select both packages and initiate a Distribute Content to your distribution points

Boot Images

Boot images will automatically update during setup. See our post on upgrade consideration in a large environment to avoid this if you have multiple distribution points.

  • Go to Software Library / Operating Systems / Boot Images
  • Select your boot image and check the last Content Status date. It should match your setup date

Updating the Clients

Our preferred way to update our clients is by using the Client Upgrade feature: (You can refer to our complete post documenting this feature)

  • Open the SCCM Console
  • Go to Administration / Site Configuration / Sites
  • Click the Hierarchy Settings in the top ribbon
  • Select Client Upgrade tab
  • The Upgrade client automatically when the new client update is available to check box is enabled
  • Review your time frame and adjust it to your needs

SCCM 1802 Upgrade Guide

Monitor SCCM Client Version Number

SCCM Reports Client Version

You can see our SCCM Client version reports to give detailed information about every client version in your environment. It’s the easiest way to track your client updates.

SCCM 2012 - System Health Configuration Manager SS


In conclusion, you can create a collection that targets clients without the latest client version because is very useful when it comes to monitoring non-compliant client.

Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contains this collection)

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.ClientVersion != '5.00.8634.1007'

Share this Post

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 4 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.

25 Comments on “Step-by-Step SCCM 1802 Upgrade Guide”

  1. We are currently running 2012 R2 SP1 – 5.0.8239.1000

    Can we upgrade straight to version 1802, if so, how as we do not have the option to run the upgrade within the console and can’t seem to find any advice on the best way (we already have sql server 2012 and updated to Windows 10 ADK).


    1. Did you have any luck with this? | I’m in the same boat as you.
      Updates and Servicing is missing from Administration
      System Center 2012 Configuration Manager SP2 | console version 5.0.8239.1000

      I have downloaded the 1802 current branch media ISO but am unsure if I should try and proceed..
      Independently ran “prereqchk.exe /LOCAL” but it fails detecting previous installation; which is true.
      I’m in a test environment so I can always restore.

      Is your SQL 2012; SP3 or SP4?

      1. No I have just got back from annual leave.
        I assume it is a simple as running the setup from the 1802 ISO, but I can’t seem to find anyone who has done it this way.
        It seems like it could be very destructive if this is not the correct method.

        We are running SQL 2012 SP3, which is the minimum required for the update.

        I found that problem with the checks, but running the prereqchk.exe straight from the folder but as an admin seemed to work fine.

  2. great article, but no one tells whether ADK and MDT needs to be updated or not and what versions they should be before upgrading to 1802
    also the boot image update process

  3. We will also need to Upgrade Secondary Servers once CAS and Primary are updated, in guide its not mentioned. was that missed on purposely ? just curios to know.

  4. Hallo, we have an issue happened after upgrade to SCCM 1802:

    Site Component Manager failed to reinstall this component on this site system.

    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.

  5. Hi,

    We have a simple single site, single server setup which is currently on 1606 and needs to get to 1802. I understand that server-side we will need to run 2 phases: 1606 –> 1706 and then 1706 –> 1802. For the clients though, can we skip rolling out 1706 to the clients and just upgrade them from 1606 to 1802 directly by rolling out the client update package of 1802 once the server is up to that version? (I get that idea from MS: –> Tip: If you are upgrading your server infrastructure from a previous version of Configuration Manager (such as Configuration Manager 2007 or System Center 2012 Configuration Manager), we recommend that you complete the server upgrades including installing all current branch updates, before upgrading the Configuration Manager clients. The latest current branch update contains the latest version of the client, so it’s best to do client upgrades after you have installed all of the Configuration Manager updates you want to use.)


    1. Hi Jon,

      Sure, you can just push the latest 1802 client, you can skip 1706 client without problem.

  6. Hi, thanks for the detailed guide. I’m new to System Center and upgraded to 1802 from 1702. When I check Software Library -> Application Management -> Packages there is no version no. for Config Mgr Client Package. Delete and deploy options are greyed out and properties are greyed out. Is this normal? I just want to check the upgrade has been successful.

  7. after the upgrade I’m getting this error and I can’t use PXE anymore….

    Your Pc/Device need to be repaired
    The windows Boot Configuration Data (BCD) file from PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture.
    code 0xc0000098

    1. Have you distribute both Boot Image (x64,x86) to your distribution point that host the PXE service?

      1. Hi,
        Before the Upgrade there were Boot Images working. Have I to redistribute that images again?

        Or Have I to create new boot images and distribute?

  8. Hi’ great article, helped me in the upgrade to 1802
    Q: is the Configuration Manager Remote Control tool, suppose to be upgrade also with 1802 ???
    cause it seems it didnt

Leave a Reply

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