Step-by-Step SCCM 1706 Upgrade Guide

Nicolas PilonSCCM34 Comments

Need help to upgrade 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 upgrade your environment! This post is a complete step-by-step SCCM 1706 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 1706 New Features and Fixes

1706 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 1706 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 in 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 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 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 1706 is Available

SCCM 1706 Upgrade Guide

  • If it’s not available, right-click Updates and Servicing and select Check for Updates
If the new version is still not available, you can run this script from Technet Gallery to Enable Early Update Ring. Take note that it’s optional, otherwise you will need to wait till it’s available on your console.
  • 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 / Site Servicing Status, right-click your Update Name and select Show Status

SCCM 1706 Upgrade Guide

SCCM 1706 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 : b7700d5c-d16f-40da-bb0d-a8c5a90822b9
  • It can take up to 15 minutes to extract all files.

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 Agerland did a great post about the tool.

SCCM 1706 Upgrade Guide

Step 1 | SCCM 1706 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 1706 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

SCCM 1706 Upgrade Guide

  • When completed the State column will show Prerequisite check passed

Step 2 | Launching the SCCM 1706 update

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

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

SCCM 1706 Upgrade Guide

  • On the General tab, click Next

SCCM 1706 Upgrade Guide

  • On the Features tab, check boxes 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 in Administration \ Updates and Servicing \ Features

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

SCCM 1706 Upgrade Guide

  • 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 in 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

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

Verification

Consoles

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

Servers

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

Clients

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

 

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

Collections

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.8540.1003'

Happy updating!!

Founder of System Center Dudes. Nick has been awarded in 2016 as a Microsoft MVP in Enterprise Mobility category.
Working as a senior SCCM and Intune advisor as well as a specialist Microsoft Cloud solutions specialist.
Step-by-Step SCCM 1706 Upgrade Guide
5 - 4 votes

