You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/mem/configmgr/setup-migrate-backup-recovery/understand-troubleshoot-updates-servicing.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ Knowing the stage at which the update failed gives you a starting point for trou
105
105
> [!NOTE]
106
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.
107
107
108
-
:::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.png":::
108
+
:::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":::
109
109
110
110
> [!IMPORTANT]
111
111
> If the update package doesn't appear in either the console or in the Windows PowerShell output, the installation might be in the Applicability stage. Search the top-level site's SQL CM_UpdatePackages table. Use a query that resembles the following excerpt:
@@ -265,7 +265,7 @@ Updates that aren't applicable (and aren't visible in the console) have entries
265
265
266
266
If you suspect that your issue occurs in the Synchronization stage, use the following flowchart to investigate which components might be involved and which processes the issue affects.
267
267
268
-
:::image type="content" source="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-synchronization-stage.png" alt-text="Diagram of a decision tree to isolate an issue that might occur during the Synchronization stage." lightbox="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-synchronization-stage.png":::
268
+
:::image type="content" source="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-synchronization-stage.png" alt-text="Diagram of a decision tree to isolate an issue that might occur during the Synchronization stage." lightbox="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-synchronization-stage-expanded.png":::
269
269
270
270
The following steps summarize this troubleshooting process. The steps vary depending on whether your SCP is configured in Online mode or Offline mode.
271
271
@@ -303,7 +303,7 @@ The following steps summarize this troubleshooting process. The steps vary depen
303
303
304
304
If you suspect that your issue occurs in the Applicability check stage, use the following flowchart to investigate which components might be involved and which processes the issue affects.
305
305
306
-
:::image type="content" source="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-application-stage.png" alt-text="Diagram of a decision tree to isolate an issue that might occur during the Applicability check stage." lightbox="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-application-stage.png":::
306
+
:::image type="content" source="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-applicability-stage.png" alt-text="Diagram of a decision tree to isolate an issue that might occur during the Applicability check stage." lightbox="./media/understand-troubleshoot-updates-servicing/cm-updates-and-servicing-applicability-stage-expanded.png":::
307
307
308
308
Additionally, you also need information from the top-level Site SQL Database. Use the following query:
0 commit comments