|
| 1 | +--- |
| 2 | +title: Enable virtual hardware and VM CRUD capabilities in a machine with Arc agent installed |
| 3 | +description: Enable virtual hardware and VM CRUD capabilities in a machine with Arc agent installed |
| 4 | +ms.topic: how-to |
| 5 | +ms.date: 12/27/2023 |
| 6 | +ms.service: azure-arc |
| 7 | +ms.subservice: azure-arc-vmware-vsphere |
| 8 | +author: Farha-Bano |
| 9 | +ms.author: v-farhabano |
| 10 | +manager: jsuri |
| 11 | +ms.custom: |
| 12 | +--- |
| 13 | + |
| 14 | +# Enable virtual hardware and VM CRUD capabilities in a machine with Arc agent installed |
| 15 | + |
| 16 | +In this article, you learn how to enable virtual hardware management and VM CRUD operational ability on a VMware VM that has Arc agents installed via the Arc-enabled Servers route. |
| 17 | + |
| 18 | +>[!IMPORTANT] |
| 19 | +> This article is applicable only if you've installed Arc agents directly in VMware machines before onboarding to Azure Arc-enabled VMware vSphere by deploying Arc resource bridge. |
| 20 | +
|
| 21 | +## Prerequisites |
| 22 | + |
| 23 | +- An Azure subscription and resource group where you have *Azure Arc VMware Administrator role*. |
| 24 | +- Your vCenter instance must be [onboarded](quick-start-connect-vcenter-to-arc-using-script.md) to Azure Arc. |
| 25 | + |
| 26 | +## Enable virtual hardware management and self-service access to vCenter VMs with Arc agent installed |
| 27 | + |
| 28 | +1. From your browser, go to [Azure portal](https://portal.azure.com/). |
| 29 | + |
| 30 | +1. Navigate to the Virtual machines inventory page of your vCenter. <br> |
| 31 | + The virtual machines that have Arc agent installed via the Arc-enabled Servers route will have **Link to vCenter** status under virtual hardware management. |
| 32 | + |
| 33 | +1. Select **Link to vCenter** to view the pane with the list of all the machines under vCenter with Arc agent installed but not linked to the vCenter in Azure Arc. |
| 34 | + |
| 35 | +1. Choose all the machines that need to be enabled in Azure, and select **Link** to link the machines to vCenter. |
| 36 | + |
| 37 | +1. After you link to vCenter, the virtual hardware status will reflect as **Enabled for all the VMs**, and you can perform [virtual hardware operations](perform-vm-ops-through-azure.md). |
| 38 | + |
| 39 | +### Known issue |
| 40 | + |
| 41 | +During the first scan of the vCenter inventory after onboarding to Azure Arc-enabled VMware vSphere, Arc-enabled Servers machines will be discovered under vCenter inventory. If the Arc-enabled Server machines aren't discovered and you try to perform the **Enable in Azure** operation, you'll encounter the following error:<br> |
| 42 | + |
| 43 | + |
| 44 | +``` |
| 45 | +A machine '/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXXX/resourceGroups/rg-contoso/providers/Microsoft.HybridCompute/machines/testVM1' already exists with the specified virtual machine MoRefId: 'vm-4441'. The existing machine resource can be extended with private cloud capabilities by creating the VirtualMachineInstance resource under it. |
| 46 | +``` |
| 47 | + |
| 48 | +When you encounter this error message, try performing the **Link to vCenter** operation again after a few minutes (5-10 minutes). Alternatively, you can use the following Azure CLI command to link an existing Arc-enabled Server machine to vCenter:<br> |
| 49 | + |
| 50 | + |
| 51 | +```azurecli-interactive |
| 52 | +az connectedvmware vm create --subscription XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXXX --location eastus --resource-group rg-contoso --custom-location /providers/microsoft.extendedlocation/customlocations/contoso-cl --name contoso-hcrp-machine-name --inventory-item /subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXXX/resourceGroups/contoso-rg/providers/Microsoft.ConnectedVMwarevSphere/VCenters/contoso-vcenter/InventoryItems/vm-142359 |
| 53 | +``` |
| 54 | + |
| 55 | +## Next steps |
| 56 | + |
| 57 | +[Set up and manage self-service access to VMware resources through Azure RBAC](setup-and-manage-self-service-access.md). |
| 58 | + |
0 commit comments