Muokkaa

Jaa

Manage Arc VMs on Azure Local

  • Artikkeli

Applies to: Azure Local, version 23H2

This article describes how to manage Arc virtual machines (VMs) running on Azure Local, version 23H2. The procedures to enable guest management, start, stop, restart, pause, save, or delete an Arc VM, are detailed.

Prerequisites

Before you begin, make sure to complete the following prerequisites:

  1. Make sure you have access to an Azure Local instance that is deployed and registered. During the deployment, an Arc Resource Bridge and a custom location are also created.

    Go to the resource group in Azure. You can see the custom location and Azure Arc Resource Bridge created for your Azure Local. Make a note of the subscription, resource group, and the custom location as you use these later in this scenario.

  2. Make sure you have one or more Arc VMs running on your Azure Local. For more information, see Create Arc VMs on Azure Local.

Enable guest management

After you created a VM, you would want to enable guest management on that VM.

There are two agents that are important to understand in the context of guest management - a VM guest agent and an Azure Connected Machine agent. Every Arc VM created via Azure portal or Azure CLI is provisioned with a guest agent (also referred to as the mocguestagent) on it.

When you enable guest management on an Arc VM, the guest agent installs the Azure Connected Machine agent. The Azure Connected Machine agent enables you to manage Azure Arc VM extensions on your VM.

Here are some key considerations for enabling guest management on a VM after provisioning it:

  • Make sure that your Azure Local is running 2311 or later.
  • Enabling guest management after VM provisioning isn't supported for Windows Server 2012 and Windows Server 2012 R2.
  • The steps to enable guest management differ based on whether a guest agent is running on your Arc VM.

Verify if guest agent is running

  1. To verify whether the guest agent is running on the Arc VM, connect to the machine.

  2. Run the following command:

    az stack-hci-vm show --name "<VM name>" --resource-group "<Resource group name>"

    Here's a snippet of the sample output that indicates that the guest agent is running. Look for statuses under the vmAgent in the output.

    "instanceView": {
  "vmAgent": {
    "statuses": [
      {
        "code": "ProvisioningState/succeeded",
        "displayStatus": "Connected",
        "level": "Info",
        "message": "Successfully established connection with mocguestagent",
        "time": "2024-01-13T00:57:39Z"
      },
      {
        "code": "ProvisioningState/succeeded",
        "displayStatus": "Connected",
        "level": "Info",
        "message": "New mocguestagent version detected 'v0.13.0-3-gd13b4794",
        "time": "2024-01-13T00:57:39Z"
      }
    ],
    "vmConfigAgentVersion": "v0.13.0-3-gd13b4794"
  }
}

    The guest agent is running:

    • When statuses indicate code as ProvisioningState/succeeded and the displayStatus as Connected.
    • If running an older version, the statuses would indicate code as OK and the displayStatus as Active

If your statuses do not match the above output, follow the steps in Enable guest management when the guest agent is not running.

Enable guest management on a VM with guest agent running

To enable guest management on an Arc VM that has guest agent running, run the following command:

az stack-hci-vm update --name "mylocal-vm" --enable-agent true --resource-group "mylocal-rg"

Guest management is enabled by setting the enable-agent parameter to true. Guest management should take a few minutes to get enabled.

Follow the steps to verify that the guest management is enabled in the Azure portal.

Enable guest management on a VM when guest agent is not running

There are two scenarios when the guest agent is not running - when the statuses is connecting and when the statuses are blank. Each of these scenarios and the corresponding steps are described in the following sections.

Status displayed as connecting

Your status shows as connecting. Here's a sample output snippet indicating the requisite status.

"instanceView": {
      "vmAgent": {
        "statuses": [
          {
            "code": "ProvisioningState/InProgress",
            "displayStatus": "Connecting",
            "level": "Info",
            "message": "Waiting for connection with mocguestagent",
            "time": "2024-01-19T01:41:15Z"
          }
        ]
      }
    },

