SCCM Configmgr Current Branch update 1610 available

Microsoft released Update 1610 for SCCM Configmgr current branch (CB) that is available as an in-console update for previously installed sites that run version 1511, 1602, or 1606 which includes some great new features and product enhancements.

This update (1610) includes lots of new features and enhancements in Windows 10 and Office 365 management, application management, end user experience, client management and also includes new functionality for customers using Configuration Manager in hybrid mode with Microsoft Intune.

changes and new capabilities introduced in version 1610 of Configuration Manager current branch are:

  • In-console monitoring of update installation status
  • Exclude clients from automatic upgrade
  • Improvements for boundary groups
  • Peer Cache for content distribution to clients
  • Migrate multiple shared distribution points at the same time
  • Cloud management gateway for managing Internet-based clients
  • Improvements to the Windows 10 Edition Upgrade Policy
  • Manage hardware identifiers
  • Enhancements to Windows Store for Business integration with Configuration Manager
  • Policy sync for Intune-enrolled devices
  • Use compliance settings to configure Windows Defender settings
  • General improvements to Software Center
  • Customizable Branding for Software Center Dialogs
  • Enforcement grace period for required application and software update deployments
  • Improved functionality for required software dialogs
  • Software updates dashboard
  • Improvements to the application request process
  • Filter by content size in automatic deployment rules
  • Office 365 Client Management dashboard
  • Task sequence steps to manage BIOS to UEFI conversion
  • New compliance settings for configuration items
  • Improvements to the Prepare ConfigMgr Client for Capture task sequence step

For more information ,Whats new in Configmgr Current branch 1610 on https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1610

How to get this update available in your Configmgr Current branch ?

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 on your central administration site or standalone primary site, you will see the update available in your console right away.

Launch the console ,administration node—>updates and servicing—>Click check for updates.

Account that you use to run this ,make sure the security scope is set to All ,for more information ,read http://eskonr.com/2016/04/why-dont-i-see-sccm-configmgr-1602-updates-in-my-console/

image

If you are not able to see the updates ,run the powershell script.

Download the script and launch powershell cmd using administrator ,run it using the syntax:

EnableFastUpdateRing1610.ps1 <SiteServer_Name | SiteServer_IP> where SiteServer refers to the CAS or standalone primary site server

image

Monitor dmpdownloader.log to know the status of update downloading.

If the update installation is suspended at “Downloading” state for extended period of time, restart the SMS_EXECUTIVE (smsexec) service on the standalone primary or central administration site server (CAS).

image

After a while you will see updates in the console.

Once the download is ready ,state will be changed to available and ready for installation.

Right click on the update and choose Install Update Pack ,choose next next next depends on the options you need.

For installation status ,monitor CMUpdate.log .

1610 update has following version for:

Console Version:5.0.8458.1500

Site Version:5.0.8458.1000

Client Version:5.00.8458.1005

image

10 Responses to "SCCM Configmgr Current Branch update 1610 available"

  1. Hi Eswar do you know why my update didnt start, the download ended fine (dmpdownloader.log) the state says "Installing" but in the CMUpdate.log nothing happen

    Reply
    1. Hi Ernesto,
      did you look at the monitoring node-->Updates and servicing status for installation status or ConfigMgrSetup.log in root drive (C:) ?

      Regards,
      Eswar

      Reply
  2. Hi Eswar,
    Quick question, is it possible to roll back ConfigMgr Current Branch installation.
    For example, if I have issues with new CB 1610 version and would like to roll back, is there option to revert to previous version (1606) or that is not possible.
    Thanks,
    Vern

    Reply
    1. Hi Venon,
      Never looked at rollback installed updates in current branch and never heard of any issues that cause to rollback. If you really have issues with new updates ,you can report to microsoft and if the issue is genuine ,you wont be charged for that .You can also file the issue in connect.microsoft.com
      btw,what issues do you have ?

      Regards,
      Eswar

      Reply
    1. Hi,
      i would suggest to look at dmpdownloader.log to see the download progress also check if you have access to internet on the server.

      Regards,
      Eswar

      Reply
    2. Hello, since I am now trying to install the update now I also noticed for the first time that the download was not working this never happened before. But after looking thru the dmpdownloader.log it was not able to extract the package af633310-e419-44b3-9e0e-ab93d57087cf.cab as it turns out that there is a autorun.inf which our antivirus was blocking. I would suggest disabling the AV while the extraction occurs.

      Reply
  3. Hi Eswar, thanks for this. I have a question - once you have run EnableFastUpdateRing1610.ps1 and then applied 1610, how do you turn it off again - to go back to slow ring?

    Reply
    1. Hi,
      You dont need to turn it off or no such option exist to convert fast ring to slow ring. It will automatically set back to slow ring during the next update cycle. so you can simply ignore it.

      regards,
      Eswar

      Reply

Leave a Reply