Updates and servicing for Configuration Manager

Applies to: Configuration Manager (current branch)

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. The out-of-band updates are intended for customers who need to resolve issues that might be specific to their environment.


The terms upgrade, update, and install are used to describe three separate concepts in Configuration Manager. For more information about how each term is used, see About upgrade, update, and install.

Baseline and update versions

Use the latest baseline version when you install a new site in a new hierarchy.

  • Also use a baseline version to upgrade from System Center 2012 Configuration Manager.

  • After upgrading to Configuration Manager current branch, don't use baseline versions to stay current. Instead, only use in-console updates to update to the newest version.

  • Periodically, another baseline version is released. When you use the latest baseline version to install a new hierarchy, you avoid installing an outdated or unsupported version of Configuration Manager, followed by another update to your infrastructure.

After you install a baseline version, later versions of Configuration Manager are available as in-console updates. Use these updates to 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 the central administration site (CAS) automatically install at child primary sites. Control this timing by using a service window at the primary site. For more information, see Service Windows.

  • 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.

  • Use the files in the CD. Latest folder during site recovery. Also, when your hierarchy no longer runs a baseline version, use these files to install other sites.

  • You can't 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.

Version details

Some updates for Configuration Manager are available as both an in-console update version for existing infrastructure, and as a new baseline version.

Supported versions

The following supported versions of Configuration Manager are currently available as a baseline, an update, or both:

Version Availability date Support end date Baseline In-console update
April 22, 2024 October 22, 2025 YesNote 1 Yes
October 9, 2023 April 9, 2025 No Yes
April 10, 2023 October 10, 2024 YesNote 1 Yes
December 5, 2022 June 5, 2024 No Yes


The Availability date in this table is when the early update ring was released. Baseline media will be available on the VLSC soon after the update is globally available.

Note 1: How to get baseline media

The baseline media is available as part of the following releases on the Volume License Service Center (VLSC):

  • Microsoft Configmgr (current branch)
  • System Center Datacenter
  • System Center Standard

For example, search the VLSC for Microsoft Configmgr (current branch). Find the baseline media in the list of files, and download for that release.


The search string may be different on other media sites. For example, on the Visual Studio Subscriptions Portal, search for Microsoft Configuration Manager.

Historical versions

The following table lists historical versions of Configuration Manager current branch that are out of support:

Version Availability date Support end date Baseline In-console update
August 12, 2022 February 12, 2024 No Yes
April 6, 2022 October 6, 2023 Yes Yes
December 1, 2021 June 1, 2023 No Yes
August 2, 2021 February 2, 2023 No Yes
April 19, 2021 October 19, 2022 Yes Yes
November 30, 2020 May 30, 2022 No Yes
August 11, 2020 February 11, 2022 No Yes
April 1, 2020 October 1, 2021 Yes Yes
November 29, 2019 May 29, 2021 No Yes
July 26, 2019 January 26, 2021 No Yes
March 27, 2019 September 27, 2020 Yes Yes
November 27, 2018 December 1, 2020 No Yes
July 31, 2018 January 31, 2020 No Yes
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
1606 with KB3186654
October 12, 2016 October 12, 2017 Yes No
July 22, 2016 July 22, 2017 No Yes
March 11, 2016 March 11, 2017 No Yes
December 8, 2015 December 8, 2016 Yes No

How to check the version

To check the version of your Configuration Manager site, in the console go to About Configuration Manager at the top-left corner of the console. This dialog displays the site and console versions.


The console version is slightly different from the site version. The minor version of the console 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.

In-console updates and servicing

When you use a production-ready installation of Configuration Manager current branch, most updates 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. It includes only updates that Microsoft recommends for all customers.

These updates include:

  • New versions, like version 2207, 2211, or 2303.

  • Updates that include new features for your current version.

  • Hotfixes for your version of Configuration Manager and that all customers should install.


    In-console hotfixes have supersedence relationships. For more information, see Supersedence for in-console hotfixes.

The in-console updates deliver increased stability and resolve common issues. They replace the update types seen for previous product versions such as service packs, cumulative updates, hotfixes that are applicable to all customers, and the extension for Microsoft Intune.

The in-console updates can apply to one or more of the following systems:

  • Primary and CAS 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. Synchronize your Configuration Manager service connection point with the Microsoft cloud service, noting the following behaviors:

  • When your service connection point is in online mode, your site synchronizes with Microsoft every day. It automatically identifies new updates that apply to your infrastructure. To download updates and redistributable files, 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 more information about other locations used by the service connection point, see Internet access requirements.

  • When your service connection point is in offline mode, use the service connection tool to manually sync with the Microsoft cloud. For more information, see Use the service connection tool.

  • In-console updates replace the need to independently locate and install individual updates, service packs, and new features.

  • Install only the in-console updates you choose. When installing some updates, you can select individual features to enable and use. For more information, see Enable optional features from updates.

When you install an in-console update, the following process occurs:

  • It automatically runs a prerequisite check. You can also manually run this check before starting the installation.

  • It installs at the top-level site in your environment. This site is the CAS if there's one. In a hierarchy, the update automatically installs at primary sites. Control when each primary site server is allowed to update by using Service windows for site servers.

  • After a site server updates, all affected site system roles automatically update. These roles include instances of the SMS Provider. After the site installs the update, Configuration Manager consoles also prompt the console user to update the console.

  • If an update includes the Configuration Manager client, you're 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 don't automatically update. Instead, you must manually start the secondary site update.


The Configuration Manager current branch, the long-term servicing branch, and the technical preview branch are different releases. Updates that apply for one branch aren't available as in-console updates for the other branches. For more information about available branches, see Which branch of Configuration Manager should I use?.

Supersedence for in-console hotfixes

In-console hotfixes have supersedence relationships. When Microsoft publishes a new Configuration Manager hotfix, the console doesn't display any hotfixes that are superseded by this new hotfix. This new behavior helps you better determine which hotfixes to install.

Supersedence example

There are three hotfixes available: Hotfix-A, Hotfix-B, and Hotfix-C. Hotfix-A is superseded by Hotfix-B, and Hotfix-B is superseded by Hotfix-C.

Hotfix-A Hotfix-B Hotfix-C In-console view
Not installed Not installed Not installed Show all three hotfixes
Installed Installed Not installed Hotfix-B shows as installed
Hotfix-C shows as ready to install
Not installed Not installed Installed Hotfix-C shows as installed

Out-of-band hotfixes

Some hotfixes release with limited availability to address specific issues. Other hotfixes are applicable to all customers but can't install using the in-console method. These fixes are delivered out-of-band and not discovered from the Microsoft cloud service.

Typically, when you're seeking to fix or address a problem with your deployment of Configuration Manager, you can learn about out-of-band hotfixes from Microsoft customer support services, a Microsoft support knowledge base article, or the Configuration Manager team blog.

Install these fixes manually, using one of the following two methods:

Update Registration Tool

This tool manually imports the hotfix into your Configuration Manager console. Then install the update as you would in-console updates that are discovered automatically.

This method is used for hotfixes that use the following file name structure: <Product>-<product version>-<KB article ID>-ConfigMgr.Update.exe

For more information, see Use the update registration tool to import hotfixes.

Hotfix Installer

Use this tool to manually install a hotfix that can't 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.

Next steps

The following articles can help you understand how to find and install the different update types for Configuration Manager:

For more information about the technical preview branch, see Technical preview.