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: azure-local/update/update-troubleshooting-23h2.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ This scenario occurs when preparing to install system updates in Azure Update Ma
49
49
Follow the remediation instructions to resolve the failures.
50
50
51
51
> [!NOTE]
52
-
> The system health checks run every 24 hours, so it may take up to 24 hours for the new results to sync to the Azure portal after remediating the failures. To initiate a new system health check immediately or further troubleshoot, see the [PowerShell](update-troubleshooting-23h2.md#using-powershell) section.
52
+
> The system health checks run every 24 hours, so it may take up to 24 hours for the new results to sync to the Azure portal after remediating the failures. To initiate a new system health check immediately or further troubleshoot, see the [PowerShell](#using-powershell) section.
53
53
54
54
**Scenario 2: Update readiness checks**
55
55
@@ -67,7 +67,7 @@ This scenario occurs when installing and tracking system updates in Azure Update
67
67
68
68
Follow the remediation instructions to resolve the failures and then select the **Try again** button to retry the pre-update readiness checks and **Resume the update**.
69
69
70
-
To further troubleshoot, see the [PowerShell](#using-powershell) section.
70
+
To further troubleshoot, see the [PowerShell](#powershell) section.
71
71
72
72
### Using PowerShell
73
73
@@ -239,7 +239,7 @@ If there is an issue that causes an update to fail, reviewing the detailed step
239
239
240
240
- Failure message string (may pinpoint the issue to a specific known issue with documented remediation).
241
241
242
-
Microsoft recommends using the Azure portal to identify the failing step information as shown at [Resume an update](./update-troubleshooting-23h2.md#the-azure-portal). Alternatively, see the next section for how view similar details in PowerShell using `Start-MonitoringActionplanInstanceToComplete`.
242
+
Microsoft recommends using the Azure portal to identify the failing step information as shown at [Resume an update](#the-azure-portal). Alternatively, see the next section for how view similar details in PowerShell using `Start-MonitoringActionplanInstanceToComplete`.
243
243
244
244
See the table below for update failure scenarios and remediation guidelines.
245
245
@@ -253,7 +253,7 @@ See the table below for update failure scenarios and remediation guidelines.
253
253
254
254
You can also collect diagnostic logs to help Microsoft identify and fix the issues.
255
255
256
-
To collect logs for updates using the Azure portal, see [Resume an update](./update-troubleshooting-23h2.md#the-azure-portal).
256
+
To collect logs for updates using the Azure portal, see [Resume an update](#the-azure-portal).
257
257
258
258
To collect logs for the update failures see [Collect diagnostic logs for Azure Local, version 23H2](../manage/collect-logs.md?tabs=azureportal.md).
0 commit comments