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/azure-arc/servers/agent-overview.md
+18-6Lines changed: 18 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Overview of the Azure Connected Machine agent
3
3
description: This article provides a detailed overview of the Azure Arc-enabled servers agent available, which supports monitoring virtual machines hosted in hybrid environments.
4
-
ms.date: 03/01/2022
4
+
ms.date: 03/03/2022
5
5
ms.topic: conceptual
6
6
ms.custom: devx-track-azurepowershell
7
7
---
@@ -223,9 +223,6 @@ Connecting machines in your hybrid environment directly with Azure can be accomp
223
223
| At scale | [Connect machines with a Configuration Manager custom task sequence](onboard-configuration-manager-custom-task.md)
224
224
| At scale |[Connect machines from Automation Update Management](onboard-update-management-machines.md) to create a service principal that installs and configures the agent for multiple machines managed with Azure Automation Update Management to connect machines non-interactively. |
225
225
226
-
227
-
228
-
229
226
> [!IMPORTANT]
230
227
> The Connected Machine agent cannot be installed on an Azure Windows virtual machine. If you attempt to, the installation detects this and rolls back.
231
228
@@ -239,7 +236,7 @@ The Connected Machine agent for Windows can be installed by using one of the fol
239
236
* Manually by running the Windows Installer package `AzureConnectedMachineAgent.msi` from the Command shell.
240
237
* From a PowerShell session using a scripted method.
241
238
242
-
Installing, updating, and removing the Connected Machine agent will not require you to restart your server.
239
+
Installing, upgrading, or removing the Connected Machine agent will not require you to restart your server.
243
240
244
241
After installing the Connected Machine agent for Windows, the following system-wide configuration changes are applied.
245
242
@@ -261,6 +258,21 @@ After installing the Connected Machine agent for Windows, the following system-w
261
258
|GCArcService |Guest configuration Arc Service |gc_service |Monitors the desired state configuration of the machine.|
262
259
|ExtensionService |Guest configuration Extension Service | gc_service |Installs the required extensions targeting the machine.|
263
260
261
+
* The following virtual service account is created during agent installation.
262
+
263
+
| Virtual Account | Description |
264
+
|------------------|---------|
265
+
| NT SERVICE\\himds | Unprivileged account used to run the Hybrid Instance Metadata Service. |
266
+
267
+
> [!TIP]
268
+
> 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.
269
+
270
+
* The following local security group is created during agent installation.
271
+
272
+
| Security group name | Description |
273
+
|---------------------|-------------|
274
+
| Hybrid agent extension applications | Members of this security group can request Azure Active Directory tokens for the system-assigned managed identity |
275
+
264
276
* The following environmental variables are created during agent installation.
265
277
266
278
|Name |Default value |Description |
@@ -290,7 +302,7 @@ After installing the Connected Machine agent for Windows, the following system-w
290
302
291
303
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).
292
304
293
-
Installing, updating, and removing the Connected Machine agent will not require you to restart your server.
305
+
Installing, upgrading, or removing the Connected Machine agent will not require you to restart your server.
294
306
295
307
After installing the Connected Machine agent for Linux, the following system-wide configuration changes are applied.
Copy file name to clipboardExpand all lines: articles/azure-arc/servers/manage-agent.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ To clear a configuration property's value, run the following command:
105
105
106
106
The Azure Connected Machine agent is updated regularly to address bug fixes, stability enhancements, and new functionality. [Azure Advisor](../../advisor/advisor-overview.md) identifies resources that are not using the latest version of machine agent and recommends that you upgrade to the latest version. It will notify you when you select the Azure Arc-enabled server by presenting a banner on the **Overview** page or when you access Advisor through the Azure portal.
107
107
108
-
The Azure Connected Machine agent for Windows and Linux can be upgraded to the latest release manually or automatically depending on your requirements. Installing, upgrading, and uninstalling the Azure Connected Machine Agent will not require you to restart your server.
108
+
The Azure Connected Machine agent for Windows and Linux can be upgraded to the latest release manually or automatically depending on your requirements. Installing, upgrading, or uninstalling the Azure Connected Machine Agent will not require you to restart your server.
109
109
110
110
The following table describes the methods supported to perform the agent upgrade.
Copy file name to clipboardExpand all lines: articles/azure-arc/servers/security-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,11 +30,11 @@ To manage the Azure Connected Machine agent (azcmagent) on Windows, your user ac
30
30
31
31
The Azure Connected Machine agent is composed of three services, which run on your machine.
32
32
33
-
* The Hybrid Instance Metadata Service (himds) service is responsible for all core functionality of Arc. This includes sending heartbeats to Azure, exposing a local instance metadata service for other apps to learn about the machine’s Azure resource ID, and retrieve Azure AD tokens to authenticate to other Azure services. This service runs as an unprivileged virtual service account on Windows, and as the **himds** user on Linux.
33
+
* The Hybrid Instance Metadata Service (himds) service is responsible for all core functionality of Arc. This includes sending heartbeats to Azure, exposing a local instance metadata service for other apps to learn about the machine’s Azure resource ID, and retrieve Azure AD tokens to authenticate to other Azure services. This service runs as an unprivileged virtual service account (NT SERVICE\\himds) on Windows, and as the **himds** user on Linux. The virtual service account requires the Log on as a Service right on Windows.
34
34
35
35
* The Guest Configuration service (GCService) is responsible for evaluating Azure Policy on the machine.
36
36
37
-
* The Guest Configuration Extension service (ExtensionService) is responsible for installing, updating, and deleting extensions (agents, scripts, or other software) on the machine.
37
+
* The Guest Configuration Extension service (ExtensionService) is responsible for installing, upgrading, and deleting extensions (agents, scripts, or other software) on the machine.
38
38
39
39
The guest configuration and extension services run as Local System on Windows, and as root on Linux.
0 commit comments