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
The Azure Connected Machine agent package contains several logical components, which are bundled together:
17
+
The Azure Connected Machine agent package contains several logical components bundled together:
18
18
19
19
* The Hybrid Instance Metadata service (HIMDS) manages the connection to Azure and the connected machine's Azure identity.
20
20
@@ -26,7 +26,7 @@ The Azure Connected Machine agent package contains several logical components, w
26
26
* Guest assignment is stored locally for 14 days. Within the 14-day period, if the Connected Machine agent reconnects to the service, policy assignments are reapplied.
27
27
* Assignments are deleted after 14 days, and are not reassigned to the machine after the 14-day period.
28
28
29
-
* The Extension agent manages VM extensions, including install, uninstall, and upgrade. Extensions are downloaded from Azure and copied to the `%SystemDrive%\%ProgramFiles%\AzureConnectedMachineAgent\ExtensionService\downloads` folder on Windows, and to `/opt/GC_Ext/downloads` on Linux. On Windows, the extension is installed to the following path `%SystemDrive%\Packages\Plugins\<extension>`, and on Linux the extension is installed to `/var/lib/waagent/<extension>`.
29
+
* The Extension agent manages VM extensions, including install, uninstall, and upgrade. Azure downloads extensions and copies them to the `%SystemDrive%\%ProgramFiles%\AzureConnectedMachineAgent\ExtensionService\downloads` folder on Windows, and to `/opt/GC_Ext/downloads` on Linux. On Windows, the extension installs to the following path `%SystemDrive%\Packages\Plugins\<extension>`, and on Linux the extension installs to `/var/lib/waagent/<extension>`.
30
30
31
31
>[!NOTE]
32
32
> The [Azure Monitor agent](../../azure-monitor/agents/azure-monitor-agent-overview.md) (AMA) is a separate agent that collects monitoring data, and it does not replace the Connected Machine agent; the AMA only replaces the Log Analytics agent, Diagnostics extension, and Telegraf agent for both Windows and Linux machines.
@@ -37,10 +37,10 @@ The following information describes the directories and user accounts used by th
37
37
38
38
### Windows agent installation details
39
39
40
-
The Windows agent is distributed as a Windows Installer package (MSI) and can be downloaded from the [Microsoft Download Center](https://aka.ms/AzureConnectedMachineAgent).
41
-
After installing the Connected Machine agent for Windows, the following system-wide configuration changes are applied.
40
+
The Windows agent is distributed as a Windows Installer package (MSI). Download the Windows agent from the [Microsoft Download Center](https://aka.ms/AzureConnectedMachineAgent).
41
+
Installing the Connected Machine agent for Window applies the following system-wide configuration changes:
42
42
43
-
* The following installation folders are created during setup.
43
+
* The installation process creates the following folders during setup.
44
44
45
45
| Directory | Description |
46
46
|-----------|-------------|
@@ -51,15 +51,15 @@ After installing the Connected Machine agent for Windows, the following system-w
51
51
| %ProgramData%\GuestConfig | Extension package downloads, guest configuration (policy) definition downloads, and logs for the extension and guest configuration services.|
| himds | Azure Hybrid Instance Metadata Service | himds | Synchronizes metadata with Azure and hosts a local REST API for extensions and applications to access the metadata and request Azure Active Directory managed identity tokens |
59
59
| GCArcService | Guest configuration Arc Service | gc_service | Audits and enforces Azure guest configuration policies on the machine. |
60
60
| ExtensionService | Guest configuration Extension Service | gc_service | Installs, updates, and manages extensions on the machine. |
61
61
62
-
*The following virtual service account is created during agent installation.
62
+
*Agent installation creates the following virtual service account.
63
63
64
64
| Virtual Account | Description |
65
65
|------------------|-------------|
@@ -68,20 +68,20 @@ After installing the Connected Machine agent for Windows, the following system-w
68
68
> [!TIP]
69
69
> This account requires the "Log on as a service" right. This right is automatically granted during agent installation, but if your organization configures user rights assignments with Group Policy, you may need to adjust your Group Policy Object to grant the right to "NT SERVICE\\himds" or "NT SERVICE\\ALL SERVICES" to allow the agent to function.
70
70
71
-
*The following local security group is created during agent installation.
71
+
*Agent installation creates the following local security group.
72
72
73
73
| Security group name | Description |
74
74
|---------------------|-------------|
75
75
| Hybrid agent extension applications | Members of this security group can request Azure Active Directory tokens for the system-assigned managed identity |
76
76
77
-
*The following environmental variables are created during agent installation.
77
+
*Agent installation creates the following environmental variables
* There are several log files available for troubleshooting. They are described in the following table.
84
+
* There are several log files available for troubleshooting, described in the following table.
85
85
86
86
| Log | Description |
87
87
|-----|-------------|
@@ -91,9 +91,9 @@ After installing the Connected Machine agent for Windows, the following system-w
91
91
| %ProgramData%\GuestConfig\ext_mgr_logs\gc_ext.log | Records details about extension manager activity (extension install, uninstall, and upgrade events). |
92
92
| %ProgramData%\GuestConfig\extension_logs | Directory containing logs for individual extensions. |
93
93
94
-
* The local security group **Hybrid agent extension applications** is created.
94
+
* The process creates the local security group **Hybrid agent extension applications**.
95
95
96
-
*During uninstall of the agent, the following artifacts are not removed.
96
+
*After uninstalling the agent, the following artifacts remain.
97
97
98
98
* %ProgramData%\AzureConnectedMachineAgent\Log
99
99
* %ProgramData%\AzureConnectedMachineAgent
@@ -102,13 +102,13 @@ After installing the Connected Machine agent for Windows, the following system-w
102
102
103
103
### Linux agent installation details
104
104
105
-
The Connected Machine agent for Linux is provided in the preferred package format for the distribution (.RPM or .DEB) that's hosted in the Microsoft [package repository](https://packages.microsoft.com/). The agent is installed and configured with the shell script bundle [Install_linux_azcmagent.sh](https://aka.ms/azcmagent).
105
+
The preferred package format for the distribution (.RPM or .DEB) that's hosted in the Microsoft [package repository](https://packages.microsoft.com/) provides the Connected Machine agent for Linux. The shell script bundle [Install_linux_azcmagent.sh](https://aka.ms/azcmagent) installs and configurs the agent.
106
106
107
-
Installing, upgrading, and removing the Connected Machine agent will not require you to restart your server.
107
+
Installing, upgrading, and removing the Connected Machine agent is not required after server restart.
108
108
109
-
After installing the Connected Machine agent for Linux, the following system-wide configuration changes are applied.
109
+
Installing the Connected Machine agent for Linux applies the following system-wide configuration changes.
110
110
111
-
*The following installation folders are created during setup.
111
+
*Setup creates the following installation folders.
112
112
113
113
| Directory | Description |
114
114
|-----------|-------------|
@@ -118,15 +118,15 @@ After installing the Connected Machine agent for Linux, the following system-wid
118
118
| /var/opt/azcmagent/ | Configuration, log and identity token files for azcmagent CLI and instance metadata service.|
119
119
| /var/lib/GuestConfig/ | Extension package downloads, guest configuration (policy) definition downloads, and logs for the extension and guest configuration services.|
120
120
121
-
*The following daemons are created on the target machine during installation of the agent.
121
+
*Installing the agent creates the following daemons.
122
122
123
123
| Service name | Display name | Process name | Description |
| himdsd.service | Azure Connected Machine Agent Service | himds | This service implements the Hybrid Instance Metadata service (IMDS) to manage the connection to Azure and the connected machine's Azure identity.|
126
126
| gcad.service | GC Arc Service | gc_linux_service | Audits and enforces Azure guest configuration policies on the machine. |
127
127
| extd.service | Extension Service | gc_linux_service | Installs, updates, and manages extensions on the machine. |
128
128
129
-
* There are several log files available for troubleshooting. They are described in the following table.
129
+
* There are several log files available for troubleshooting, described in the following table.
130
130
131
131
| Log | Description |
132
132
|-----|-------------|
@@ -136,14 +136,14 @@ After installing the Connected Machine agent for Linux, the following system-wid
136
136
| /var/lib/GuestConfig/ext_mgr_logs | Records details about extension manager activity (extension install, uninstall, and upgrade events). |
137
137
| /var/lib/GuestConfig/extension_logs | Directory containing logs for individual extensions. |
138
138
139
-
*The following environment variables are created during agent installation. These variables are set in `/lib/systemd/system.conf.d/azcmagent.conf`.
139
+
*Agent installation creates the following environment variables, set in `/lib/systemd/system.conf.d/azcmagent.conf`.
*During uninstall of the agent, the following artifacts are not removed.
146
+
*After uninstalling the agent, the following artifacts remain.
147
147
148
148
* /var/opt/azcmagent
149
149
* /var/lib/GuestConfig
@@ -152,14 +152,15 @@ After installing the Connected Machine agent for Linux, the following system-wid
152
152
153
153
The Azure Connected Machine agent is designed to manage agent and system resource consumption. The agent approaches resource governance under the following conditions:
154
154
155
-
* The Guest Configuration agent is limited to use up to 5% of the CPU to evaluate policies.
156
-
* The Extension Service agent is limited to use up to 5% of the CPU to install, upgrade, run, and delete extensions. The following exceptions apply:
155
+
* The Guest Configuration agent can use up to 5% of the CPU to evaluate policies.
156
+
* The Extension Service agent can use up to 5% of the CPU to install, upgrade, run, and delete extensions. The following exceptions apply:
157
157
158
-
* If the extension installs background services that run independent of Azure Arc, such as the Microsoft Monitoring Agent, those services will not be subject to the resource governance constraints listed above.
159
-
* The Log Analytics agent and Azure Monitor Agent are allowed to use up to 60% of the CPU during their install/upgrade/uninstall operations on Red Hat Linux, CentOS, and other enterprise Linux variants. The limit is higher for this combination of extensions and operating systems to accommodate the performance impact of [SELinux](https://www.redhat.com/en/topics/linux/what-is-selinux) on these systems.
158
+
* If the extension installs background services that run independent of Azure Arc, such as the Microsoft Monitoring Agent, those services are not subject to the resource governance constraints listed above.
159
+
* The Log Analytics agent and Azure Monitor Agent can use up to 60% of the CPU during their install/upgrade/uninstall operations on Red Hat Linux, CentOS, and other enterprise Linux variants. The limit is higher for this combination of extensions and operating systems to accommodate the performance impact of [SELinux](https://www.redhat.com/en/topics/linux/what-is-selinux) on these systems.
160
160
* The Azure Monitor Agent can use up to 30% of the CPU during normal operations.
161
161
* The Linux OS Update Extension (used by Azure Update Management Center) can use up to 30% of the CPU to patch the server.
162
162
* The Microsoft Defender for Endpoint extension can use up to 30% of the CPU during installation, upgrades, and removal operations.
163
+
* The Microsoft Sentinel DNS extension can use up to 30% of the CPU to collect logs from DNS servers
163
164
164
165
## Instance metadata
165
166
@@ -195,7 +196,7 @@ Metadata information about a connected machine is collected after the Connected
195
196
* Service accounts
196
197
* Zone
197
198
198
-
The following metadata information is requested by the agent from Azure:
199
+
The agent requests the following metadata information from Azure:
199
200
200
201
* Resource location (region)
201
202
* Virtual machine ID
@@ -209,7 +210,7 @@ The following metadata information is requested by the agent from Azure:
209
210
210
211
## Deployment options and requirements
211
212
212
-
To deploy the agent and connect a machine, certain [prerequisites](prerequisites.md) must be met. There are also [networking requirements](network-requirements.md) to be aware of.
213
+
Agent deployment and machine connection requires certain [prerequisites](prerequisites.md). There are also [networking requirements](network-requirements.md) to be aware of.
213
214
214
215
We provide several options for deploying the agent. For more information, see [Plan for deployment](plan-at-scale-deployment.md) and [Deployment options](deployment-options.md).
0 commit comments