The guest agent is not running when:

  • The guest agent is not running when statuses indicate code as ProvisioningState/InProgress and the displayStatus as Connecting.
  • If running an older version, the statuses would indicate code as OK, the displayStatus as Activeand message as Successfully started HyperV listener.

Follow these steps:

  1. Connect to the VM using the OS specific steps. Run PowerShell as administrator.

  2. Run one of the following commands to enable the guest agent on your VM based on the OS type:

    Linux:

    sudo -- sh -c 'mkdir /mociso && mount -L mocguestagentprov /mociso && bash /mociso/install.sh && umount /mociso && rm -df /mociso && eject LABEL=mocguestagentprov'

    Windows:

    $d=Get-Volume -FileSystemLabel mocguestagentprov;$p=Join-Path ($d.DriveLetter+':\') 'install.ps1';powershell $p

    Here's a sample output for a Linux VM that shows the guest agent is successfully installed.

    Screenshot showing that the guest agent is successfully enabled on the VM.

  3. Connect to one of the machines. Run the following command to enable guest management.

    az stack-hci-vm update --name "mylocal-vm" --enable-agent true --resource-group "mylocal-rg"

Follow the steps to verify that the guest management is enabled in the Azure portal.

Status displayed as null

Your status shows as null. This indicates the required iso for guest agent is missing. Here's a sample output snippet indicating the null status.

"instanceView": {
      "vmAgent": {
        "statuses": []
      }
    },

Follow these steps:

  1. Connect to a machine.

  2. Run the following command:

    az stack-hci-vm update --name "<VM Name>" --resource-group "<Resource group name>" --enable-vm-config-agent true

    The enable-vm-config-agent parameter mounts the required iso for the guest agent.

  3. Wait a few minutes and rerun the az stack-hci-vm show command. When the status shows as connecting, follow the steps in Status displayed as connecting.

Verify guest management is enabled in the Azure portal

  1. Go to the Azure portal.

  2. Navigate to Your Azure Local > Virtual machines and then select the VM on which you enabled the guest management.

  3. In the Overview page, on the Properties tab in the right pane, go to Configuration. The Guest management should show as Enabled (Connected).

    Screenshot showing how to Create a VM using Windows VM image.

View VM properties

Follow these steps in the Azure portal of your Azure Local to view VM properties.

  1. Go to the Azure Local resource and then go to Virtual machines.

  2. In the right pane, from the list of virtual machines, select the name of the VM whose properties you wish to view.

    Screenshot of VM selected from the list of VMs.

  3. On the Overview page, go to the right pane and then go to the Properties tab. You can view the properties of your VM.

    Screenshot of properties of the selected Arc VM.

Start a VM

Follow these steps in the Azure portal of your Azure Local to start a VM.

  1. Go to the Azure Local resource and then go to Virtual machines.

  2. In the right pane, from the list of virtual machines, select a VM that isn't running and you wish to start.

  3. On the Overview page for the VM, from the top command bar in the right pane, select Start, then select Yes.

  4. Verify the VM has started.

    Screenshot of select + start VM.

Stop a VM

Follow these steps in the Azure portal of your Azure Local to stop a VM.

  1. Go to the Azure Local resource and then go to Virtual machines.

  2. In the right pane, from the list of virtual machines, select a VM that is running and you wish to stop.

  3. On the Overview page for the VM, from the top command bar in the right pane, select Stop, then select Yes.

  4. Verify the VM has stopped.

    Screenshot of select + stop VM.

Restart a VM

Follow these steps in the Azure portal of your Azure Local to restart a VM.

  1. Go to the Azure Local resource and then go to Virtual machines.

  2. In the right pane, from the list of virtual machines, select a VM that is stopped and you wish to restart.

  3. On the Overview page for the VM, from the top command bar in the right pane, select Restart, then select Yes.

  4. Verify the VM has restarted.

    Screenshot of select + restart VM.

Pause a VM

Pausing the VMs is useful to save the compute resources when you are not using the VMs. Pausing a VM stops any CPU activity. You can only pause running VMs. Once paused, you can resume the VM later.

  1. Connect to a machine on your system.

  2. To pause the VM, run the following PowerShell cmdlet:

    #Set input parameters

$rg = "<Resource group name>"
$vmName = "<VM name>"

#Pause the VM

az stack-hci-vm pause --name $vmName --resource-group $rg

    The parameters used for this cmdlet are as follows:

    Parameter Description
    name Name of the virtual machine.
    resource-group Name of resource group. You can configure the default group using az configure --defaults group=<name>.
    subscription Name or ID of subscription. You can configure the default subscription using az account set -s NAME_OR_ID.

  3. Check the VM status to verify that the VM is paused.

    #Check the VM status

az stack-hci-vm show --name $vmName --resource-group $rg

  4. Start the VM to resume the VM from the paused state. Verify that the VM is running.

    #Start the VM

az stack-hci-vm start --name $vmName --resource-group $rg

    Example output

    Expand this section to see an example output. 
    
#Set parameters

[v-host1]: PS C:\Users\HCIDeploymentUser> $rg = "<Resource group name>"    
[v-host1]: PS C:\Users\HCIDeploymentUser> $vmName = "<VM name>"

#Pause the VM

[v-host1]: PS C:\Users\HCIDeploymentUser> az stack-hci-vm pause --name $vmName --resource-group $rg

#Show the current state of the VM
[v-host1]: PS C:\Users\HCIDeploymentUser> az stack-hci-vm show -g $rg --name $vmName
{
  "attestationStatus": null,
  "virtualmachineinstance": {
    "extendedLocation": {
      "name": "/subscriptions/<Subscription ID>/resourcegroups/<Resource group name>/providers/Microsoft.ExtendedLocation/customLocations/s-cluster-customlocation",
      "type": "CustomLocation"
    },
    "id": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/testvm001/providers/Microsoft.AzureStackHCI/virtualMachineInstances/default",
    "identity": null,
    "name": "default",
    "properties": {
      "guestAgentInstallStatus": null,
      "hardwareProfile": {
        "dynamicMemoryConfig": {
          "maximumMemoryMb": null,
          "minimumMemoryMb": null,
          "targetMemoryBuffer": null
        },
        "memoryMb": 2000,
        "processors": 2,
        "vmSize": "Custom"
      },
      "httpProxyConfig": null,
      "instanceView": {
        "vmAgent": {
          "statuses": [
            {
              "code": "ProvisioningState/succeeded",
              "displayStatus": "Connected",
              "level": "Info",
              "message": "Connection with mocguestagent was successfully reestablished",
              "time": "2024-06-24T16:30:05+00:00"
            },
          ],
          "vmConfigAgentVersion": "v0.18.0-4-gd54376b0"
        }
      },
      "networkProfile": {
        "networkInterfaces": []
      },
      "osProfile": {
        "adminPassword": null,
        "adminUsername": "azureuser",
        "computerName": "testvm001",
        "linuxConfiguration": {
          "disablePasswordAuthentication": false,
          "provisionVmAgent": false,
          "provisionVmConfigAgent": true,
          "ssh": {
            "publicKeys": null
          }
        },
        "windowsConfiguration": {
          "enableAutomaticUpdates": null,
          "provisionVmAgent": false,
          "provisionVmConfigAgent": true,
          "ssh": {
            "publicKeys": null
          },
          "timeZone": null
        }
      },
      "provisioningState": "Succeeded",
      "resourceUid": null,
      "securityProfile": {
        "enableTpm": false,
        "securityType": null,
        "uefiSettings": {
          "secureBootEnabled": true
        }
      },
      "status": {
        "errorCode": "",
        "errorMessage": "",
        "powerState": "Paused",
        "provisioningStatus": null
      },
      "storageProfile": {
        "dataDisks": [],
        "imageReference": {
          "id": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.AzureStackHCI/galleryImages/WinImage-26tdJUIS",
          "resourceGroup": "<Resource group name>"
        },
        "osDisk": {
          "id": null,
          "osType": "Windows"
        },
        "vmConfigStoragePathId": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.AzureStackHCI/storageContainers/UserStorage2-guid"
      },
      "vmId": "<guid>"
    },
    "resourceGroup": "<Resource group name>",
    "systemData": {
      "createdAt": "2024-06-24T01:29:06.594266+00:00",
      "createdBy": "7d6ffe2f-dac5-4e74-9bf2-4830cf7f4668",
      "createdByType": "Application",
      "lastModifiedAt": "2024-06-24T16:41:27.166668+00:00",
      "lastModifiedBy": "319f651f-7ddb-4fc6-9857-7aef9250bd05",
      "lastModifiedByType": "Application"
    },
    "type": "microsoft.azurestackhci/virtualmachineinstances"
  }
}

#Start the VM after it was paused. 

[v-host1]: PS C:\Users\HCIDeploymentUser> az stack-hci-vm start --name $vmName --resource-group $rg
Inside _start_initial/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/testvm0012024-02-01-preview/https://management.azure.com/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/testvm001/providers/Microsoft.AzureStackHCI/virtualMachineInstances/d
efault/start?api-version=2024-02-01-preview

#Show the current state of the VM. The VM should be running.

[v-host1]: PS C:\Users\HCIDeploymentUser> az stack-hci-vm show -g $rg --name $vmName
{
  "attestationStatus": null,
  "virtualmachineinstance": {
    "extendedLocation": {
      "name": "/subscriptions/<Subscription ID>/resourcegroups/<Resource group name>/providers/Microsoft.ExtendedLocation/customLocations/s-cluster-customlocation",
      "type": "CustomLocation"
    },
    "id": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/testvm001/providers/Microsoft.AzureStackHCI/virtualMachineInstances/default",
    "identity": null,
    "name": "default",
    "properties": {
      "guestAgentInstallStatus": null,
      "hardwareProfile": {
        "dynamicMemoryConfig": {
          "maximumMemoryMb": null,
          "minimumMemoryMb": null,
          "targetMemoryBuffer": null
        },
        "memoryMb": 2000,
        "processors": 2,
        "vmSize": "Custom"
      },
      "httpProxyConfig": null,
      "instanceView": {
        "vmAgent": {
          "statuses": [
            {
              "code": "ProvisioningState/succeeded",
              "displayStatus": "Connected",
              "level": "Info",
              "message": "Connection with mocguestagent was succesfully reestablished",
              "time": "2024-06-24T17:25:19+00:00"
            }
          ],
          "vmConfigAgentVersion": "v0.18.0-4-gd54376b0"
        }
      },
      "networkProfile": {
        "networkInterfaces": []
      },
      "osProfile": {
        "adminPassword": null,
        "adminUsername": "azureuser",
        "computerName": "testvm001",
        "linuxConfiguration": {
          "disablePasswordAuthentication": false,
          "provisionVmAgent": false,
          "provisionVmConfigAgent": true,
          "ssh": {
            "publicKeys": null
          }
        },
        "windowsConfiguration": {
          "enableAutomaticUpdates": null,
          "provisionVmAgent": false,
          "provisionVmConfigAgent": true,
          "ssh": {
            "publicKeys": null
          },
          "timeZone": null
        }
      },
      "provisioningState": "Succeeded",
      "resourceUid": null,
      "securityProfile": {
        "enableTpm": false,
        "securityType": null,
        "uefiSettings": {
          "secureBootEnabled": true
        }
      },
      "status": {
        "errorCode": "",
        "errorMessage": "",
        "powerState": "Running",
        "provisioningStatus": null
      },
      "storageProfile": {
        "dataDisks": [],
        "imageReference": {
          "id": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.AzureStackHCI/galleryImages/WinImage-26tdJUIS",
          "resourceGroup": "<Resource group name>"
        },
        "osDisk": {
          "id": null,
          "osType": "Windows"
        },
        "vmConfigStoragePathId": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.AzureStackHCI/storageContainers/UserStorage2-guid"
      },
      "vmId": "<guid>"
    },
    "resourceGroup": "<Resource group name>",
    "systemData": {
      "createdAt": "2024-06-24T01:29:06.594266+00:00",
      "createdBy": "<guid>",
      "createdByType": "Application",
      "lastModifiedAt": "2024-06-24T17:28:13.206935+00:00",
      "lastModifiedBy": "<guid>",
      "lastModifiedByType": "Application"
    },
    "type": "microsoft.azurestackhci/virtualmachineinstances"
  }
}

Save a VM

Saving a VM stores the current state of the VM to the disk and stops the VM. Saving a VM frees up memory and CPU resources. You can only save running VMs.

  1. Connect to a machine on your system.

  2. To save the VM, run the following PowerShell cmdlet:

    #Set input parameters

$rg = "<Resource group name>"
$vmName = "<VM name>"

#Save the VM

az stack-hci-vm save --name $vmName --resource-group $rg

    The parameters used for this cmdlet are as follows:

    Parameter Description
    name Name of the virtual machine.
    resource-group Name of resource group. You can configure the default group using az configure --defaults group=<name>.
    subscription Name or ID of subscription. You can configure the default subscription using az account set -s <Subscription name or Subscription ID>.

  3. Check the VM status to verify that the VM is saved.

    #Check the VM status

az stack-hci-vm show --name $vmName --resource-group $rg

  4. Start the VM to resume the VM from the saved state. Verify that the VM is running.

    #Start the VM

az stack-hci-vm start --name $vmName --resource-group $rg

    Example output

    Expand this section to see an example output. 
    #Set parameters

[v-host1]: PS C:\Users\HCIDeploymentUser> $rg = "<Resource group name>"    
[v-host1]: PS C:\Users\HCIDeploymentUser> $vmName = "<VM name>"

#Save the VM

[v-host1]: PS C:\Users\HCIDeploymentUser> az stack-hci-vm save --name $vmName --resource-group $rg

#Show the current state of the VM

[v-host1]: PS C:\Users\HCIDeploymentUser> az stack-hci-vm show -g $rg --name $vmName
{
  "attestationStatus": null,
  "virtualmachineinstance": {
    "extendedLocation": {
      "name": "/subscriptions/<Subscription ID>/resourcegroups/<Resource group name>/providers/Microsoft.ExtendedLocation/customLocations/s-cluster-customlocation",
      "type": "CustomLocation"
    },
    "id": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/testvm001/providers/Microsoft.AzureStackHCI/virtualMachineInstances/default",
    "identity": null,
    "name": "default",
    "properties": {
      "guestAgentInstallStatus": null,
      "hardwareProfile": {
        "dynamicMemoryConfig": {
          "maximumMemoryMb": null,
          "minimumMemoryMb": null,
          "targetMemoryBuffer": null
        },
        "memoryMb": 2000,
        "processors": 2,
        "vmSize": "Custom"
      },
      "httpProxyConfig": null,
      "instanceView": {
        "vmAgent": {
          "statuses": [
            {
              "code": "ProvisioningState/succeeded",
              "displayStatus": "Connected",
              "level": "Info",
              "message": "Connection with mocguestagent was succesfully reestablished",
              "time": "2024-06-24T17:25:19+00:00"
            },
          ],
          "vmConfigAgentVersion": "v0.18.0-4-gd54376b0"
        }
      },
      "networkProfile": {
        "networkInterfaces": []
      },
      "osProfile": {
        "adminPassword": null,
        "adminUsername": "azureuser",
        "computerName": "testvm001",
        "linuxConfiguration": {
          "disablePasswordAuthentication": false,
          "provisionVmAgent": false,
          "provisionVmConfigAgent": true,
          "ssh": {
            "publicKeys": null
          }
        },
        "windowsConfiguration": {
          "enableAutomaticUpdates": null,
          "provisionVmAgent": false,
          "provisionVmConfigAgent": true,
          "ssh": {
            "publicKeys": null
          },
          "timeZone": null
        }
      },
      "provisioningState": "Succeeded",
      "resourceUid": null,
      "securityProfile": {
        "enableTpm": false,
        "securityType": null,
        "uefiSettings": {
          "secureBootEnabled": true
        }
      },
      "status": {
        "errorCode": "",
        "errorMessage": "",
        "powerState": "Saved",
        "provisioningStatus": null
      },
      "storageProfile": {
        "dataDisks": [],
        "imageReference": {
          "id": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.AzureStackHCI/galleryImages/WinImage-26tdJUIS",
          "resourceGroup": "<Resource group name>"
        },
        "osDisk": {
          "id": null,
          "osType": "Windows"
        },
        "vmConfigStoragePathId": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.AzureStackHCI/storageContainers/UserStorage2-345d968fa1e74e99a9509ab7f3d259fd"
      },
      "vmId": "<guid>"
    },
    "resourceGroup": "<Resource group name>",
    "systemData": {
      "createdAt": "2024-06-24T01:29:06.594266+00:00",
      "createdBy": "<guid>",
      "createdByType": "Application",
      "lastModifiedAt": "2024-06-24T18:29:02.794305+00:00",
      "lastModifiedBy": "<guid>",
      "lastModifiedByType": "Application"
    },
    "type": "microsoft.azurestackhci/virtualmachineinstances"
  }
}

#Start the VM after it was saved

[v-host1]: PS C:\Users\HCIDeploymentUser> az stack-hci-vm start --name $vmName --resource-group $rg
Inside _start_initial/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/testvm0012024-02-01-previewhttps://management.azure.com/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/testvm001/providers/Microsoft.AzureStackHCI/virtualMachineInstances/default/start?api-version=2024-02-01-preview

#Show the current state of the VM. The VM should be running.

[v-host1]: PS C:\Users\HCIDeploymentUser> az stack-hci-vm show -g $rg --name $vmName
{
  "attestationStatus": null,
  "virtualmachineinstance": {
    "extendedLocation": {
      "name": "/subscriptions/<Subscription ID>/resourcegroups/<Resource group name>/providers/Microsoft.ExtendedLocation/customLocations/s-cluster-customlocation",
      "type": "CustomLocation"
    },
    "id": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/testvm001/providers/Microsoft.AzureStackHCI/virtualMachineInstances/default",
    "identity": null,
    "name": "default",
    "properties": {
      "guestAgentInstallStatus": null,
      "hardwareProfile": {
        "dynamicMemoryConfig": {
          "maximumMemoryMb": null,
          "minimumMemoryMb": null,
          "targetMemoryBuffer": null
        },
        "memoryMb": 2000,
        "processors": 2,
        "vmSize": "Custom"
      },
      "httpProxyConfig": null,
      "instanceView": {
        "vmAgent": {
          "statuses": [
            {
              "code": "ProvisioningState/succeeded",
              "displayStatus": "Connected",
              "level": "Info",
              "message": "Connection with mocguestagent was succesfully reestablished",
              "time": "2024-06-24T18:32:41+00:00"
            }
          ],
          "vmConfigAgentVersion": "v0.18.0-4-gd54376b0"
        }
      },
      "networkProfile": {
        "networkInterfaces": []
      },
      "osProfile": {
        "adminPassword": null,
        "adminUsername": "azureuser",
        "computerName": "testvm001",
        "linuxConfiguration": {
          "disablePasswordAuthentication": false,
          "provisionVmAgent": false,
          "provisionVmConfigAgent": true,
          "ssh": {
            "publicKeys": null
          }
        },
        "windowsConfiguration": {
          "enableAutomaticUpdates": null,
          "provisionVmAgent": false,
          "provisionVmConfigAgent": true,
          "ssh": {
            "publicKeys": null
          },
          "timeZone": null
        }
      },
      "provisioningState": "Succeeded",
      "resourceUid": null,
      "securityProfile": {
        "enableTpm": false,
        "securityType": null,
        "uefiSettings": {
          "secureBootEnabled": true
        }
      },
      "status": {
        "errorCode": "",
        "errorMessage": "",
        "powerState": "Running",
        "provisioningStatus": null
      },
      "storageProfile": {
        "dataDisks": [],
        "imageReference": {
          "id": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.AzureStackHCI/galleryImages/WinImage-26tdJUIS",
          "resourceGroup": "<Resource group name>"
        },
        "osDisk": {
          "id": null,
          "osType": "Windows"
        },
        "vmConfigStoragePathId": "/subscriptions/<Subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.AzureStackHCI/storageContainers/UserStorage2-guid"
      },
      "vmId": "<guid>"
    },
    "resourceGroup": "<Resource group name>",
    "systemData": {
      "createdAt": "2024-06-24T01:29:06.594266+00:00",
      "createdBy": "<guid>",
      "createdByType": "Application",
      "lastModifiedAt": "2024-06-24T18:35:18.206280+00:00",
      "lastModifiedBy": "<guid>",
      "lastModifiedByType": "Application"
    },
    "type": "microsoft.azurestackhci/virtualmachineinstances"
  }
}

Change local account password

Follow these steps to change the local account passwords for an Arc VM deployed on your Azure Local. The steps are different for Windows and Linux VMs.

  1. Sign in to the Arc VM.

  2. Run the following PowerShell command:

    # Define the username
$username = "AccountName"

# Prompt the user to enter the new password securely
$newPassword = Read-Host -AsSecureString "Enter the new password for $username"

# Prompt the user to re-enter the new password securely for verification
$verifyPassword = Read-Host -AsSecureString "Re-enter the new password for verification"

# Convert the secure strings to plain text for comparison
$plainPassword = [Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR($newPassword))
$plainVerifyPassword = [Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR($verifyPassword))

# Check if the passwords match and change the password if they match. Fail if the passwords don’t match.
if ($plainPassword -eq $plainVerifyPassword) {
    $account = [ADSI]"WinNT://./$username,user"
    $account.SetPassword($plainPassword)
    $account.SetInfo()

    Write-Host "Password for user $username has been reset successfully." -ForegroundColor Green
} else {
    Write-Host "The passwords do not match. Please try again." -ForegroundColor Red
}

Delete a VM

Follow these steps in the Azure portal of your Azure Local to remove a VM.

  1. Go to the Azure Local resource and then go to Virtual machines.

  2. In the right pane, from the list of virtual machines, select a VM that you wish to remove from your system.

  3. On the Overview page for the VM, from the top command bar in the right pane, select Delete, then select Yes.

    You are now prompted to confirm the deletion. Select Yes. Verify the VM is removed.

    Note that when a VM is deleted, all the resources associated with the VM are not deleted. For example, the data disks or the network interfaces associated with the VM are not deleted. You need to locate and delete these resources separately.

    Screenshot of warning when deleting VM.

  4. You can now go to the resource group where this VM was deployed. You can see that the VM is removed from the list of resources in the resource group. You may need to select the option to Show hidden types to view the resources associated with this VM that were not deleted.

    Screenshot of hidden types resources associated with a virtual machine.

Locate the associated resources such as the network interfaces and data disks, and delete them.

Change cores and memory

Follow these steps in the Azure portal of your Azure Local to change cores and memory.

  1. Go to your Azure Local resource and then go to Virtual machines.

  2. From the list of VMs in the right pane, select and go to the VM whose cores and memory you want to modify.

  3. Under Settings, select Size. Edit the Virtual processor count or Memory (MB) to change the cores and memory size for the VM. Only the memory size can be changed. The memory type can't be changed once a VM is created.

    Screenshot of Size page for a VM.

Next steps