Blog on Microsoft and Other Technologies.

Installing Update 1706 of System Center Configuration Manager

22 1,692

In this post we will see the steps for installing update 1706 of system center configuration manager. I still remember installing SCCM technical preview 1706 and we have the current branch version ready. Like previous updates, this update is available as in-console update. Most of all update 1706 is available for configuration manager sites running version 1606, 1610, or 1702. Therefore you can directly upgrade from SCCM 1606, 1610 and 1702 to version 1706. The update is rolled out globally and should be available in updates and servicing node. Seems like I had to run the powershell script just to get this update early.

Installing Update 1706 of System Center Configuration ManagerIn this post we will look at installing update 1706 with current version being SCCM 1702. I have my lab setup running current branch version 1702 and we will upgrade it to version 1706.

Update 1706 comes up lot of new features. Take a look at what’s new in SCCM version 1706 here. In addition I am listing some of the cool features included with Configuration Manager update 1706.

  • Peer cache improvements.
  • New Windows 10 compliance settings.
  • Three new MAM policy settings introduced.
  • Ability to manage Microsoft Surface driver updates.
  • Run PowerShell scripts from the Configuration Manager console.
  • Update comes with new device compliance policy rules.
  • Improved Azure AD integration with Configuration Manager.
  • Update reset tool to troubleshoot in-console updates.
  • Client Peer Cache support for express installation files for Windows 10 and Office 365.

Installing Update 1706 of System Center Configuration Manager

Let’s see the steps to install configuration manager update 1706. Launch the configuration manager console and click Administration > Overview > Updates and Servicing. On the top ribbon click Check for updates. Wait for the update to appear in the console. Right click Configuration Manager 1706 update and click Download.

Note – You may skip installing the configuration manager 1702 hotfix rollup. This update 1706 is cumulative and doesn’t require installation of the hotfix.

Installing Update 1706 of System Center Configuration Manager

Under Monitoring > Overview > Update and Servicing status, we see the update is downloading. Open the dmpdownloader.log file to view download progress.

Installing Update 1706 of System Center Configuration Manager

In the same node, check the update pack installation status. Click Refresh to see the progress of update installation.

Installing Update 1706 of System Center Configuration Manager

Once you see the update state as ready to install, right click update and click Install update pack.

Installing Update 1706 of System Center Configuration Manager

Since this update is installed on SCCM running on my lab setup, I chose to ignore pre-req check warnings. Click Next.

Installing Update 1706 of System Center Configuration Manager

You could enable the new features if required. I will leave it to default and click Next.

Installing Update 1706 of System Center Configuration Manager

For client update settings, I select Upgrade without validating. Click Next.

Installing Update 1706 of System Center Configuration Manager

For other steps click Next and finally click Close.

Installing Update 1706 of System Center Configuration Manager

In my lab setup it took almost 15 minutes for the update to install. When you refresh the console you see a box to upgarde the console. A new version of the console is available 5.00.8450.1300. Click OK to contine with upgrade.

Installing Update 1706 of System Center Configuration Manager

The update 1706 of SCCM installation is complete. Here are the details about site version and console version.

Version – 1706

Console version – 5.00.8540.1300

Site version – 5.0.8540.1000

Installing Update 1706 of System Center Configuration ManagerWhile i test out the awesome features, you can use this guide to install the update. If you have any questions, post it as comment or in community forums.

