Close Menu
    Facebook X (Twitter) Instagram
    Sunday, May 18
    X (Twitter) LinkedIn
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»configmgr»1606»SCCM Configmgr Current Branch 1606 is now available

    SCCM Configmgr Current Branch 1606 is now available

    Eswar KonetiBy Eswar KonetiJuly 24, 12:44 am2 Mins Read 1606 3,023 Views
    Share
    Facebook Twitter LinkedIn Reddit

    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) https://technet.microsoft.com/en-us/library/mt767553.aspx?f=255&MSPPError=-2147217396

    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 https://technet.microsoft.com/en-us/library/mt752488.aspx

    image

    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

    image

    If you unable to see SCCM Configmgr updates in console ,refer this blog post http://eskonr.com/2016/04/why-dont-i-see-sccm-configmgr-1602-updates-in-my-console/

    Recommended Reading:

    Updates for System Center Configuration Manager https://technet.microsoft.com/en-us/library/mt607046.aspx?f=255&MSPPError=-2147217396

    What’s new in SCCM Configmgr Current Branch 1606 https://technet.microsoft.com/en-us/library/mt752488.aspx

    What's changed in System Center Configuration Manager from System Center 2012 Configuration Manager  https://technet.microsoft.com/en-us/library/mt622084.aspx?f=255&MSPPError=-2147217396

    Upgrade to System Center Configuration Manager https://technet.microsoft.com/en-us/library/mt627853.aspx

    1606 5.00.8412.1000 cm configmgr Current branch fastRing Powershell SCCM SCCM CB
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    Optimize Your Intune Workflow with a Powerful Browser Extension

    March 22, 10:39 am

    Migrate Microsoft 365 Updates from SCCM/MECM to Intune for Co-Managed Devices

    February 11, 9:50 pm

    Investigating Co-Management Issues with Windows Endpoints in SCCM/Intune

    October 26, 10:45 pm

    4 Comments

    1. Andrews on July 29, 2016 5:42 PM

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

      Reply
      • Eswar Koneti on August 3, 2016 11:16 PM

        Hi andrews,
        Great Tip ,thank you. I will update the blog post.

        Thanks,
        Eswar

        Reply
    2. Henrik Bierbum Bacher on July 25, 2016 3:22 PM

      Apparently 1606 is not a baseline build, there is a typo in the documentation: https://twitter.com/djammmer/status/757174980991778816

      Reply
      • Eswar Koneti on August 3, 2016 11:20 PM

        Hi Henrik,
        thats true and i noticed it from dJammer via twitter and updated the blog post.

        thanks,
        Eswar

        Reply

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2024 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.