Skip to content

Commit 61cce11

Browse files
Merge pull request #265989 from SnehaSudhirG/12Feb-PeriodicAssessmentUpdate
Added new info in TSG and added note in P.Assessment at scale article
2 parents c7b6cb8 + be7c45d commit 61cce11

File tree

3 files changed

+31
-5
lines changed

3 files changed

+31
-5
lines changed
210 KB
Loading

articles/update-manager/periodic-assessment-at-scale.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article shows how to manage update settings for your Windows a
44
ms.service: azure-update-manager
55
author: SnehaSudhirG
66
ms.author: sudhirsneha
7-
ms.date: 01/17/2024
7+
ms.date: 02/27/2024
88
ms.topic: conceptual
99
---
1010

@@ -25,6 +25,11 @@ This article describes how to enable Periodic Assessment for your machines at sc
2525

2626
You can monitor the compliance of resources under **Compliance** and remediation status under **Remediation** on the Azure Policy home page.
2727

28+
> [!NOTE]
29+
> Currently, Periodic assessment policies don’t support specialized, migrated, and restored images. However, they work for both marketplace and generalized gallery images. If you are facing failures during remediation see, [remediation failures for gallery images](troubleshoot.md#policy-remediation-tasks-are-failing-for-gallery-images-and-for-images-with-encrypted-disks) for more information.
30+
31+
32+
2833
## Enable Periodic Assessment for your Azure Arc-enabled machines by using Azure Policy
2934

3035
1. Go to **Policy** in the Azure portal and select **Authoring** > **Definitions**.

articles/update-manager/troubleshoot.md

Lines changed: 25 additions & 4 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: 02/21/2024
5+
ms.date: 02/27/2024
66
ms.topic: conceptual
77
ms.author: sudhirsneha
88
author: SnehaSudhirG
@@ -16,7 +16,10 @@ This article describes the errors that might occur when you deploy or use Azure
1616

1717
The following troubleshooting steps apply to the Azure virtual machines (VMs) related to the patch extension on Windows and Linux machines.
1818

19-
### Azure Linux VM
19+
20+
#### [Azure Virtual Machines](#tab/azure-machines)
21+
22+
##### Azure Linux VM
2023

2124
To verify if the Microsoft Azure Virtual Machine agent (VM agent) is running and has triggered appropriate actions on the machine and the sequence number for the autopatching request, check the agent log for more information in `/var/log/waagent.log`. Every autopatching request has a unique sequence number associated with it on the machine. Look for a log similar to `2021-01-20T16:57:00.607529Z INFO ExtHandler`.
2225

@@ -27,7 +30,7 @@ To review the logs related to all actions performed by the extension, check for
2730
* `<seq number>.core.log`: Contains information related to the patch actions. This information includes patches assessed and installed on the machine and any problems encountered in the process.
2831
* `<Date and Time>_<Handler action>.ext.log`: There's a wrapper above the patch action, which is used to manage the extension and invoke specific patch operation. This log contains information about the wrapper. For autopatching, the log `<Date and Time>_Enable.ext.log` has information on whether the specific patch operation was invoked.
2932

30-
### Azure Windows VM
33+
##### Azure Windows VM
3134

3235
To verify if the VM agent is running and has triggered appropriate actions on the machine and the sequence number for the autopatching request, check the agent log for more information in `C:\WindowsAzure\Logs\AggregateStatus`. The package directory for the extension is `C:\Packages\Plugins\Microsoft.CPlat.Core.WindowsPatchExtension<version>`.
3336

@@ -36,7 +39,8 @@ To review the logs related to all actions performed by the extension, check for
3639
* `WindowsUpdateExtension.log`: Contains information related to the patch actions. This information includes patches assessed and installed on the machine and any problems encountered in the process.
3740
* `CommandExecution.log`: There's a wrapper above the patch action, which is used to manage the extension and invoke specific patch operation. This log contains information about the wrapper. For autopatching, the log has information on whether the specific patch operation was invoked.
3841

39-
### Azure Arc-enabled servers
42+
#### [Arc-enabled Servers](#tab/azure-arc)
43+
4044

4145
For Azure Arc-enabled servers, see [Troubleshoot VM extensions](../azure-arc/servers/troubleshoot-vm-extensions.md) for general troubleshooting steps.
4246

@@ -46,6 +50,23 @@ To review the logs related to all actions performed by the extension, on Windows
4650
* `cmd_execution_<numeric>_stdout.txt`: There's a wrapper above the patch action. It's used to manage the extension and invoke specific patch operation. This log contains information about the wrapper. For autopatching, the log has information on whether the specific patch operation was invoked.
4751
* `cmd_excution_<numeric>_stderr.txt`
4852

53+
---
54+
55+
## Policy remediation tasks are failing for gallery images and for images with encrypted disks
56+
57+
### Issue
58+
There are remediation failures for VMs which have a reference to the gallery image in the Virtual Machine mode. This is because it requires the read permission to the gallery image and it is currently not part of the Virtual Machine Contributor role.
59+
60+
:::image type="content" source="./media/troubleshoot/policy-remediation-failure-error.png" alt-text="Screenshot that shows the error code for the policy remediation failure. " lightbox="./media/troubleshoot/policy-remediation-failure-error.png":::
61+
62+
### Cause
63+
The Virtual Machine Contributor role doesn’t have enough permissions.
64+
65+
### Resolution
66+
- For all the new assignments, a recent change is introduced to provide **Contributor** role to the managed identity created during policy assignment for remediation. Going forward, this will be assigned for any new assignments.
67+
- For any previous assignments if you are experiencing failure of remediation tasks, we recommend that you manually assign the contributor role to the managed identity by following the steps listed under [Grant permissions to the managed identity through defined roles](../governance/policy/how-to/remediate-resources.md)
68+
- 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).
69+
4970

5071
### Unable to generate periodic assessment for Arc-enabled servers
5172

0 commit comments

Comments
 (0)