Consulting Services

Need help with your SCCM infrastructure ? Consult our fixed price consulting plans to see our rates or contact us for a custom quote.

Microsoft has released a new version of SCCM Current Branch. It’s now time to upgrade your environment! This post is a complete step-by-step SCCM 1710 upgrade guide. If you’re looking for a complete SCCM installation guide, see our blog series which covers it all. You won’t be able to install this upgrade if you are running SCCM 2012, the minimum required version is at least SCCM 1702. This version is the latest baseline version.

It’s very important to keep your infrastructure up to date. You can benefit from the new features and fixes lots of issues, which some of them are important. It’s also easier to upgrade to the new version since Microsoft has implemented the new model of update servicing.

SCCM 1710 New Features and Fixes

SCCM 1710 includes lots of new features and enhancements in the adoption of Windows 10 and Office 365 as well in modern management, mobile device management, site infrastructure, compliance settings, application management, software updates, reporting and device protection.

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

Here’s our list of favorite features:

  • Co-management for Windows 10 devices
  • Restart computers form the Configuration Manager console
  • Add child task sequences to a task sequence (Woot ! My Last year MVP hackathon project)
  • Improvements for Run Scripts

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.

SCCM 1706 Upgrade Guide

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 1710 is Available

SCCM 1710 Upgrade Guide

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

The SCCM 1710 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

SCCM 1710 Upgrade Guide

  • 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

SCCM 1710 Upgrade Guide

  • The process will first download the .CAB file and will then extract the file in the EasyPayload folder in your SCCM installation directory.
    • GUID : b56c84cf-f5a1-48d2-b89a-5bac6b2c983b
  • It can take up to 15 minutes to extract all files.

SCCM 1710 Upgrade Guide

