Edit

Run Command in Azure VMware Solution

  • Article

In Azure VMware Solution, vCenter Server has a built-in local user called cloudadmin assigned to the CloudAdmin role. The CloudAdmin role has vCenter Server privileges that differ from other VMware cloud solutions and on-premises deployments. The Run Command feature lets you perform operations that would normally require elevated privileges through a collection of PowerShell cmdlets.

Azure VMware Solution supports the following operations:

Note

Run Commands are executed one at a time in the order submitted.

View the status of an execution

You can view the status of any executed Run Command, including the output, errors, warnings, and information logs of the cmdlets.

  1. Sign in to the Azure portal.

    Note

    If you need access to the Azure US Gov portal, go to https://portal.azure.us/

  2. Select Run command > Run execution status.

    You can sort by the various columns by selecting the column.

    Screenshot showing Run Command execution status tab.

  3. Select the execution you want to view. A pane opens with details about the execution, and other tabs for the various types of output generated by the cmdlet.

    Screenshot showing an example of a run execution.

    You can view more details about the execution including the output, errors, warnings, and information.

    • Details - Summary of the execution details, such as the name, status, package, cmdlet name, and error if the command failed.

    • Output - Messages output by the cmdlet can include progress or the result of the operation. Not all cmdlets have output.

      Screenshot showing the output of a run execution.

    • Error - Error messages generated in the execution of the cmdlet in addition to the terminating error message on the details pane.

      Screenshot showing the errors detected during the execution of an execution.

    • Warning - Warning messages generated during the execution.

      Screenshot showing the warnings detected during the execution of an execution.

    • Information - Progress and diagnostic generated messages during the execution of a cmdlet.

      Screenshot showing the overall real-time progress of the cmdlet as it runs.

Cancel or delete a job

Method 1

This method attempts to cancel the execution, and then deletes it upon completion.

Important

Method 1 is irreversible.

  1. Select Run command > Run execution status and then select the job you want to cancel.

    Screenshot showing how to cancel and delete a run command.

  2. Select Yes to cancel and remove the job for all users.

Method 2

  1. Select Run command > Packages > Run execution status.

  2. Select More (...) for the job you want to cancel and delete.

    Screenshot showing how to cancel and delete a run command using the ellipsis.

  3. Select Yes to cancel and remove the job for all users.

Next steps

Now that you've learned about the Run Command concepts, you can use the Run Command feature to:

  • Configure storage policy - Each VM deployed to a vSAN datastore is assigned a vSAN storage policy. You can assign a vSAN storage policy in an initial deployment of a VM or when you do other VM operations, such as cloning or migrating.

  • Configure external identity source for vCenter Server (Run Command) - Configure Active Directory over LDAP or LDAPS for vCenter Server, which enables the use of an external identity source as an Active Directory. Then, you can add groups from the external identity source to the CloudAdmin role.

  • Deploy disaster recovery using JetStream - Store data directly to a recovery cluster in vSAN. The data gets captured through I/O filters that run within vSphere. The underlying vSphere datastore can be VMFS, vSAN, vVol, or any supported HCI platform.