Skip to content

Commit 95169e9

Browse files
Merge pull request #294754 from SnehaSudhirG/17Feb-TSUpdate
fixed the error in headings
2 parents c0766ef + 94caea5 commit 95169e9

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

articles/update-manager/troubleshoot.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Troubleshoot known issues with Azure Update Manager
33
description: This article provides details on known issues and how to troubleshoot any problems with Azure Update Manager.
44
ms.service: azure-update-manager
5-
ms.date: 11/11/2024
5+
ms.date: 02/17/2025
66
ms.topic: troubleshooting
77
ms.author: sudhirsneha
88
author: SnehaSudhirG
@@ -90,22 +90,22 @@ The Virtual Machine Contributor role doesn’t have enough permissions.
9090
- Also, in scenarios where the Contributor role doesn’t work when the linked resources (gallery image or disk) is in another resource group or subscription, manually provide the managed identity with the right roles and permissions on the scope to unblock remediations by following the steps in [Grant permissions to the managed identity through defined roles](../governance/policy/how-to/remediate-resources.md).
9191

9292

93-
### Unable to generate periodic assessment for Arc-enabled servers
93+
## Unable to generate periodic assessment for Arc-enabled servers
9494

95-
#### Issue
95+
### Issue
9696

9797
The subscriptions in which the Arc-enabled servers are onboarded aren't producing assessment data.
9898

99-
#### Resolution
99+
### Resolution
100100
Ensure that the Arc servers subscriptions are registered to Microsoft.Compute resource provider so that the periodic assessment data is generated periodically as expected. [Learn more](../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider)
101101

102-
### Maintenance configuration isn't applied when VM is moved to a different subscription or resource group
102+
## Maintenance configuration isn't applied when VM is moved to a different subscription or resource group
103103

104-
#### Issue
104+
### Issue
105105

106106
When a VM is moved to another subscription or resource group, the scheduled maintenance configuration associated to the VM isn't running.
107107

108-
#### Resolution
108+
### Resolution
109109

110110
Maintenance configurations do not currently support the moving of assigned resources across resource groups or subscriptions. As a workaround, use the following steps for the resource that you want to move. **As a prerequisite, first remove the assignment before following the steps.**
111111

@@ -125,26 +125,26 @@ If any of the steps are missed, please move the resource to the previous resourc
125125
> [!NOTE]
126126
> If the resource group is deleted, recreate it with the same name. If the subscription ID is deleted, reach out to the support team for mitigation.
127127
128-
### Unable to change the patch orchestration option to manual updates from automatic updates
128+
## Unable to change the patch orchestration option to manual updates from automatic updates
129129

130-
#### Issue
130+
### Issue
131131

132132
You want to ensure that the Windows Update client won't install patches on your Windows Server so you want to set the patch setting to Manual. The Azure machine has the patch orchestration option as `AutomaticByOS/Windows` automatic updates and you're unable to change the patch orchestration to Manual Updates by using **Change update settings**.
133133

134-
#### Resolution
134+
### Resolution
135135

136136
If you don't want any patch installation to be orchestrated by Azure or aren't using custom patching solutions, you can change the patch orchestration option to **Customer Managed Schedules (Preview)** or `AutomaticByPlatform` and `ByPassPlatformSafetyChecksOnUserSchedule` and not associate a schedule/maintenance configuration to the machine. This setting ensures that no patching is performed on the machine until you change it explicitly. For more information, see **Scenario 2** in [User scenarios](prerequsite-for-schedule-patching.md#user-scenarios).
137137

138138
:::image type="content" source="./media/troubleshoot/known-issue-update-settings-failed.png" alt-text="Screenshot that shows a notification of failed update settings.":::
139139

140-
### Machine shows as "Not assessed" and shows an HRESULT exception
140+
## Machine shows as "Not assessed" and shows an HRESULT exception
141141

142-
#### Issue
142+
### Issue
143143

144144
* You have machines that show as `Not assessed` under **Compliance**, and you see an exception message below them.
145145
* You see an `HRESULT` error code in the portal.
146146

147-
#### Cause
147+
### Cause
148148

149149
The Update Agent (Windows Update Agent on Windows and the package manager for a Linux distribution) isn't configured correctly. Update Manager relies on the machine's Update Agent to provide the updates that are needed, the status of the patch, and the results of deployed patches. Without this information, Update Manager can't properly report on the patches that are needed or installed.
150150

0 commit comments

Comments
 (0)