@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Updates and servicing - Configuration Manager | Microsoft Learn+title: Updates and Servicing - Configuration Manager | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/intune/configmgr/core/servers/manage/updates breadcrumb_path: /intune/breadcrumb/toc.json uhfHeaderId: MSDocsHeader-Intune@@ -17,7 +17,7 @@ ms.reviewer: - hugowu - qiani description: Learn about the in-console service method called Updates and Servicing that makes it easy to locate and install recommended updates.-ms.date: 2026-09-22T00:00:00.0000000Z+ms.date: 2026-10-22T00:00:00.0000000Z ms.subservice: core-infra ms.topic: article ms.collection: tier3@@ -44,22 +44,22 @@ spProducts: platformId: 8cf6ccca-5d1d-2c98-820d-94311742041e --- -# Updates and servicing - Configuration Manager | Microsoft Learn+# Updates and Servicing - Configuration Manager | Microsoft Learn  *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.
+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.
 
 Tip
 
-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](../../understand/upgrade-update-install).
+The terms *upgrade*, *update*, and *install* are used to describe three separate concepts in Configuration Manager. For more information, see [About upgrade, update, and install](../../understand/upgrade-update-install).
 
 ## Baseline and update versions
 
 Use the latest baseline version when you install a new site in a new hierarchy.
 
-- After upgrading to Configuration Manager current branch, don't use baseline versions to stay current. Instead, only use [in-console updates](install-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 upgrade to Configuration Manager current branch, don't use baseline versions to stay current. Instead, use [in-console updates](install-in-console-updates) to update to the newest version.
+- Periodically, Microsoft releases another baseline version. 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.
 
@@ -69,8 +69,8 @@ After you install a baseline version, later versions of Configuration Manager ar 
 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](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.
+- 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.
 
 ### Version details
 
@@ -88,7 +88,7 @@ The following supported versions^`*`^, of Configuration Manager are currently av 
 Note
 
-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.
+The **Availability date** in this table is when the early update ring was released. Baseline media are available on the VLSC soon after the update is globally available.
 
 ##### Note 1: How to get baseline media
 
@@ -98,15 +98,15 @@ The baseline media is available as part of the following releases on the [Volume - `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.
+For example, search the VLSC for `Microsoft Configmgr (current branch)`. Find the baseline media in the list of files, and download it for that release.
 
 Note
 
-The search string may be different on other media sites. For example, on the [Visual Studio Subscriptions Portal](https://my.visualstudio.com/), search for `Microsoft Configuration Manager`.
+The search string might be different on other media sites. For example, on the [Visual Studio Subscriptions Portal](https://my.visualstudio.com/), search for `Microsoft Configuration Manager`.
 
 Note
 
-`*`**Supported Versions in Configuration Manager**: In the context of Configuration Manager, the term `supported` encompasses both *engineering* and *assisted technical support*. While no further engineering development will occur for the versions in question, users will not have access to phone or online assisted technical support for these versions. However, Technical Support will assist with upgrading to a supported version of Configuration Manager. Users will resume their regular assisted technical support once Configuration Manager is upgraded to a supported version."
+`*`**Supported Versions in Configuration Manager**: In the context of Configuration Manager, the term `supported` encompasses both *engineering* and *assisted technical support*. While no further engineering development will occur for the versions in question, users won't have access to phone or online assisted technical support for these versions. However, Technical Support will assist with upgrading to a supported version of Configuration Manager. Users will resume their regular assisted technical support once Configuration Manager is upgraded to a supported version.
 
 #### Historical versions
 
@@ -145,21 +145,21 @@ The following table lists historical versions of Configuration Manager current b 
 #### 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.
+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.
 
 Note
 
-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 2303 the initial site version is 5.0.9122.1000, and the initial console version is 5.**9122**.1082.1700. The build (1082) and revision (1700) numbers may change with future hotfixes.
+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 2303 the initial site version is 5.0.9122.1000, and the initial console version is 5.9122.1082.1700. The build (1082) and revision (1700) numbers might 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.
+When you use a production-ready installation of Configuration Manager current branch, you can get most updates through 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
 - Updates that include new features for your current version
-- Hotfixes for your version of Configuration Manager and that all customers should install
+- Hotfixes for your version of Configuration Manager that all customers should install
 
     Note
 
@@ -184,7 +184,7 @@ Configuration Manager discovers new updates for you. Synchronize your Configurat 
 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 automatically runs a prerequisite check. You can also manually run this check before you start 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](service-windows).
 - 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.
@@ -192,15 +192,15 @@ When you install an in-console update, the following process occurs: 
 Note
 
-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?](../../understand/which-branch-should-i-use).
+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?](../../understand/which-branch-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.
+In-console hotfixes have supersedence relationships. When Microsoft publishes a new Configuration Manager hotfix, the console doesn't display any hotfixes that this new hotfix supersedes. 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.
+Three hotfixes are 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 |
 | --- | --- | --- | --- |
@@ -210,24 +210,24 @@ There are three hotfixes available: Hotfix-A, Hotfix-B, and Hotfix-C. Hotfix-A i 
 ## 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.
+Some hotfixes release with limited availability to address specific issues. Other hotfixes are applicable to all customers but can't install by using the in-console method. These fixes are delivered out-of-band and aren't 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](https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/bg-p/ConfigurationManagerBlog).
+Typically, when you want 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](https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/bg-p/ConfigurationManagerBlog).
 
-Install these fixes manually, using one of the following two methods:
+Use one of the following methods to manually install these fixes:
 
 ### 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 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`
+Use this method 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](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.
+Use this tool to manually install a hotfix that you can't install by 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`
+Use this method 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](use-the-hotfix-installer-to-install-updates).\ No newline at end of file