Supported Upgrade Paths to ConfigMgr Current Branch

214_1

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

Baseline build Supported Release date (yyyy-MM-dd)
System Center Configuration Manager 1511 (Current Branch)  Ends 2016-12  2015-12-08
System Center Configuration Manager 1606 (Current Branch and LTSB)  Ends 2017-10  2016-10-12

Upgrade path to latest ConfigMgr Current Branch

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

Existing version Upgrade path to latest Current Branch version
ConfigMgr 2012 RTM In-Place upgrade to ConfigMgr 1511 baseline build and then In-Console update to ConfigMgr 1606
ConfigMgr 2012 SP1 In-Place upgrade to ConfigMgr 1511 baseline build and then In-Console update to ConfigMgr 1606
ConfigMgr 2012 SP2 In-Place upgrade to ConfigMgr 1606
ConfigMgr 2012 R2 In-Place upgrade to ConfigMgr 2012 R2 SP1, In-Place upgrade to ConfigMgr 1511 baseline build and then In-Console update to ConfigMgr 1606
In-Place upgrade to ConfigMgr 2012 R2 SP1 and then In-Place upgrade to ConfigMgr 1606
ConfigMgr 2012 R2 SP1 In-Place upgrade to ConfigMgr 1606
SCCM 2007 Perform a side-by-side migration to ConfigMgr 1606

Leave a Comment

Your email address will not be published. Required fields are marked *