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.

A new upgrade for SCCM Current Branch is now available. This post is a complete step-by-step SCCM 1702 installation guide. If you’re looking for a complete SCCM installation guide, see our blog series which covers it all. You can’t install this upgrade if you are running SCCM 2012. You need to be at least at SCCM 1511.

Installing SCCM upgrades is very important to your infrastructure. It adds new features and fixes lots of issues, which some of them are important.

New Update and Servicing Model

If you’re not familiar with the new SCCM servicing model, read our New Update and Servicing section of the 1602 upgrade post which explain it all.

Similar to SCCM 1610, if you need to make a new SCCM installation, you can’t install SCCM 1702 directly. You need to install SCCM 1606 first and then apply SCCM 1702 from the console. SCCM 1606 is the baseline version if you’re starting from scratch.

*If you are running SCCM 1511, 1602,1606 or 1610, the latest updates will be replaced by SCCM 1702 in the SCCM Console after installation. If you are on SCCM 1511, you won’t be able to install 1602, 1606 or 1610 after 1702. You can skip all previous versions and install SCCM 1702 directly which contains all 1602, 1606 and 1610 fixes and features.

SCCM 1702 New Features and Fixes

If you’ve been installing SCCM Technical Preview in your lab, SCCM 1702 contain most features included in the latest Technical Previews. Refer to the chart in the Capabilities delivered in technical previews section.

1702 includes lots of new features and enhancements in Operating system deployment, Software Updates, application management and Mobile device deployment.

Consult the What’s new in version 1702 of System Center Configuration Manager Technet article for a full list of changes. 1702 also applies the latest KB/fixes to fix known bugs, including KB3209501, KB3214042, KB4010155

Here’s our list of favorite features:

  • Close executable files at the deadline when they would block application installation – If executable files are listed on the Install Behavior tab for a deployment type and the application is deployed to a collection as required, then a more intrusive notification experience is provided to inform the user, and the specified executable files will be closed automatically at the deadline
  • Support for Windows 10 Creators Update – This version of Configuration Manager now supports the release of upcoming Windows 10 Creators Update
  • Express files support for Windows 10 Cumulative Update – Configuration Manager now supports Windows 10 Cumulative Update using Express files
  • Customize high-risk deployment warning – You can now customize the Software Center warning when running a high-risk deployment, such as a task sequence to install a new operating system

Deprecated Features

Version 1702 drops support for the following products:

  • SQL Server 2008 R2, for site database servers. This version of SQL Server remains supported when you use a Configuration Manager version prior to version 1702.
  • Windows Server 2008 R2, for site system servers and most site system roles. This version of Windows remains supported when you use a Configuration Manager version prior to version 1702.
  • Windows Server 2008, for site system servers and most site system roles.
  • Windows XP Embedded, as a client operating system. This version of Windows remains supported when you use a Configuration Manager version prior to version 1702.

Support for SCCM Current Branch Versions

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


Before you begin

Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear in 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 top-level site upgrades, 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’ll be updating a standalone Primary Site Server, consoles and clients.

Before installing, check if your site is ready for the update:

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

SCCM 1702 Installation Guide

  • If it’s not available, right-click Updates and Servicing and select Check for Updates
  • The update state will change to Downloading
  • You can follow the download in Dmpdownloader.log or by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status

SCCM 1702 Installation Guide

SCCM 1702 Installation Guide

  • The process will first download a .CAB file and will then extract the file in the EasyPayload folder in your SCCM Installation directory. (GUID : 2dc025b9-af2f-4f22-a477-33f19c16c14c)  It can take up to 15 minutes to extract all files.

SCCM 1702 Installation Guide

SCCM 1702 Installation guide

Step 1 | SCCM 1702 Prerequisite check

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

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

SCCM 1702 Installation Guide

  • Nothing will happen, the prerequisite check runs in the background. All menu options will be grayed out during the check
  • One way to see progress is by viewing C:\ConfigMgrPrereq.log

