What are Baseline versions in System Center Configuration Manager (Current Branch)

Note: This blog post was last updated 2019/4/2 to include info about the latest baseline release, version 1902.

Introduction

Microsoft recently released System Center Configuration Manager (Current Branch) version 1902. You can read the official announcement here and for a detailed list of what’s new, please see the following blog post.

I blogged about how you can do the upgrade from start to finish here.

In the documentation there’s a section called Baseline and update versions here, which describes what Baseline versions are and why you need them. In a nutshell since System Center Configuration Manager (Current Branch) originally released there have been a total of 5 Baseline releases.

  • 1511
  • 1606
  • 1702
  • 1802
  • 1902

These baselines are listed in the following document (I’ve added emphasis):

Baseline versions are downloadable media (from the Microsoft Volume License Service center) which can be used for a variety of installation methods.

  • Clean install of a new Configuration Manager (Current Branch) site in a new hierarchy.
  • Upgrade from a support version of System Center 2012 Configuration Manager.

These baseline versions are updated periodically to ensure that you have relatively recent media to do your clean installs or supported upgrades with, however most servicing (updating of the hierarchy) should be done in-console using the Updates and Servicing ability.

However, there are times (like now) when there can be a slight over lap. And that is when one baseline is about to become unsupported (1710) and it’s replacement media has not yet been released on the MVLSC site. If you browse the Configuration Manager Current Branch media on the MVLSC site you’ll see that the latest available baseline version is still listed as version 1802 (verified 2019/4/2 even though 1902 has been listed as the latest supported Baseline version.

So even though 1902 is listed as a new Baseline version, the Fast ring process is not yet complete, and as a result, any bug fixes or corrections to the media have not yet taken place before it is uploaded to the MVLSC.

Once 1902 moves into the Slow Ring in a couple of weeks and becomes generally available (show up in the Configuration Manager console), the 1902 baseline version will appear on the Licensing site soon after.

Until then, all Clean installs and Upgrades (for supported SCCM 2012 versions) should continue to use the 1802 baseline version.

Once complete, you should then use Updates and Servicing in the console to bring your hierarchy up to date.

This entry was posted in baseline version, System Center Configuration Manager (Current Branch). Bookmark the permalink.

13 Responses to What are Baseline versions in System Center Configuration Manager (Current Branch)

  1. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 1 | just another windows noob ?

  2. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 2 | just another windows noob ?

  3. Pingback: System Center Configuration Manager (Current Branch) version 1802 is now available on the eval site | just another windows noob ?

  4. Pingback: System Center Configuration Manager (Current Branch) version 1802 is available on VLSC now ! | just another windows noob ?

  5. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 3 | just another windows noob ?

  6. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 4 | just another windows noob ?

  7. Pingback: A summary of System Center Configuration Manager releases in 2018 and the new features – Part 1 (Current Branch) | just another windows noob ?

  8. Pingback: How can I upgrade to System Center Configuration Manager Current Branch version 1902 | just another windows noob ?

  9. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1902 on Windows Server 2019 with SQL Server 2017 – Part 1 | just another windows noob ?

  10. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1902 on Windows Server 2019 with SQL Server 2017 – Part 2 | just another windows noob ?

  11. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1902 on Windows Server 2019 with SQL Server 2017 – Part 3 | just another windows noob ?

  12. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1902 on Windows Server 2019 with SQL Server 2017 – Part 4 | just another windows noob ?

  13. Pingback: How can I install System Center Configuration Manager (Current Branch) version 1902 on Windows Server 2019 with SQL Server 2017 – Part 5 | just another windows noob ?

Leave a Reply

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