[su_note note_color=”#eebebc” radius=”8″]You may experience problems if the downloading status remains for a long time. You can find solutions on the net like the MVP Anoop post. Even though updates are becoming easier to do, this is the most common problem. Please note that starting with SCCM 1706, a reset tool has been included to help you in these situations. MVP Kent Agerlund did a great post about the tool.[/su_note]

SCCM 1710 Upgrade Guide

Step 1 | SCCM 1710 Prerequisite Check

Before launching the update, we recommend to launch the prerequisite check first:

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

SCCM 1710 Upgrade Guide

  • 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

SCCM 1710 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

SCCM 1710 Upgrade Guide

  • When completed the State column will show Prerequisite check passed

SCCM 1710 Upgrade Guide

Step 2 | Launching the SCCM 1710 update

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

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

SCCM 1710 Upgrade Guide

  • On the General tab, click Next

SCCM 1710 Upgrade Guide

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

SCCM 1710 Upgrade Guide

  • 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 in Administration \ Updates and Servicing \ Features

SCCM 1710 Upgrade Guide

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

SCCM 1710 Upgrade Guide

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

SCCM 1710 Upgrade Guide

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

SCCM 1710 Upgrade Guide

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

  • During installation, the State column changes to Installing

SCCM 1710 Upgrade Guide

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

SCCM 1710 Upgrade Guide

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

SCCM 1710 Upgrade Guide

[su_note note_color=”#eebebc” radius=”8″]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![/su_note]

  • 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

SCCM 1710 Upgrade Guide

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

SCCM 1710 Upgrade Guide

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

SCCM 1710 Upgrade Guide

  • 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 5.0.8577.1000 and the version is now Version 1710 .

SCCM 1710 Upgrade Guide


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

SCCM 1710 Upgrade Guide


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


SCCM 1710 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 check box is enable
  • Review your time frame and adjust it to your needs

SCCM 1710 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.8577.1003' 

Happy updating!!

Comments (29)

Scott Gordon

04.02.2019 AT 08:54 AM
Hi folks, we're planning to upgrade SCCM to take advantage of all recent fixes / updates etc. My set-up is - site server running SCCM 2012 R2 CU4 (5.0.7958.1501) on Windows 2008 R2 Standard x64 SP1, 20+ branch distribution points running SCCM 2012 R2 CU4 (5.0.7958.1501) on Windows 2012 R2 Standard x64, separate database server runnign SQL Server 2008 SP2 on Windows 2008 R2 SP1. What version can I upgarde to and what upgrade path would you recommend please? As far as I can see, 1902 is the latest, and from your details, it looks like I would first go to SCCM 1710 and then up to 1902. Please confirm. Also, does the Site Server OS / SQL OS and SQL version need to be upgraded? Thanks very much for your help, Scott


03.14.2018 AT 12:19 AM
Thanks guys - awesome upgrade guide as usual. Just one small thing I've noticed is the client version is actually 5.00.8577.1005 (last digit is 5) as it is listed as 3.


03.11.2018 AT 06:32 AM
Bonjour, Je roule actuellement SCCM 2012 BUILD 1710.Main Site. Mes DP sont encore sur 2012 R2. Comment faire pour les upgrader a la version 1710. Merci David


02.13.2018 AT 09:10 AM
When updating secondary sites for CB 1710, should we us the "Recover Secondary Site" option or the "Upgrade" option?

Jonathan Lefebvre

03.14.2018 AT 09:18 AM


01.31.2018 AT 01:11 AM
Hello, I tried upgrading my 1702 environment to 1710 but the prerequisites failed. When I checked the logs, it failed due to unsupported site Operating System. This is odd because my environment is running in Windows 2012 R2. Any idea or did anyone came across this issue and find a fix?

Mohammad Faizan

03.14.2018 AT 05:16 PM
That's because you may have some Dp's running on deprecated OS. If that's the case then you may go ahead and ignore the warnings


01.08.2018 AT 03:30 PM
Thank you for this very helpful article.

Andrew Barzyk

01.04.2018 AT 09:39 AM
All of our desktops running the Admin Council fail with a log file message stating that: Cannot find MSPs Cannot find ReportViewerLP_*s CheckProductInstalled - MSI product code {669D8708-D6AF-47EF-949E-83E651CEDC7A} received unexpected return value: 1612" I'm guessing that the wrong version of Report Viewer is installed and the automated Console process runs the MSI that does not check for prereqs... Finding the install path for the exe of the console is nowhere to be found. Why does it seem like nothing Microsoft produces works right?


01.03.2018 AT 02:01 PM
Does a remote Console successfully upgrade if a domain user is opening and attempting to run the auto-update? Or will it need to be run with admin permissions? Will the 1710 Configuration Manager client update require a reboot?

Gary Knigge

12.28.2017 AT 09:37 AM
Thanks very much for this information. I come to System Center Dudes first for thorough information on upgrading our SCCM environment. If one is using MDT integration for task sequences, is it necessary to have MDT installed on the site server? Or is it sufficient to install the current ADK and MDT on management workstations that edit the Task Sequences? Thanks very much!


12.23.2017 AT 02:36 PM
updating from 1706 with all hotfixes to 1710 broke my SCCM. After the update, my IIS started throwing error 500 - Internal server error. Management point went into "critical" (saying that ISS responded with error 500). I spent an afternoon trying to debug this, but I didn't manage. Multiple logs are giving very general and unspecific error messages... Luckily, I made a snapshot before the upgrade, so I just reverted the VM to 1707. I tried this again today and ran into the same issue. Either something is wrong with 1710 or with my configuration of SCCM (which I think is pretty standard) or both. So - as always - do your snapshots before you upgrade your servers.

Wim De Block

01.26.2018 AT 07:52 AM
We have the same issue. Management Point goes offline after update from 1706. No solution found so far.


12.21.2017 AT 08:49 PM
What do we do if the update hangs? It keeps trying this: Failed to open registry key SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_EXECUTIVE\Threads\SMS_REPLICATION_CONFIGURATION_MONITOR (0), sleeping for 60 seconds... CONFIGURATION_MANAGER_UPDATE 32932 (0x80A4) It is ConfigMgr 1702 on Server 2016 with SQL Server 2016. Single server for everything

Ryan Steele

01.26.2018 AT 02:52 PM
I had the same issue, and it seemed to resolve itself after about 30 minutes. I closed and re-opened the SCCM console and allowed it to update itself around the same time as the issue was cleared, so that may have been the fix.


01.18.2018 AT 01:04 PM
Im having this issue now in My QA environment. How did you fix it?


01.25.2018 AT 07:29 PM
did you guys ever fix this? same issue.


12.20.2017 AT 10:00 AM
Hello guys Do you have any documentation on a side by side migration from start to finish for 2012R2 to Current Branch?

Jonathan Lefebvre

12.20.2017 AT 11:45 AM
Hi Anthony, here it is! It is still valid. Jonathan


12.20.2017 AT 02:42 AM
interesting on microsoft docs it says: Ensure that all sites run a version of System Center Configuration Manager that supports update to 1710: Each site server in the hierarchy must run the same version of System Center Configuration Manager before you can start the installation of update 1710. ->>>>>>>>>>To update to 1710, you must use version 1610, 1702, or 1706. care to revise the instruction?


12.15.2017 AT 06:54 AM
Have updated our SCCM on 13th Dec, can see that the client version is 5.00.8577.1005 instead of 5.00.8577.1003. No other info currently available online.


12.13.2017 AT 01:27 PM
Am I wrong in assuming you can't come from an earlier build like 1610 and upgrade straight into the 17xx branch?

Benoit Lecours

12.18.2017 AT 07:15 AM
Some updates need a certain version to be installed. For example 1710 update show only in 1610+ consoles.

Ruben O Garcia

12.13.2017 AT 08:22 AM
Hi. Just to let you know during the installation, the client version is 5.00.8577.1005 instead of 5.00.8577.1003. Best Regards


12.08.2017 AT 06:55 PM
Anyone have any ideas for a botched upgrade. This is a test environment but I upgraded from 1706 to 1710. All prereqs were successful, but the upgrade failed. Instead of Retry I decided to reboot the server (apparently not a smart idea). Now the SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER services won't start. They get a "Error 1053: The service did not respond to the restart or control request in a timely fashion". When I go to the splash.hta for 1710 it runs and when I try to do a reset the Next button is greyed out. Again, just test, but I've put in a lot of hours and don't want to lose my work.


12.06.2017 AT 08:24 AM
Great article, Benoit, keep it up!


12.05.2017 AT 11:27 AM
"The SCCM 1710 update is not yet available for everyone." --- Is enabling fast ring supported by Microsoft in a production environment? Also typically how fast does something leave the "fast ring" and show up to the general SCCM update? **Thank you for posting this I often wondered why it takes so long for updates to show up, not having any download errors. I thought once released it was widely available.


11.22.2017 AT 02:01 AM
How about Windows ADK? Should it be updated before?

Benoit Lecours

11.28.2017 AT 03:00 PM
Windows ADK should be updated if you fall out of SCCM support or if you need it for a specific Windows build (ex: Win10 1709) We wrote an article on that :