Updates for System Center Configuration Manager
Applies to: System Center Configuration Manager (Current Branch)
System Center Configuration Manager uses an in-console service method called Updates and Servicing. This in-console method makes it easy to find and install recommended updates for your Configuration Manager infrastructure. In-console servicing is supplemented by out-of-band updates such as hotfixes that are intended for customers who need to resolve issues that might be specific to their environment.
When managing System Center Configuration Manager site and hierarchy infrastructure, the terms upgrade, update, and install are used to describe three separate concepts. To learn how each term is used, see About upgrade, update, and install.
The following topics can help you understand how to find and install the different update types for System Center Configuration Manager:
If you use the Technical Preview branch, see Technical Preview for System Center Configuration Manager for additional information that is specific to that branch.
Baseline and update versions
The first release of System Center Configuration Manager current branch was version 1511, which was a baseline version. More recent baseline versions include version 1702, and 1802:
Use the latest baseline version when you install a new site in a new hierarchy.
You use a baseline version to upgrade from System Center 2012 Configuration Manager. After upgrading to System Center Configuration Manager, you can no longer use baseline versions to stay current and instead only use in-console updates to update to the newest version.
Periodically, additional baseline versions are released. When you use the latest baseline version to install a new hierarchy, you avoid installing an outdated version of Configuration Manager followed by an additional upgrade of your infrastructure to bring it up to date.
After you install a baseline version, additional versions of Configuration Manager are available as in-console updates. In-console updates update your infrastructure to the latest version of Configuration Manager.
You install in-console updates to update the version of your top-level site.
Updates you install at central administration site automatically install at child primary sites, unless blocked by a maintenance window you have configured at the primary site.
You manually update secondary sites to a new update version from within the console.
When you install an update, the update stores installation files for that version on the site server in a folder named CD.Latest. For more information about these files, see The CD.Latest folder for System Center Configuration Manager.
You use the files in the CD.Latest folder during Site Recovery and to install additional sites in a hierarchy that no longer runs a baseline version.
You cannot use installation files from CD.Latest to install the first site of a new hierarchy, or to upgrade a site from System Center 2012 Configuration Manager.
Some updates for Configuration Manager are available as both an in-console update version for existing infrastructure, and as a new baseline version.
The following versions of Configuration Manager are available as a baseline, an update, or both:
|Version||Availability date||Support end date||Baseline||in-console update|
|March 22, 2018||September 22, 2019||Yes||Yes|
|November 20, 2017||May 20, 2019||No||Yes|
|July 31, 2017||July 31, 2018||No||Yes|
|March 27, 2017||March 27, 2018||Yes||Yes|
|November 18, 2016||November 18, 2017||No||Yes|
|July 22, 2016||July 22, 2017||No||Yes|
|1606 with the 1606 hotfix rollup (KB3186654)
5.00.8412.1307 (Note 1)
|October 12, 2016||October 12, 2017||Yes||No|
|March 11, 2016||March 11, 2017||No||Yes|
|December 8, 2015||December 8, 2016||Yes||No|
(Note 1) The 1802 and 1702 baseline media are available as part of the Microsoft System Center 2016 or System Center Configuration Manager (Current Branch and Long-Term Servicing Branch) releases on the Volume License Service Center (VLSC). For example, on the VLSC you can search for System Center Config Mgr (current branch and LTSB), and both 1802 and 1702 version baseline media are returned, and available for download.
To check the version of your Configuration Manager site, in the console go to About System Center Configuration Manager at the top-left corner of the console where the new site and console version displays.
Starting in version 1802, the console version is now slightly different from the site version. The minor version of the console now corresponds to the Configuration Manager release version. For example, in Configuration Manager version 1802 the initial site version is 5.0.8634.1000, and the initial console version is 5.1802.1082.1700. The build (1082) and revision (1700) numbers may change with future hotfixes to the 1802 release.
In-console updates and servicing
When you use a production ready installation of System Center Configuration Manager, also referred to as the current branch, most updates you install are available using the Updates and Servicing channel. This method identifies, downloads, and makes available the updates that apply to your current infrastructure version and configuration, and includes only updates that Microsoft recommends for all customers.
New versions, like version 1702, 1706, 1710, or 1802.
Updates, that include new features for your current version.
Hotfixes, for your version of Configuration Manager and that all customers should install.
The in-console updates deliver increased stability and resolve common issues. They replace the update types seen for previous product versions for service packs, cumulative updates, hotfixes that are applicable to all customers, and Extension for Microsoft Intune. These updates can apply to one or more of the following:
Primary and central administration site servers
Site system roles and site system servers
Instances of the SMS Provider
Configuration Manager consoles
Configuration Manager clients
Configuration Manager discovers new updates for you when you synchronize your service connection point site system role with the Microsoft cloud service and download center:
When your service connection point is in online mode, your site synchronizes with Microsoft every day to automatically identify new updates that apply to your infrastructure. To download updates and redist files for updates, the computer that hosts the Service Connection Point site system role uses the System context to access the following Internet locations: go.microsoft.com and download.microsoft.com. For information about additional locations the service connection point connects to, see Internet access requirements in About the service connection point in System Center Configuration Manager.
When your service connection point is in offline mode, you use the service connection tool to manually sync with the Microsoft cloud. For more information, see Use the Service Connection Tool for System Center Configuration Manager.
In-console updates replace the need to independently locate and install individual updates, service packs, and new features.
You install only the in-console updates you choose, and when installing some updates you can select the individual features you want to enable and use. For more information, see Enable optional features from updates.
When you install an in-console update:
It automatically runs a prerequisite check. You can also run this check prior to starting the installation.
It installs at the central administration site (if you have one), and at primary sites automatically. You can control when each primary site server is allowed to update its infrastructure by using Service windows for site servers.
After a site server updates, all affected site system roles (including instances of the SMS Provider) automatically update. Configuration Manager consoles also prompt the console user to update the console, after the site installs the update.
If an update includes the Configuration Manager client, you are offered the option to test the update in pre-production, or to apply the update to all clients immediately.
After a primary site is updated, secondary sites do not automatically update. Instead, you must initiate the secondary site update.
The production release of System Center Configuration Manager (current branch), the Long-Term Servicing Branch, and the Technical Preview for System Center Configuration Manager are different releases. Therefore, updates that apply for one branch are not available as in-console updates for the other branches. For more information about available branches, see Which branch of Configuration Manager should I use?
Some hotfixes release with limited availability to address specific issues, or are applicable to all customers but cannot install using the in-console method. These fixes are delivered out-of-band and not discovered from the Microsoft cloud service.
Typically, you learn about out-of-band hotfixes from Microsoft customer support services, a Knowledge Base article, or from the System Center Configuration Manager Team blog when you are seeking to fix or address a problem with your deployment of Configuration Manager.
You install these fixes manually, using one of two methods:
Update Registration Tool: This tool manually imports the hotfix into your Configuration Manager console where you can then install the update as you would in-console updates that are discovered automatically. This method is used for updates that use the following file name structure: .update.exe. The full file name for this type of hotfix resembles: <Product>-<product version>-<KB article ID>-ConfigMgr.Update.exe.
For more information, see Use the Update Registration Tool to import hotfixes to System Center Configuration Manager.
Hotfix Installer: This tool is used to manually install a hotfix that cannot be installed using the in-console method. This method is used for fixes that use the following file name structure: <Product>-<product version>-<KB article ID>-<platform>-<language>.exe.
For more information, see Use the Hotfix Installer to install updates for System Center Configuration Manager.