Skip to content

Commit a766931

Browse files
Merge pull request #262293 from johnmarco/jm-update-onboarding-options
Add VMware and SCVMM onboarding options
2 parents b0f20fb + bb8a159 commit a766931

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

articles/azure-arc/servers/deployment-options.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Azure Connected Machine agent deployment options
33
description: Learn about the different options to onboard machines to Azure Arc-enabled servers.
4-
ms.date: 05/04/2023
4+
ms.date: 01/03/2024
55
ms.topic: how-to
66
---
77

@@ -24,6 +24,8 @@ The following table highlights each method so that you can determine which works
2424
| At scale | [Connect machines with a Configuration Manager custom task sequence](onboard-configuration-manager-custom-task.md)
2525
| At scale | [Connect Windows machines using Group Policy](onboard-group-policy-powershell.md)
2626
| 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. |
27+
| At scale | [Connect your VMware vCenter server to Azure Arc by using the helper script](../vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md) if you're using VMware vCenter to manage your on-premises estate. |
28+
| At scale | [Connect your System Center Virtual Machine Manager management server to Azure Arc by using the helper script](../system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc.md) if you're using SCVMM to manage your on-premises estate. |
2729

2830
> [!IMPORTANT]
2931
> The Connected Machine agent cannot be installed on an Azure virtual machine. The install script will warn you and roll back if it detects the server is running in Azure.

articles/azure-arc/servers/prepare-extended-security-updates.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: How to prepare to deliver Extended Security Updates for Windows Server 2012 through Azure Arc
33
description: Learn how to prepare to deliver Extended Security Updates for Windows Server 2012 through Azure Arc.
4-
ms.date: 11/22/2023
4+
ms.date: 01/03/2024
55
ms.topic: conceptual
66
---
77

@@ -56,7 +56,7 @@ You must also download both the licensing package and servicing stack update (SS
5656

5757
### Deployment options
5858

59-
There are several at-scale onboarding options for Azure Arc-enabled servers, including running a [Custom Task Sequence](onboard-configuration-manager-custom-task.md) through Configuration Manager and deploying a [Scheduled Task through Group Policy](onboard-group-policy-powershell.md).
59+
There are several at-scale onboarding options for Azure Arc-enabled servers, including running a [Custom Task Sequence](onboard-configuration-manager-custom-task.md) through Configuration Manager and deploying a [Scheduled Task through Group Policy](onboard-group-policy-powershell.md). There are also at-scale ESU delivery options for [VMware vCenter managed VMs](../vmware-vsphere/deliver-extended-security-updates-for-vmware-vms-through-arc.md) and [SCVMM managed VMs](../system-center-virtual-machine-manager/deliver-esus-for-system-center-virtual-machine-manager-vms.md) through Azure Arc.
6060

6161
> [!NOTE]
6262
> Delivery of ESUs through Azure Arc to virtual machines running on Virtual Desktop Infrastructure (VDI) is not recommended. VDI systems should use Multiple Activation Keys (MAK) to apply ESUs. See [Access your Multiple Activation Key from the Microsoft 365 Admin Center](/windows-server/get-started/extended-security-updates-deploy) to learn more.

0 commit comments

Comments
 (0)