SCCM Configmgr Current Branch 1606 is now available

Yesterday (22-July-2016) Microsoft released new version of SCCM Configmgr Current Branch 1606 (YY MM) with lot of new features and improvements to the existing features. You can install this update via in-console update.

You can update to latest version of SCCM Configmgr Current branch 1606 either from Configmgr 1511 or 1602 using in-console update.

This Version 1606 for SCCM Configmgr current branch is both a baseline install (which you use to install a new hierarchy), and an update which you can use to update from version 1511 or 1602.

Take a look at the checklist document for installing this update (1606)

As usual ,to get the Latest update (1602) in your console under administrative console—>Cloud services—>updates and Servicing ,you need to run the PowerShell script (fastring) and restart SMS executive service (only if you are on V1511 version) ,monitor dmpdownloader.log

Installing the update 1606 is a straight forward process within the console and is smooth process without any hassle. You can refer this blog post for,how to install SCCM Configmgr Updates using updates and Servicing.

To know more about ,what’s new in SCCM Configmgr Current Branch 1606 ,read


Configmgr Console,Site and Console Versions:

Version of Configmgr Console: 5.00.8412.1003

Version of Configmgr Site:5.00.8412.1000

Version of Configmgr Client: 5.00.8412.1006


If you unable to see SCCM Configmgr updates in console ,refer this blog post

Recommended Reading:

Updates for System Center Configuration Manager

What’s new in SCCM Configmgr Current Branch 1606

What's changed in System Center Configuration Manager from System Center 2012 Configuration Manager

Upgrade to System Center Configuration Manager

4 Responses to "SCCM Configmgr Current Branch 1606 is now available"

  1. Little tip if you don't have update 1606 visible in console 1602. Problem is when you previously use MS powershell script to make visible 1602...
    Use same script but change value to "2" ($EmbeddedProperty.Value = 2) and ($oProp.Value=2). Then restart SMS_EXECUTIVE. If is value set to 1 then applicabilitychecks script return "SET @Applicable = 393213" APPLICABILITY_HIDE . I had this situation in the lab and two production servers...


Leave a Reply