Running Actions for Provisioned Resources

The actions that are available for a provisioned resource depend on the type of resource, how the action was configured and made available for provisioned items, and the operational state of the item.

The configured actions that are available for a provisioned machine or deployment appear in the Actions menu for the selected resource on the Items tab.

If the item was provisioned by IaaS using an IaaS machine blueprint, the list of available actions is determined by what was selected on the Actions tab for the machine type component when the blueprint was created, and then by what is applicable based on machine type or state.

If the item was provisioned using an XaaS blueprint, the resource actions must be created, published, and entitled in the same service that is used to provision the item. The list of available actions is determined by the item type and the current state of the item.

The available actions for an item that was provisioned as an IaaS machine might also include XaaS resource actions if the actions are mapped to the item.

You can view and manage deployments and send reclamation requests to deployment owners. A reclamation request specifies a new lease length in days, the amount of time given for a deployment owner’s response, and which machines to target for reclamation.

You can change the reservation or storage setting for a managed machine. This ability is useful when a machine moves to a new storage path that is not available in its current reservation. For a single machine deployment, you can also change the business group for the machine.

Depending on how your administrators have configured your environment, you might be able to create a snapshot of your virtual machine. A snapshot is an image of a virtual machine at a specific time. It is a space-efficient copy of the original VM image. Snapshots are an easy way to recover a system from damage, data loss, or security threats. After you create a snapshot of your virtual machine, you can apply it and reset your system back to the point where the snapshot was taken.

If your vRealize Automation deployment uses untrusted certificates, before you can use remote consoles with VMware Remote Console, you must configure your client browser to trust the certificate, The steps to do this vary by browser.

If a failed blueprint deployment includes a vRealize Orchestrator workflow, you can use the token ID to troubleshoot problems with the workflow. You use the token ID to locate the logs in vRealize Orchestrator.