34 Comments on “Step-by-Step SCCM 1706 Upgrade Guide”

  1. We just upgraded to 1706 on a newly installed 1702.
    After upgrade we could not install any clients due to version mismatch.
    – From cmsetup.log “Client version ‘5.00.8498.1008’ is older than site version ‘5.00.8540.1005’. May skip this location.”
    When I check in the console Production Client and Pilot Client version is still ‘5.00.8498.1008’ although the binaries seem to be ‘5.00.8540.1005’.

    I tried running CMUpdatereset but was notified that update already was in post install state,

    How do I solve this mismatch without reinstalling the site?

  2. Help Required!!!

    After the upgrade from CM 1702 to 1706, OSD has stopped working. I m trying to deploy Windows 10 _1606 version.

    <![LOG[ Setting policy location = http:///SMS_MP/.sms_pol?SP120008-SP100067-6F6BCC28.2_00.%5DLOG%5D!&gt;

    <![LOG[Request location: http:///SMS_MP/.SMS_POL?SP120008-SP100067-6F6BCC28.2_00%5DLOG%5D!&gt;

    <![LOG[ Setting policy location = http:///SMS_MP/.sms_pol?DEP-SP120008-SP100003-6F6BCC28.1_00.%5DLOG%5D!&gt;

    <![LOG[Request location: http:///SMS_MP/.SMS_POL?DEP-SP120008-SP100003-6F6BCC28.1_00%5DLOG%5D!&gt;

    <![LOG[ Setting policy location = http:///SMS_MP/.sms_pol?{1e634014-b07b-47e7-8a5b-adcbee71c04e}.2_00.]LOG]!>

    <time="14:35:21.026-120"

  3. Does any one facing problem with SCCM Replication for the global Replication Group CMScripts in Primary Site servers?

    In our enviornmnet, we have two Primary Sites reporting a CAS. In both Primary sites, replication fails for Global Replication Group CMScripts.

    any idea to fix this problem will be helpful.

    Thanks,
    Mahantesh

  4. Hi People,

    So i just updated to SCCM 1706 on Windows Server 2012R2. When deploying a new machine Windows 10 1607 the task sequence is failing when the SCCM Clients starts installing.

    smsts.log

    Executing command line: “C:\_SMSTaskSequence\OSD\P0100003\ccmsetup.exe” /useronly /source:C:\_SMSTaskSequence\OSD\P0100003 /config:MobileClient.TCF /status:772 OSDSetupHook 4-10-2017 14:00:40 3868 (0x0F1C)
    Process completed with exit code 7 OSDSetupHook 4-10-2017 14:02:03 3868 (0x0F1C)
    FALSE, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdgina\installclient.cpp,1151) OSDSetupHook 4-10-2017 14:02:03 3868 (0x0F1C)
    Client installation failed, code 7 OSDSetupHook 4-10-2017 14:02:03 3868 (0x0F1C)

    Checking the ccmsetup.log shows :
    MSI: Actie 14:01:29: SmsGenerateFailureMIF. ccmsetup 4-10-2017 14:01:29 4088 (0x0FF8)
    MSI: Actie 14:01:29: SmsGenerateSuccessMIF. ccmsetup 4-10-2017 14:01:29 4088 (0x0FF8)
    MSI: Actie 14:01:29: CcmStopServiceRollback. Hiermee wordt de service CcmStartService aangeroepen, waarmee de service ccmexec wordt gestart. ccmsetup 4-10-2017 14:01:29 4088 (0x0FF8)
    MSI: Actie 14:01:29: ProcessComponents. Bezig met het bijwerken van de registratie van de onderdelen ccmsetup 4-10-2017 14:01:29 4088 (0x0FF8)
    MSI: Actie 14:01:29: CcmStopService. Hiermee wordt de service ccmexec gestopt. ccmsetup 4-10-2017 14:01:29 4088 (0x0FF8)
    MSI: Actie 14:01:29: StopServices. Bezig met het beëindigen van services ccmsetup 4-10-2017 14:01:29 4088 (0x0FF8)
    MSI: Actie 14:01:29: SmsUninstallPrepDrvr. Uninstalling Software Metering PREP Driver ccmsetup 4-10-2017 14:01:29 4088 (0x0FF8)
    MSI: Waarschuwing 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 4-10-2017 14:01:29 4088 (0x0FF8)
    Also the last part of client.msi.log : https://hastebin.com/ereyelimug.vbs

    Found online that adding /forcereboot should help. But that didn’t do the trick.

    Any advice ?

    Thanks,

    Michael

  5. Hi,

    I’ve a question about the following sentence:

    “The minimum required version is at least SCCM 1702”.

    But, according Microsoft Docs, the minimum SCCM version can be 1606.
    So it’s a little bit confusing for me.

    I hope you guys can help me.

    1. Hi Nick,
      you are right, it’s a bit confusing.

      If you are running SCCM 2012, you can’t go straight to SCCM 1706 as this is not a baseline release. The baseline for an upgrade from SCCM 2012, is 1702.

      If you are already running a version of current branch, the minimum required is 1606.

      Hope it’s more clear that way.

      thanks
      Jonathan

  6. 1706 update completed successfully for us- status shows everything comPleted. On completion of that, Hotfix KB4042345 showed up. I saw that installations downloaded after 9/13 include this fix. We downloaded on 9/6 so our installation did not include the fix. We ran KB4042345 and the status shows installation completed successfully. Post installation has been “In progress” for 5 hours though. The first 5 entries have a status of “not started”. The last 3 have a status of completed. Any advice?

    Not started: Installing SMS_EXECUTIVE service, Installing SMS_DATABASE_NOTIFICATION_MONITOR component, Installing SMS_HIERARCHY_MANAGER component, installing SMS_REPLICATION_CONFIGURATION_MONITOR component, Monitoring replication initialization.

    Completed: Updating Configuration Manager Client Preproduction Package, Updating Client folder on Site Server, Updating Configuration Manager Client Package

    1. Everything completed after a restart… I didn’t originally want to restart if it was in the middle of something, but everything did resolve after a restart.

  7. I did my update over the weekend to Production without issue but it looks like the build numbers are different from when you all performed yours for this article.

    Console Version: 5.00.8540.1600
    Client Version: 5.00.8540.1007

    Site version is the same at 5.00.8540.1000

  8. Got the same Problem:
    Deleted both; folder and cab file (0f11caa4-7f7f-454b-96d6-75f427d015ce) in EasySetupPayload and the 0f11caa4-7f7f-454b-96d6-75f427d015ce-Folder inCMUstaging

    Result: SCCM launch a new Download which stucks again. dmpdownloader.log Message:

    Error in verifying the trust of file ‘e:\SystemCenter_Prg\SCCM\EasySetupPayload\0f11caa4-7f7f-454b-96d6-75f427d015ce.cab’. SMS_DMP_DOWNLOADER 08.09.2017 10:43:16 9432 (0x24D8)

    WARNING: Failed to call IsFileTrusted SMS_DMP_DOWNLOADER 08.09.2017 10:43:16 9432 (0x24D8)

    I tried lots of possibilities -but no solution. After hours i gave up. Wait for the 1706 CM iso in VSLC.

  9. i am trying to download 1706, but stuck in downloading.
    I am seeing “Failed to extract the payload cab of package from Easysetuppayload” folder in dmpdownloader.log file.

    any solutions to fix this problem?

  10. Hello Jonathan
    Got the same problem as elsewhere – CM 1706 stuck since 6.9. 17 at download. None of the solution in the net gave it push. I downloaded the cmupdatereset tool – neither. What to do with this update now – wait til dawn?

  11. Failed installation. My upgrade is failing on a few files in C:\Program Files\Microsoft Configuration Manager\CMUStaging\0F11CAA4-7F7F-454B-96D6-75F427D015CE\SMSSETUP\CLIENT\X64 files with 0kb size. I assume the CAB was corrupt in someway. Is there a way to force a redownload of the CAB file. I have tried deleting the files from CMUStaging and Easy setup payload. No change. CAN get re extracted with the same 0kb files.

  12. Hi.

    Just to add that I was able to solve the problem! Our maintenance window was defined to happen on Sundays… therefore the error message “It is not in any service windows defined for the site server. Will check later.”.
    Once I changed the maintenance window, the process re-started immediately.

    Hope this helps someone.

    Cheers

  13. Hi Dudes.

    I started the upgrade yesterday at 8:00 am and the installation is stuck in “Check Service Window”… although the step is marked as complete I can see in the logs this messages:
    “Successfully reported ConfigMgr update status (SiteCode=PT1, SubStageID=0xd0008, IsComplete=1, Progress=1, Applicable=1)
    It is not in any service windows defined for the site server. Will check later.”

    In the hman.log I have this:

    CheckSQLServiceRestart : SQL Service hasn’t been restart since last time we check, skip it. $$
    ~Wait for site control changes for maximum 3600 seconds… $$
    Wait for client upgrade notification timed out. $$
    Loaded client upgrade settings from DB successfully. FullClientPackageID=PT100003, StagingClientPackageID=PT100060, ClientUpgradePackageID=PT100004, PilotingUpgradePackageID=PT100061, ClientUpgradeAdvertisementID=PT120000, ClientPilotingAdvertisementID=PT120051 $$
    Highest patch version is ‘5.00.8498.1711’. $$
    Highest patch version is ‘5.00.8498.1711’. $$
    Highest patch version is ‘5.00.8498.1711’. $$
    Highest patch version is ‘5.00.8498.1711’. $$
    INFO: Client baselines are up to date. $$
    Update client deployment compliance state per baseline definition. $$
    Waiting for Configuration Manager Client Upgrade changes for maximum 10764 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Wait for message forwarding notification timed out. $$
    Waiting for ISM changes for maximum 3600 seconds… $$
    Wait for message forwarding notification timed out. $$
    Wait for Site Reassign notification timed out. $$
    Wait for update notification timed out. $$
    C:\Program Files\Microsoft Configuration Manager\CMUStaging\ApplicabilityChecks\CM1702-KB4018732_AppCheck_239E18DA.sql has hash value SHA256:2ADF7C178C4489FD03721EB496DAD7A713548934FF466C2D1621DF652EE72B7C $$
    SQL MESSAGE: – Not a 1702 Fast Ring build, skip this hotfix $$
    Configuration Manager Update (PackageGuid=239E18DA-5872-47BF-93C5-9531A744C6F3) is not applicable and should be filtered. $$
    Check CMU status… $$
    Successfully checking Site server readiness for update. $$
    There are update package in progress. Cleanup will skip this time. $$
    Waiting for Configuration Manager Update changes for maximum 3600 seconds… $$
    Wait for message forwarding notification timed out. $$
    Check CFD status… $$
    Waiting for CFD changes for maximum 3600 seconds… $$
    Wait for site control change notification timed out. $$
    CheckPinResetCertificate() – start the pin reset certificate check task $$
    Pin reset cert scan threshold is not met yet. $$
    HandleRBACPermissions : Check if there is request. $$
    End sync rbac permissions. $$
    INFO: Enter HandleAIPermissions. $$
    INFO: Enter GetUserOfAIManageRole $$
    INFO: Enter GetUserOfAIDBRoleButNotManageRole $$
    INFO: Exit HandleAIPermissions. $$
    Update site server active directory information into DB $$
    INFO: .SLG file not found ~ $$
    CheckSQLServiceRestart : SQL Service hasn’t been restart since last time we check, skip it. $$
    ~Wait for site control changes for maximum 3600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$
    Successfully recorded currently running queries. $$
    running queries will be polled in 600 seconds… $$

    Any ideas?

    Cheers,
    Pedro

  14. Hi,

    We are still deploying 1511 in our task sequence, but it seems like after the update to SCCM 1706 the deployments fail..
    I have ADK installed of 1511. Can i just install ADK 1703? (in combination with deploy w10 1511?)

  15. hi,
    The update 1706 is successfull and everything looks fine except for boot image. it is still not updated. Any clue or suggestion why and how can i update this boot image.

  16. I’ve updates to 1706 in my lab. There are a few things that the don’t work appropriate way.
    1) Log compmon.log said that “Can not get the current execution state for component CONFIGURATION_MANAGER_UPDATE since it is not installed or completed installing.”. That is not true.The update process is finished. The console said all task were completed.
    2) Configuration Manager Service Manager does not communicate with most of components. I have no idea why because they work

    agl

  17. On the “Update Pack Installation Status” window my install appears to be stuck on “Replication – In Progress” and has been like that for three days (I left it running for the weekend)! In CMUpdate.log it reads;

    CONFIGURATION_MANAGER_UPDATE service is starting… CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    Microsoft System Center Configuration Manager v5.00 (Build 8498) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    Process ID: 1320 CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    Worker thread ID: 1408 CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    Set inbox to \\\SMS_XXX\inboxes\cmupdate.box CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    Getting SYSCENTERID & iLicenseType CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    Initializing the status message reporting system… CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    The path to the “Status Manager” inbox is “D:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs”. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:02 AM 1408 (0x0580)
    Registered this process as a source of “SMS Server” events. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 1408 (0x0580)
    Registered this process as a source of “SMS Client” events. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 1408 (0x0580)
    Registered this process as a source of “SMS Provider” events. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 1408 (0x0580)
    Status message reporting system initialized successfully. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 1408 (0x0580)
    Starting ConfigMgr Update post installation monitor thread… CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 1408 (0x0580)
    post installation monitor thread is starting, thread ID = 0x1068 (4200) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 1408 (0x0580)
    Waiting for changes to the “\\\SMS_XXX\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds… CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 1408 (0x0580)
    ConfigMgr update post installation monitoring thread started. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0001, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 4200 (0x1068)
    successfully detected service SMS_EXECUTIVE is running. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0001, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0002, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 4200 (0x1068)
    thread component SMS_DATABASE_NOTIFICATION_MONITOR is not detected to be running. current state is Stopping. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 4200 (0x1068)
    Waiting for registry changes of SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_EXECUTIVE\Threads\SMS_DATABASE_NOTIFICATION_MONITOR for maximum 1800 seconds… CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:07 AM 4200 (0x1068)
    successfully detected thread component SMS_DATABASE_NOTIFICATION_MONITOR is running. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:15 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0002, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:15 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0003, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:15 AM 4200 (0x1068)
    thread component SMS_HIERARCHY_MANAGER is not detected to be running. current state is Starting. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:15 AM 4200 (0x1068)
    Waiting for registry changes of SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_EXECUTIVE\Threads\SMS_HIERARCHY_MANAGER for maximum 1800 seconds… CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:15 AM 4200 (0x1068)
    successfully detected thread component SMS_HIERARCHY_MANAGER is running. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0003, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0004, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    successfully detected thread component SMS_REPLICATION_CONFIGURATION_MONITOR is running. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0004, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0005, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    successfully detected thread component SMS_POLICY_PROVIDER is running. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0005, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0006, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    check current replication details CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    successfully detected the site server is in ReplicationInactive state. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    Successfully reported ConfigMgr update status (SiteCode=XXX, SubStageID=0xe0006, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    ConfigMgr Update post installation monitor thread stopped. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:14:21 AM 4200 (0x1068)
    There are no pending update package to be processed. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:24:07 AM 1408 (0x0580)
    Waiting for changes to the “\\\SMS_XXX\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds… CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:24:07 AM 1408 (0x0580)
    There are no pending update package to be processed. CONFIGURATION_MANAGER_UPDATE 27/06/2017 9:34:07 AM 1408 (0x0580)

    It then just keeps repeating this;
    Waiting for changes to the “\\\SMS_XXX\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds…

    There are no pending update package to be processed.

    Looking in the cmupdate.box folder it is empty.

    Thoughts?? I don’t think I have the option to cancel the install so not sure what to do now…

      1. MS Updated the doc you linked to. No backwards compatible for ADK 1607. The only Win10 ADK version that SCCM 1706 supports is 1703.

          1. Personally we are still on ADK 1607 With SCCM 1706.
            And it seems to Work.

            At first I had upgraded to ADK 1703 but for some reason SCCM was still on Version 1607. When I was going to Update Distribution Point, The Currenct ADK Version shown was 1607, but I did update with the New ADK the boot image was Upgraded to 1703 but I couldn’t edit the boot image anymore. If somebody has any Idea on the one ?
            But yeah still is backward compatible.

  18. The beginning of this article is incorrect. “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 is from the checklist:

    Ensure that all sites run a version of System Center Configuration Manager that supports update to 1706:
    Each site server in the hierarchy must run the same version of System Center Configuration Manager before you can start the installation of update 1706. To update to 1706, you must use version 1606, 1610, or 1702.

    https://docs.microsoft.com/en-us/sccm/core/servers/manage/checklist-for-installing-update-1706#checklist

    1. Hi ,

      Its confusing, I was running 1511 in my Lab environment, updated to 1610 hoping I could jump to 1706. (after reading from the said #checklist) but still 1706 doesn’t appear in the console. I could only see 1702. There is no clear info about this infamous SCCM Upgrade 🙁

  19. I’m still having issues seeing the update. I’ve ran the fast ring PowerShell script I don’t see any errors flagged in dmpdownloader.log when looking at it. Would having Windows Updates disabled in group policy affect this?

    1. Hi Jordan,
      I had issue also, but forcing the Check for Update a couple time and wait did the trick.

      For some reason also, closing and re-opening the console helped more than the Refresh…

      Jonathan

Leave a Reply

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