This SCCM version is not the latest version available in your SCCM console!

Make sure to upgrade your SCCM with the latest version available in your SCCM console.

Microsoft has released the final SCCM version for 2018. Microsoft still uses identical standard naming versions. You can upgrade your SCCM Current Branch environment to the latest 1810 release. If you want to install the latest updates, this post is a complete step-by-step SCCM 1810 upgrade guide.

If you’re looking for a comprehensive SCCM installation guide, see our blog series, which covers it all. You won’t be able to install 1810 if you are running SCCM 2012; the baseline version is 1802.

To install SCCM 1810 as an update, you must have installed at least SCCM 1710, SCCM 1802 or SCCM 1806.

Keeping your infrastructure up to date is essential. You will benefit from the new features and fixes, which some of them can apply to your environment. It’s easier than ever to upgrade since Microsoft has implemented the new servicing model directly from the console.

SCCM 1810 New Features and Fixes

SCCM 1810 includes many new features and enhancements in the site infrastructure, content management, client management, co-management, application management, operating system deployment, software updates, reporting, and configuration manager console.

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

Here’s our list of favourite features:

  • Support for Windows Server 2019
  • Hierarchy support for site server high availability
  • Prefer cloud distribution points over distribution points
  • Improvements to collection evaluation by entirely disabling a schedule with a query-based collection
  • Improvements to Co-Management Dashboard
  • Convert applications to MSIX from MSI
  • Repair applications directly in Software Center
  • Approve application request via email
  • Task Sequence support of Windows Autopilot for existing devices
  • Phased deployment of software updates
  • Configuration Manager administrator authentication
  • Support Center
  • SMS Provider API
  • New Permission for Client Notification actions

Support for SCCM Current Branch Versions

Ensure that you 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, ensure you run a supported Operating System and SQL version. The older SCCM version was warning during the Prerequisite check, but 1810 is giving an error preventing the installation from continuing.

1810 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 upgrading each child site. Complete the upgrade of each site before upgrading the following site. Until all sites are upgraded, your hierarchy operates in a mixed version mode.

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

This post 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 updated Configuration Manager 1810 is Available
Step-by-Step SCCM 1810 Upgrade Guide
  • If it’s not available, right-click Updates and Servicing and select Check for Updates

The SCCM 1810 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 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-clicking your Update Name and selecting Show Status.
Step-by-Step SCCM 1810 Upgrade Guide
  • The process will first download the CAB file and extract it from the EasyPayload folder in your SCCM installation directory.
  • It can take up to 15 minutes to extract all files.

SCCM 1810 Upgrade Guide

Step 1 | SCCM 1810 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 1810 update and select Run Prerequisite Check.
  • Nothing will happen; the prerequisite check runs in the background, and all menus are unavailable during the check.
  • One way to see progress is by viewing C:\ConfigMgrPrereq.log
Step-By-Step SCCM 1810 Upgrade Guide
  • 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 the Prerequisite check passed
TLS 1.2 Support

You might get a warning for TLS 1.2 support. Make sure to check ConfigMgrPrereq.log and look why the error occurs. In our situation, a higher version of SQL Server Native Client was required.

Step 2 | Launching the SCCM 1810 Update

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

  • Right-click the Configuration Manager 1810 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 can do so by using the console Administration \ Updates and Servicing \ Features.
SCCM 1710 Upgrade Guide
  • Select the desired option for your client update in the Client Update Options.
  • 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 process took a minute, but the installation began 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-clicking your Update Name and selecting 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 packages 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. If you are not running the latest version at the console opening, you will receive a warning, and the update will start automatically.

  • Since all update operations were initiated from the console, we didn’t close it during the process. We received a warning message when clicking particular objects. You will have the same message when opening a new console.
  • Click OK, and the console restart and the 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 run the latest version.



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

Beginning in 1802, this is a new version of nomenclature for the console. The console will no longer include the main build number (8740). The last 2 numbers refer to the admin console build number. For example, in the Configuration Manager version 1810, the initial site version is 5.0.8740.1000, and the initial console version is 5.1810.1075.1300. The build (1075) and revision (1300) numbers may change with future hotfixes to the 1810 release.


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

SCCM 1810 Clients

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

SCCM 1810 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 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 the checkbox is enabled
  • Review your time frame and adjust it to your needs

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 it is very useful when monitoring a 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.8740.1004'


Comments (21)


08.26.2019 AT 04:59 AM
Accidentally click Cancel during upgrade.. now console is not connecting. How do I retrigger the upgrade or fix it?


