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: articles/automation/change-tracking/enable-vms-monitoring-agent.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Enable Azure Automation Change Tracking for single machine and multiple m
3
3
description: This article tells how to enable the Change Tracking feature for single machine and multiple machines at scale from the Azure portal.
4
4
services: automation
5
5
ms.subservice: change-inventory-management
6
-
ms.date: 10/10/2024
6
+
ms.date: 10/29/2024
7
7
ms.topic: how-to
8
8
ms.service: azure-automation
9
9
---
@@ -40,9 +40,10 @@ This section provides detailed procedure on how you can enable change tracking o
40
40
It will initiate the deployment and the notification appears on the top right corner of the screen.
41
41
42
42
:::image type="content" source="media/enable-vms-monitoring-agent/deployment-success-inline.png" alt-text="Screenshot showing the notification of deployment." lightbox="media/enable-vms-monitoring-agent/deployment-success-expanded.png":::
43
-
43
+
44
44
> [!NOTE]
45
-
> It usually takes up to two to three minutes to successfully onboard and enable the virtual machine(s). After you enable a virtual machine for change tracking, you can make changes to the files, registries, or software for the specific VM.
45
+
> - When you enable Change Tracking in the Azure portal using the Azure Monitoring Agent, the process automatically creates a Data Collection Rule (DCR). This rule will appear in the resource group with a name in the format ct-dcr-aaaaaaaaa. After the rule is created, add the required resources.
46
+
> - It usually takes up to two to three minutes to successfully onboard and enable the virtual machine(s). After you enable a virtual machine for change tracking, you can make changes to the files, registries, or software for the specific VM.
@@ -55,7 +56,7 @@ This section provides detailed procedure on how you can enable change tracking o
55
56
:::image type="content" source="media/enable-vms-monitoring-agent/select-change-tracking-multiple-vms-inline.png" alt-text="Screenshot showing how to select multiple virtual machines from the portal." lightbox="media/enable-vms-monitoring-agent/select-change-tracking-multiple-vms-expanded.png":::
56
57
57
58
> [!NOTE]
58
-
> You can select upto 250 virtual machines at a time to enable this feature.
59
+
> You can select up to 250 virtual machines at a time to enable this feature.
59
60
60
61
1. In **Enable Change Tracking** page, select the banner at the top of the page, **Click here to try new change tracking and inventory with Azure Monitoring Agent (AMA) experience**.
61
62
@@ -193,6 +194,9 @@ Using the Deploy if not exist (DINE) policy, you can enable Change tracking with
193
194
194
195
:::image type="content" source="media/enable-vms-monitoring-agent/deployment-confirmation.png" alt-text="Screenshot of deployment notification.":::
195
196
197
+
> [!NOTE]
198
+
> After creating the Data Collection Rule (DCR) using the Azure Monitoring Agent's change tracking schema, ensure that you don't add any Data Sources to this rule. This can cause Change Tracking and Inventory to fail. You must only add new Resources in this section.
199
+
196
200
## Next steps
197
201
198
202
- For details of working with the feature, see [Manage Change Tracking](../change-tracking/manage-change-tracking-monitoring-agent.md).
0 commit comments