Skip to content

Commit 803c411

Browse files
author
Ryan Willis
committed
Added initial VDI and client OS details
1 parent d4b0056 commit 803c411

File tree

1 file changed

+19
-2
lines changed

1 file changed

+19
-2
lines changed

articles/azure-arc/servers/prerequisites.md

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Connected Machine agent prerequisites
33
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
55
ms.topic: conceptual
66
---
77

@@ -29,6 +29,7 @@ The following versions of the Windows and Linux operating system are officially
2929
* Windows Server 2008 R2 SP1, 2012 R2, 2016, 2019, and 2022
3030
* Both Desktop and Server Core experiences are supported
3131
* 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))
3233
* Windows IoT Enterprise
3334
* Azure Stack HCI
3435
* 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
4142
* Oracle Linux 7
4243

4344
> [!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.
4546
4647
> [!WARNING]
4748
> 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
5253
> * The Dependency agent used by Azure Monitor VM insights
5354
> * Azure Automation Update Management
5455
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.
71+
5572
## Software requirements
5673

5774
Windows operating systems:

0 commit comments

Comments
 (0)