08.05.2019 AT 11:50 AM
Hi, Do you have to upgrade the SQL Server Native Client for the TLS 1.2 warning on your Primary Server or your DB Server? Thanks.

Paul Edwards

04.18.2019 AT 02:51 AM
As per Mark's comment - i have successfully upgrade from v1710 to v1810, and all is well, except that the Lifecycle 5A report is missing from SSRS. I have the dashboard in the console, and the other 4 Lifecycle reports are there, but not no 5A...


02.22.2019 AT 12:42 AM
Also the clients are configured to upgrade after 1 days after the SCCM upgrade but still seems to be in the same version . Thank you


02.22.2019 AT 12:35 AM
Hello There, Thank you for the article. Followed step n step and able to upgrade successfully. After the upgrade i have distributed both the client packages n boot images to all the DP’s. Weird thing is that i have just imaged a workstation and it got the 1606 configuration manager client installed. Any idea why this behaviour? Thabk you


02.21.2019 AT 12:44 AM
Hey - so in a particularly large environment (200+ DP's) - how can i verify that all servers are "upgraded" to 1606, then 1706, then 1806 and then finally 1810 ? I dont want to be starting the 1810 upgrade, for example if some DP's hasn't upgraded correctly to one of the earlier versions as yet.

Jesus Rojas

02.19.2019 AT 07:30 PM
hi, some one have the iso of this version, because in microsoft only have the 1802 version, but i need 1810 version to put the license key.

Harshit Gupte

03.21.2020 AT 03:43 AM
This upgrade is only available from In-Console upgrade. No separate ISO is released. follow the steps mentioned in this article.


02.06.2019 AT 12:12 PM
The update went fine but afterward I am missing report "Lifecycle 05A - Product lifecycle dashboard". Is there a way I can manually download it or does someone have a copy I can have?


09.23.2019 AT 05:38 AM
Did you get any response to this and we are having the same issue where the 05A report is missing.


02.06.2019 AT 04:27 PM
I should mention I am running sql 2012.

Pablo Varisco

01.23.2019 AT 07:41 PM
When I start the upgrade, the update of SQL DB tables stuck. Here's the solution:


01.21.2019 AT 09:09 AM
Antoher great walk through. Heads up on the client upgrade feature. If one select not to upgrade servers and you have SCOM agents on your servers, SCCM will stop the service thus generating a bunch of SCOM alerts. Teh SCCM client doesnt get installed but it does cause a scare to your operations monitoring guys. Hopefully they scan fix as i submitted a feedback for it.

James Parle

01.10.2019 AT 04:33 AM
Brilliant guide as always! I just wanted to ask, should the collection query be to check for clients with a client version less than '5.00.8740.1012' rather than '5.00.8740.1004'? Would this be sufficient? 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.8740.1012" Thanks again!

John Rehill

12.30.2018 AT 07:34 PM
I don't have the option to do the prerequisite check so I choose install since it's been a month at least since the update came out and when it went through the check a failure on the check "Potential SQL server performance issue caused by change tracking retention period" The message was a warning: Configuration Manager detects the site database has a backlog of SQL change tracking data. For more information, see I ran the query and my CT_Days_Old value came back with 68 days! I ran the command to clean up the tracking data but the value hasn't changed. Is there another way to clear this warning?

michael brown

12.19.2018 AT 09:53 AM
Hi I get this error at prereq: Configuration Manager has detected that SQL Server does not meet the minimum requirements for site upgrade. If you continue, site upgrade may fail or some features may not work correctly. Review ConfigMgrPrereq.log for more information. The onlys item in red in configmgrprereq.log is: "INFO: The rule 'SQL availability group configured for manual failover' has been run on server , skipped." and "SQL availability group configured for manual failover; Passed", any ideas?


12.13.2018 AT 01:56 AM
Thanks for the perfect article. We've got a Problem after upgrade to 1810. The component SMS_REST_PROVIDER has the State Critical. If i check the log, i don't see any Error. Do you have an idea?

Patrick Sweeney

11.28.2018 AT 01:29 PM
The client version number blog entry linked above under Consoles and again under SCCM 1810 Clients needs to be updated now. It never ends.

Nicolas Pilon

11.29.2018 AT 01:57 AM
Thanks for the flag Patrick. We changed the information on both post. Yeah... never ends 🙂

Mike Garvey

11.28.2018 AT 11:09 AM
What version of the SQL Server Native Client did you install to make the warning go away? Should I install a specific version depending on what SQL Server instance I have installed? Thanks, Mike

Nicolas Pilon

11.29.2018 AT 01:51 AM
Microsoft release a post regarding SQL Server Native Client. The post has been updated with that information.