Before you can create a vRealize Orchestrator integration and use vRealize Orchestrator workflows in Extensbility, you must first download and deploy a orchestrator appliance.


  • Verify that vCenter Server is installed and running.

  • Verify that the host on which you are deploying the appliance meets the minimum hardware requirements:

    • 2 CPUs

    • 6 GB of memory

    • 17 GB hard disk


    Do not reduce the default memory size, because the Orchestrator server requires at least 2 GB of free memory.

  • If your system is isolated and without Internet access, you must download the .ova file for the appliance from the VMware Web site.

  • Cloud Administrator role


  1. Click Integrations > Add Integration > vRealize Orchestrator.
  2. Click the SaaS-Enabled Orchestrator link to download the vRealize Orchestrator OVA application.
  3. Log in to the vSphere Web Client as an administrator.
  4. In the vSphere Web Client, select an inventory object that is a valid parent object of a virtual machine, such as a data center, folder, cluster, resource pool, or host.
  5. Select Actions > Deploy OVF Template.
  6. Navigate to the location where the .ova file was saved and click Next.
  7. Review the OVF template details and click Next.
  8. Accept the terms in the license agreement and click Next.
  9. Enter a name and location for the deployed appliance, and click Next.
  10. Select a host, cluster, resource pool, or vApp as a destination on which you want the appliance to run, and click Next.
  11. Select a format in which you want to save the virtual disk and the storage of the appliance.



    Thick Provisioned Lazy Zeroed

    Creates a virtual disk in a default thick format. The space required for the virtual disk is allocated when the virtual disk is created. If any data remains on the physical device, it is not erased during creation, but is zeroed out on demand later on first write from the virtual machine.

    Thick Provisioned Eager Zeroed

    Supports clustering features such as Fault Tolerance. The space required for the virtual disk is allocated when the virtual disk is created. If any data remains on the physical device, it is zeroed out when the virtual disk is created. It might take much longer to create disks in this format than to create disks in other formats.

    Thin Provisioned Format

    Saves hard disk space. For the thin disk, you provision as much datastore space as the disk requires based on the value that you select for the disk size. The thin disk starts small and, at first, uses only as much datastore space as the disk needs for its initial operations.

  12. Select the options that you want to enable and set the initial password for the root user account.

    Your initial password must be at least eight characters long.


    The password for the root account of the Orchestrator Appliance expires after 365 days. You can increase the expiry time for an account by logging in to the Orchestrator Appliance as root, and running passwd -x number_of_days name_of_account. If you want to increase the Orchestrator Appliance root password to infinity, run passwd -x 99999 root.

  13. (Optional) Configure the network settings, and click Next.

    By default, the Orchestrator Appliance uses DHCP. You can change this setting and assign a fixed IP address from the appliance Web console.

  14. Review the Ready to Complete page and click Finish.


The Orchestrator Appliance is successfully deployed.

What to do next

For information on setting up vRO, refer to the vRealize Orchestrator Install and Config Guide for version 7.5 or later.