SCCM 1702 Installation Guide

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

SCCM 1702 Installation Guide

  • When completed the State column will show Prerequisite check passed

SCCM 1702 Installation Guide

Step 2 | Launching the SCCM 1702 update

We are now ready to launch the SCCM 1702 update. At this point, plan about 45 minutes for the update installation.

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

SCCM 1702 Installation Guide

  • On the General tab, click Next

SCCM 1702 Installation Guide

  • On the Features tab, select the features you want to update

SCCM 1702 Installation Guide

  • 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 \ Cloud Services \ Updates and Servicing \ Features

SCCM 1702 Installation Guide

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

SCCM 1702 Installation Guide

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

SCCM 1702 Installation Guide

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

SCCM 1702 Installation Guide

  • On the Completion tab, close the wizard. The whole process took a minute but the installation is not over, it has been initiated

SCCM 1702 Installation Guide

  • During installation, the State column changes to Installing

SCCM 1702 Installation Guide

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

SCCM 1702 Installation Guide

  • … or you can follow detailed installation progress in SCCM Installation Directory\Logs\CMUpdate.log

SCCM 1702 Installation Guide

[su_box title=”Warning” style=”glass” title_color=”#F0F0F0″]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 could be stuck in “Prerequisite check passed” status and all other options grayed out. There’s actually no officially documented methods by Microsoft to fix that. Patience is the key ![/su_box]

  • When completed, you’ll notice the message There are no pending update package to be processed in the log file
  • Monitoring / Site Servicing Status, right-click your Update Name and select Show Status, the last step will be Installation Succeeded

SCCM 1702 Installation Guide

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

SCCM 1702 Installation Guide

Updating the 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 1702 Installation Guide

  • Click OK,  console update will start automatically

SCCM 1602 upgrade guide

SCCM 1602 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.8498.1500. You can also notice that Version 1702 is stated.

SCCM 1702 Installation Guide


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

SCCM 1702 Installation Guide


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

SCCM 1702 Installation Guide

SCCM 1702 Client Package distribution

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

  • Navigate to Software Library \ Application Management \ Packages

SCCM 1602 upgrade guide

  • Check if both packages were updated, if not, select both packages and initiate a Distribute Content to your distribution points

Boot Images

Boot images are automatically updated 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 are available checkbox has been enabled
  • Review your time frame and adjust it to your needs

SCCM 1702 Installation 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


You can also create a collection that targets clients without the latest client version. I use it to monitor which client haven’t been updated yet.

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

[pastacode lang=”sql” manual=”select%20SMS_R_SYSTEM.ResourceID%2CSMS_R_SYSTEM.ResourceType%2CSMS_R_SYSTEM.Name%2CSMS_R_SYSTEM.SMSUniqueIdentifier%2CSMS_R_SYSTEM.ResourceDomainORWorkgroup%2CSMS_R_SYSTEM.Client%20from%20SMS_R_System%20where%20SMS_R_System.ClientVersion%20!%3D%20’5.00.8498.1007′” message=”” highlight=”” provider=”manual”/]

Happy updating ! 🙂

Comments (71)


04.14.2017 AT 07:39 AM
Benoit does mention "we strongly recommend that you go through the upgrade checklist provided on TechNet" but I would just like to remind everyone that RUNNING THE DATABASE UPGRADE TEST is one of the most important things you can do besides taking a backup of the site database before you run the Install Update Pack.


04.13.2017 AT 09:35 PM
Do you need to update any additional site serves, or is this now automatic?


04.10.2017 AT 02:45 PM
Can Server 2008 R2 be used for the Site Database server, so long as SQL Server 2012 is in use ?

Jonathan Lefebvre

04.10.2017 AT 07:28 PM
Hi Mike, I'd say no. The only site system role supported on Windows Server 2008R2 are Distribution Point and StateMigration Point. Here's Microsoft statement about Windows server 2008 R2 : Beginning with version 1702, this operating system is not supported for site servers or most site system roles, however versions prior to 1702 continue to support its use. This operating system does remain supported for the state migration point and distribution point site system role (including pull-distribution points, and for PXE and multicast) until deprecation of this support is announced, or this operating system's extended support period expires. Beginning with version 1602, you can upgrade in-place the operating system of a site server from Windows Server 2008 R2 to Windows Server 2012 R2. Jonathan


04.10.2017 AT 02:20 PM
WE are running SCCM 1610 on Windows Server 2012 not R2 and after running the prereq it gives me a warning that Windows Server 2008 r2 is no longer supported. But Server is not 2008 it is 2012. Any ideas is we can go ahead with the update to 1702?

Paul Robson

04.17.2017 AT 03:40 PM
Hello --- I am having a similar issue as Jason. I am running SCCM on Windows Server 2012 R2 and with latest critical updates. I have the DB running on a separate server, also running on Windows Server 2012 R2 with latest critical updates. I am receiving these messages (Warning): [Completed with warning]:Starting with version 1702, Configuration Manager does not support Windows Server 2008 R2 operating system. This check verifies that the site server operating system meets the minimum requirement of Windows Server 2012 for site server installation. Error: [Failed]:Verifies that the site server operating system meets the minimum requirement of Windows Server 2008 SP2 for site server installation.

Jonathan Lefebvre

04.10.2017 AT 07:24 PM
Hi Jason, Is your SCCM install on one server only? including site database(SQL)? Wondering if you could have remote sites like Distribution or secondary site, still running 2008R2 Jonathan

Aidan McCarthy

04.08.2017 AT 07:35 AM
My task sequences no longer show up during OSD, any suggestions. I'm running 1702 and ADK 10.


05.06.2017 AT 05:58 AM
Hi, Did you resolve this issue? Regards, Craig

Jonathan Lefebvre

04.10.2017 AT 10:22 AM
Hi Aidan, Can you provide more details please? Where does it no longer show up? In the console? at PXE boot? in WinPE? In Software Center? What are you trying to achieve? Thanks Jonathan

Aidan McCarthy

04.11.2017 AT 03:56 AM
Hi Jonathan, I get into the OSD, I can log in but immediately after I login into the OSD the system stops and says no TS available for this computer. Since upgrading I have create new boot.wim files for both architectures and I have created new TS to see was it a corruption during upgrade but same results. The deployments to Unknown Computer groups just doesnt seem to be working. I have cleare Pxe deployements on my groups and also on the individual device im testing the Upgrade on. Any help would be great

Jonathan Lefebvre

04.11.2017 AT 08:10 AM
Hi Aidan, I would be surprised about any kind of corruption. Might be an issue with duplicate MAC address. Take a look in the SMSPXE.log located on your SCCM PXE server. D:\Program Files\Microsoft Configuration Manager\Logs\SMSPXE.log I suggest to test OSD with an available deployment, instead of mandatory(with deadline). Jonathan


06.21.2017 AT 10:59 AM


05.03.2017 AT 11:36 AM
This also seems to be effecting post first wave deployments of 1702 which already includes this hotfix.

Hoppy Shaw

05.02.2017 AT 05:43 PM
We are also experiencing issues with unknown systems not being recognized after this update. No amount of troubleshooting fixes the issue. Just called MSFT and they admit the issue as well stating there should be a fix coming soon. So I wouldn't recommend the upgrade unless you wan to import MAC address for your bare metal builds in order to make it a known system.

Aidan McCarthy

04.18.2017 AT 03:31 AM
Hi Jonathan, DO you know of any issues in 1702 at recognizing Unknown Computers, I can see the system recognizing the system as Unknown but the collections font seem to be updating with the new unknown systems hence the Task Sequences aren't being presented to those devices to OSD.

Jack Fetter

04.06.2017 AT 06:19 PM
I see there is a new ADK, do we need to install it along with SCCM 1702 for Windows 10 Creators Update support? Seems to be some info saying yes but I've seen nothing regarding installing it as part of the 1610-to-1702 upgrade? Also, I saw something about having the new ADK installed before upgrading to 1702 to get the newest boot WIM's, a tad confused... Jack

Jonathan Lefebvre

04.06.2017 AT 08:01 PM
Hi Jack, Yes there's a new ADK, for the new Windows 10. It is NOT mandatory to install it to deploy Windows 10(even creator update). SCCM Upgrade do not include ADK updates as they will not always match. As for the boot images, no need to install the ADK before upgrading. ADK can be updated at a later time, then boot images updated after this. For now I would suggest to hold the update to new ADK, as it seem to have some bugs. We are working on a post about the ADK to clarify all this. Jonathan


04.06.2017 AT 12:44 PM
Hello, We are running SCCM 1606 (no hotfix), can we install 1702 and skip 1610 ? Thanks,

Benoit Lecours

04.06.2017 AT 01:41 PM


04.07.2017 AT 10:57 AM
The 1702 update not visible in console, even after I clicked on "Check for Updates". Have you ever had to run EnableFastUpdateRing1702.ps1 to make it available ? Thanks


04.04.2017 AT 08:35 AM
We just ran the upgrade now, and it failed at 'Upgrade ConfigMgr database'. CMUpdate.log says *** [42000][50000][Microsoft][SQL Server Native Client 11.0][SQL Server]ERROR 547, Level 16, State 0, Procedure sp_SetupSettingsAndRules, Line 177, Message: The MERGE statement conflicted with the REFERENCE constraint "CI_CurrentRuleDetail_SettingID_FK". The conflict occurred in database "CM_V01", table "dbo.CI_CurrentRuleDetail", column 'SettingID'. : spRethrowError CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210) ERROR: Failed to execute SQL Server command; CCISource::InsertObject returned -1 CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210) ERROR: Failed to install default configuration items (FinalSqlOperations). CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210) Failed to update database. CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210) Failed to apply update changes 0x87d20b15 CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:59 41488 (0xA210) We are retrying the upgrade right now, hoping it was just a glitch... But if anyone has any input, it would be very much appreciated.