22 Comments
  1. Khan says

    Hello Prajwal,
    Successfully updated my QA site to 1610 from 1511. The console now shows only 1702 as the latest available updates, but not 1706. I am wondering if 1702 is required to upgrade to 1706 as against to MS check list for 1706.
    Thanks

    1. Prajwal Desai says

      I think you should wait for some more time and check the updates and servicing node.

      1. Khan says

        its over 5 days now 🙁

        1. Nigel Turner says

          If you look at the CMupdate.log you may see that it is waiting for a service window.
          You need to go to Administration > Site Configuration > Sites.
          Right click on your site and go to Properties. Look at the service window. You need to specify a window for the current time period so that it will update. Otherwise it will wait til the next window.

  2. Schikitar says

    I have not had any success installing 1706. First it got stuck on the “replication” step, left it for three days, nothing. So I used this method – https://www.andersrodland.com/sccm-upgrade-stuck-checking-prerequisites – to remove the update from the SQL database. This then cleared and redownloaded the update, now it’s stuck on “Installing” under updates but doesn’t appear in any logs or in status monitoring. You can’t manually run the update, it has to be done through the console which is equally frustrating.

  3. Mike Webber says

    We were able to install the update yesterday, but now the new clients break the communication with the distribution points. Has anyone else ran into this?

    https://www.reddit.com/r/SCCM/comments/6stmrl/sccm_upgrade_1702_1706_breaks_client/

  4. KONIK says
  5. KONIK says
    1. Prajwal Desai says

      I don’t see any errors anywhere. Since how long it’s stuck ?

      1. KONIK says

        from 7:29 last stat is check service window. Now is 11:30

        1. Pedro Roeseler says

          Same problem here but on build 1706… Stuck in the same spot for more than 4 hours… no errors on the logs…

          Any ideas?

          CMUPDATE.log:

          INFO: setup type: 1, top level: 1. $$
          Successfully reported ConfigMgr update status (SiteCode=PT1, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1) $$
          Successfully reported ConfigMgr update status (SiteCode=PT1, SubStageID=0xd0007, IsComplete=2, Progress=100, Applicable=1) $$
          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. $$
          Successfully reported ConfigMgr update status (SiteCode=PT1, SubStageID=0xd0008, IsComplete=2, Progress=100, Applicable=1) $$
          site server is not in service window yet. This will be checked in next polling cycle $$
          Waiting for changes to the “\our_server.our_domain.comSMS_PT1inboxescmupdate.box” directories, updates will be polled in 600 seconds… $$

          HMAN.log:

          INFO: Client baselines are up to date. $$
          Update client deployment compliance state per baseline definition. $$
          Waiting for Configuration Manager Client Upgrade changes for maximum 10742 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… $$
          Successfully recorded currently running queries. $$
          running queries will be polled in 600 seconds… $$

          1. Pedro Roeseler says

            Still no progress… the log keeps on saying
            “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.”

            Any ideas?

          2. Pedro Roeseler says

            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.”.
            Nigel Turner reply helped me a lot.

            Once I changed the maintenance window, the process re-started immediately.

            Cheers

            1. KONIK says

              this resolve our problem but this must be created some way automaticly dont create this …
              After delete service windows installation finish OK.

  6. John Hammond says

    Good day,
    I just updated my Primary to 1706 a week ago but 2 days later (before I started upgrading my distribution points), a hotfix dropped into the console. If I run that hotfix on my Primary and THEN upgrade my distribution points, will that upgrade include the hotfix or will I still have to run the hotfix afterwards?

    1. Prajwal Desai says

      The upgrade should include the hotfix.

      1. John Hammond says

        Thank you very much sir. I’ll post back to confirm once I’ve run it.

  7. Vineet says

    Hi,

    Can we migrate directly from SCCM 1602 to 1706 or its like we need to upgrade to versions (1606,1610, or 1702) before upgrading to 1706.

    1. Jacob says

      Hi Vineet,
      I just upgraded from 1606 to 1706 in my lab environment, things seem to be working still 🙂

  8. Chris says

    Hi Prajwal,
    we have a SCCM Server, which has been inplace-upgraded from Server 2012R2 to Server2016 and SCCM Version was updated from 1610 to 1706. We activated the Pre-Release-Feature to get Surface-Updates through WSUS and checked the Box to Receive Surface Driver and Firmware-Updates. Everything is fine with the Server and WSUS, BUT in wsyncmgr.log we get the following Message: “Surface Drivers can not be supported in this hierarchy because some of the SUP are not on Windows Server 2016, resetting SyncCatalogDrivers”

    So why does WSUS say this, when the Server has been updated to Server2016? The SUP of SCCM is on the same Server like WSUS-Console. SUP has been removed and readded with no luck.

    Do you have an Idea?

  9. Omar Al-Dweik says

    Hello,
    Same Issue with me cmUpdate log
    CServerStatusReporter::DeliverAsNTEvent(): ERROR: A status message could not be reported as a Windows NT Event, Win32 ReportEvent() returned error 1717: The interface is unknown.

Leave A Reply

Your email address will not be published.