Skip to content

Commit dabc665

Browse files
authored
Update understand-troubleshoot-updates-servicing.md
Edit Review in progress
1 parent 30d73a5 commit dabc665

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

support/mem/configmgr/setup-migrate-backup-recovery/understand-troubleshoot-updates-servicing.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Understand and Troubleshoot the Updates and Servicing process
3-
description: This article helps administrators understand Updates and Servicing and troubleshoot some common issues in Configuration Manager.
3+
description: This article helps administrators understand Updates and Servicing, and troubleshoot some common issues in Configuration Manager.
44
ms.date: 11/17/2025
55
ms.reviewer: kaushika, payur
66
ms.custom: sap:Configuration Manager Setup, High Availability, Migration and Recovery\Updates and Servicing
@@ -14,7 +14,7 @@ This article helps administrators understand the Updates and Servicing process i
1414

1515
Configuration Manager synchronizes with the Microsoft Cloud service to get updates that apply to your infrastructure and version. You can use the Configuration Manager console to install these updates.
1616

17-
To view and manage the updates, in the Configuration Manager console that's connected to the top-level site, go to **Administration** > **Cloud Services** > **Updates and Servicing** For more information, see [Install in-console updates for Configuration Manager](/intune/configmgr/core/servers/manage/install-in-console-updates).
17+
To view and manage the updates, open the Configuration Manager console that's connected to the top-level site, and then go to **Administration** > **Cloud Services** > **Updates and Servicing**. For more information, see [Install in-console updates for Configuration Manager](/intune/configmgr/core/servers/manage/install-in-console-updates).
1818

1919
## Best practices for updates
2020

@@ -55,11 +55,11 @@ Before you install an update, consider running the prerequisite check for that u
5555
## Prepare to troubleshoot Updates and Servicing issues
5656

5757
> [!IMPORTANT]
58-
> When you troubleshoot an Updates and Servicing issue, avoid the following actions:
58+
> When you troubleshoot an Updates and Servicing issue, avoid taking the following actions:
5959
>
6060
> - Manually cleaning up any related folders (\\EasySetupPayload, \\CMUStaging). Only manually change these folder locations if Microsoft Support instructs you to.
61-
> - Manually cleaning up any SQL tables. Only manually change information in these tables if Microsoft Support instructs you to.
62-
> - Restoring the Configuration Manager database and/or Configuration Manager site server if there's an error during the upgrade. Instead, fix the issue, and then try again to install.
61+
> - Manually cleaning up any SQL tables. Don't manually change information in these tables unless a Microsoft Support agent instructs you to.
62+
> - Restoring the Configuration Manager database or Configuration Manager site server if an error occurs during the upgrade. Instead, fix the issue, and then try again to install.
6363
> - Reinstalling a Service Connection Point during the installation.
6464
> - Restarting the Configuration Manager Update service during the installation.
6565
> - Keeping the \CMUStaging\ folder open during the installation.
@@ -69,9 +69,9 @@ Before you install an update, consider running the prerequisite check for that u
6969
7070
### Identify the update package GUID
7171

72-
Before you troubleshoot an update issue, identify the GUID of the update package. To view the GUID, if the update package is visible in the Configuration Manager Console, add the **Package Guid** column to the **Administration** > **Update and Servicing** node.
72+
Before you troubleshoot an update issue, identify the GUID of the update package. To view the GUID of an update package that's visible in the Configuration Manager console, add the **Package Guid** column to the **Administration** > **Update and Servicing** node.
7373

74-
Sometimes, the console doesn't list the affected update package. In this case, you can find the GUID in the Configuration Manager database. To find the GUID, run a SQL query that resembles the following excerpt:
74+
If the console doesn't list the affected update package, you can find the GUID in the Configuration Manager database. To find the GUID, run a SQL query that resembles the following excerpt:
7575

7676
```sql
7777
SELECT Name, PackageGuid FROM v_LocalizedUpdatePackageMetaData_SiteLoc
@@ -103,7 +103,7 @@ During the update process, an update package passes through the following stages
103103
Knowing the stage at which the update failed gives you a starting point for troubleshooting the issue. Use the following diagram to identify the stage of the update package installation.
104104

105105
> [!NOTE]
106-
> The Replication stage is part of either the Prerequisite check stage or the Installation stage, so it's not listed separately in the diagram.
106+
> The Replication stage is part of either the Prerequisite check stage or the Installation stage. Therefore, it's not shown separately in the diagram.
107107
108108
:::image type="content" source="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-scope-issue-to-stage.png" alt-text="Diagram of a decision tree to identify the installation state." lightbox="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-scope-issue-to-stage-expanded.png":::
109109

0 commit comments

Comments
 (0)