Microsoft recently release System Center Configuration Manager (Current Branch) version 1802. 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 4 Baseline releases.
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 (1702) 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 1702 (verified 2018/3/25) even though 1802 has been listed as the latest supported Baseline version.
So even though 1802 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 1802 moves into the Slow Ring in a couple of weeks and becomes generally available (show up in the Configuration Manager console), the 1802 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 1702 baseline version even though it’s official support date ends 2018/3/27.
Once complete, you should then use Updates and Servicing in the console to bring your hierarchy up to date.