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/prerequisites.md
+19-2Lines changed: 19 additions & 2 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: Connected Machine agent prerequisites
3
3
description: Learn about the prerequisites for installing the Connected Machine agent for Azure Arc-enabled servers.
4
-
ms.date: 11/18/2022
4
+
ms.date: 01/25/2023
5
5
ms.topic: conceptual
6
6
---
7
7
@@ -29,6 +29,7 @@ The following versions of the Windows and Linux operating system are officially
29
29
* Windows Server 2008 R2 SP1, 2012 R2, 2016, 2019, and 2022
30
30
* Both Desktop and Server Core experiences are supported
31
31
* Azure Editions are supported when running as a virtual machine on Azure Stack HCI
32
+
* Windows 10, 11 (see [client operating system guidance](#client-operating-system-guidance))
32
33
* Windows IoT Enterprise
33
34
* Azure Stack HCI
34
35
* Ubuntu 16.04, 18.04, 20.04, and 22.04 LTS
@@ -41,7 +42,7 @@ The following versions of the Windows and Linux operating system are officially
41
42
* Oracle Linux 7
42
43
43
44
> [!NOTE]
44
-
> On Linux, Azure Arc-enabled servers install several daemon processes. We only support using systemd to manage these processes. In some environments, systemd may not be installed or available, in which case Arc-enabled servers are not supported, even if the distribution is otherwise supported. These environments include **Windows Subsystem for Linux** (WSL) and most container-based systems, such as Kubernetes or Docker. The Azure Connected Machine agent can be installed on the node that runs the containers but not inside the containers themselves.
45
+
> On Linux, Azure Arc-enabled servers install several daemon processes. We only support using systemd to manage these processes. In some environments, systemd may not be installed or available, in which case Arc-enabled servers are not supported, even if the distribution is otherwise supported. These environments include Windows Subsystem for Linux (WSL) and most container-based systems, such as Kubernetes or Docker. The Azure Connected Machine agent can be installed on the node that runs the containers but not inside the containers themselves.
45
46
46
47
> [!WARNING]
47
48
> If the Linux hostname or Windows computer name uses a reserved word or trademark, attempting to register the connected machine with Azure will fail. For a list of reserved words, see [Resolve reserved resource name errors](../../azure-resource-manager/templates/error-reserved-resource-name.md).
@@ -52,6 +53,22 @@ The following versions of the Windows and Linux operating system are officially
52
53
> * The Dependency agent used by Azure Monitor VM insights
53
54
> * Azure Automation Update Management
54
55
56
+
### Client operating system guidance
57
+
58
+
The Azure Arc service and Azure Connected Machine Agent are supported on Windows 10 and 11 client operating systems only when those computers are being used in a server-like environment. That is, the computer should always be:
59
+
60
+
* Connected to the internet
61
+
* Connected to a power source
62
+
* Powered on
63
+
64
+
For example, a computer running Windows 11 that's responsible for digital signage, point-of-sale solutions, and general back office management tasks is a good candidate for Azure Arc. End-user productivity machines, such as a laptop which may go offline for long periods of time, shouldn't use Azure Arc and instead should consider [Microsoft Intune](/mem/intune) or [Microsoft Endpoint Configuration Manager](/mem/configmgr).
65
+
66
+
### Short-lived servers and virtual desktop infrastructure
67
+
68
+
It is not recommended to use Azure Arc on short-lived (ephemeral) servers or virtual desktop infrastructure (VDI) VMs. Azure Arc is designed for long-term management of servers and is not optimized for scenarios where you are regularly creating and deleting servers. For example, Azure Arc does not know if the agent is offline due to planned system maintenance or if the VM has been deleted, so it will not automatically clean up server resources. This could result in a conflict if a VM is re-created with the same name and tries connecting to Azure Arc, but a resource with the same name already exists.
69
+
70
+
[Azure Virtual Desktop on Azure Stack HCI](../../virtual-desktop/azure-stack-hci-overview.md) does not use short-lived VMs and supports running Azure Arc in the desktop VMs.
0 commit comments