04.04.2017 AT 09:32 AM
No luck after trying the upgrade again. Same error.


04.07.2017 AT 03:25 AM
Follow-up: There was an error in the database, and we had to contact Microsoft to get it fixed.

Jonathan Lefebvre

04.07.2017 AT 08:16 AM
Thanks for the update Par, can you provide any more detail on what Microsoft did? Jonathan

David Beckett

04.04.2017 AT 04:55 AM
On my instance i am currently running 1610. There are two additional Hotfixes available, KB4010155 and KB4016483 BUT not 1702 update available. There dont seem to be any errors in the dmpdownloader.log or hman.log Restarted the SMS_DMP_DOWNLOADER component. Any ideas?

Benoit Lecours

04.05.2017 AT 07:30 AM
Hi David, The update is rolling out progressivelly. It's normal if you're not seeing it right away. It should appear in the following weeks. A script can be run to have it faster : (At the bottom) Note: As the update is rolled out globally in the coming weeks, it will be automatically downloaded and you will be notified when it is ready to install from the “Updates and Servicing” node in your Configuration Manager console. If you can’t wait to try these new features, this PowerShell script can be used to ensure that you are in the first wave of customers getting the update. By running this script, you will see the update available in your console right away.


06.02.2017 AT 10:41 AM
Why is there no mention of updating SQL to 2012 ? Is it required?


03.31.2017 AT 01:29 PM
As Benoit great info... Don't foget if they want to add features later. Updates and Servicing is its own node now and not under Cloud Services any more.


03.31.2017 AT 02:02 AM
Hi, can i still use 2008R2 Servers as Distribution Points or do i need to upgrade them, too?


03.31.2017 AT 01:27 PM
You can still 2008 R2 Sp1 as a DP or a State Migration Point