MSEndpointMgr
Home » Microsoft Endpoint Manager » ConfigMgr » Supported Upgrade Paths to ConfigMgr Current Branch

Supported Upgrade Paths to ConfigMgr Current Branch

For a while now, we’ve seen Microsoft releasing new versions for System Center Configuration Manager (also known as ConfigMgr Current Branch) and this will continue in a rapid pace just like it has for the past year. For organizations that have still not upgraded their ConfigMgr hierarchy, this blog post is intended to serve as guidance for those scenarios, showing what the supported upgrade path is for all supported versions. This post will be updated whenever a new version of ConfigMgr Current Branch has been released.

ConfigMgr Baseline builds

When upgrading to ConfigMgr Current Branch, you a baseline build in order to get to the absolute latest bits. Below is a table of all baseline builds showing support state, release date and the currently recommended build (marked as bold) to use during an upgrade process (from any System Center 2012 Configuration Manager) or new installation. Baseline builds should only be used when performing any of the following tasks:

  • Use the latest baseline version when you install a new site in a new hierarchy.
  • You must use a baseline version to upgrade from System Center 2012 Configuration Manager.
  • Periodically, new baseline versions will be released. When you use a newer baseline version to install a new hierarchy you avoid installing the original 1511 baseline followed by an upgrade of your infrastructure.

For more information regarding baseline builds, read the following documentation post:
https://docs.microsoft.com/en-us/sccm/core/servers/manage/updates#bkmk_Baselines

Configuration Manager Current Branch buildsVersionBaselineRelease date (yyyy-MM-dd)Support Ends (yyyy-MM-dd)
System Center Configuration Manager 15115.00.8325.1000Yes2015-12-082016-12-08
System Center Configuration Manager 16025.00.8355.1000No (in-console update)2016-03-112017-03-11
System Center Configuration Manager 16065.00.8412.1000No (in-console update)2016-07-222017-07-22
System Center Configuration Manager 1606 with the 1606 hotfix rollup (KB3186654)5.00.8412.1307Yes2016-10-122017-10-12
System Center Configuration Manager 16105.00.8458.1000No (in-console update)2016-11-182017-11-18

Upgrade path to latest ConfigMgr Current Branch

The table below shows the supported upgrade paths for the latest version of ConfigMgr Current Branch.

Existing versionUpgrade path to latest Current Branch version
ConfigMgr 2012 RTMIn-Place upgrade to ConfigMgr 1606 baseline build and then In-Console update to latest available
ConfigMgr 2012 SP1In-Place upgrade to ConfigMgr 1606 baseline build and then In-Console update to latest available
ConfigMgr 2012 SP2In-Place upgrade to ConfigMgr 1606 baseline build and then In-Console update to latest available
ConfigMgr 2012 R2In-Place upgrade to ConfigMgr 1606 baseline build and then In-Console update to latest available
ConfigMgr 2012 R2 SP1In-Place upgrade to ConfigMgr 1606 baseline build and then In-Console update to latest available
SCCM 2007Perform a side-by-side migration to ConfigMgr 1606

(7712)

Nickolaj Andersen

Chief Technical Architect and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences such as Microsoft Ignite, NIC Conference and IT/Dev Connections including nordic user groups.

2 comments

  • Nickolaj ,
    Question for you if you don’t mind
    I just took over a poorly built sccm 2012 environment that isnt worth fixing and I need to build out new sccm 2016 cas server. My question is, is there any issues with having 2 CAS servers in the same forest ? I know that the boundaries can’t overlap and site information can’t be the same. I plan on removing. the old server eventually. Any information would be great!! Thanks

    • Hi Ian,
      It would work, but I’d obviously not recommend to stand a new environment where you include a CAS server unless you need to manage more than 150 000+ servers. If less than that a stand-alone Primary site server is sufficient.
      Regards,
      Nickolaj

Sponsors

Subscribe

Do you want to be notified of new posts on our site?

Please enter your email address below:

Categories

MSEndpointMgr.com use cookies to ensure that we give you the best experience on our website.