There are several methods you can use with vRealize Automation to provision virtual machines.

Most of these options require some additional configuration outside of vRealize Automation.

Table 1. Choosing a Provisioning Method

Scenario

Supported Platforms

Provisioning Method

Pre-provisioning Preparations

Provision machines with no guest operating system. You can install an operating system after provisioning.

All

Basic

No required pre-provisioning preparations outside of vRealize Automation.

Provision machines by cloning from a template object created from an existing Windows or Linux machine, called the reference machine, and a customization specification.

  • vSphere

  • KVM (RHEV)

  • SCVMM

Clone

Checklist for Virtual Provisioning by Cloning Preparation

Provision a space-efficient copy of a virtual machine called a linked clone. Linked clones are based on a snapshot of a VM and use a chain of delta disks to track differences from a parent machine.

vSphere

Linked clone

No required pre-provisioning preparations outside of vRealize Automation.

Provision a space-efficient copy of a virtual machine by using Net App FlexClone technology.

vSphere

FlexClone

Checklist for Virtual Provisioning by Cloning Preparation

Provision a machine by booting from an ISO image, using a kickstart or autoYaSt configuration file and a Linux distribution image to install the operating system on the machine.

All

Linux Kickstart

Choosing Your Linux Kickstart Provisioning Preparation Method

Provision a machine and pass control to an SCCM task sequence to boot from an ISO image, deploy a Windows operating system, and install the vRealize Automation guest agent.

All

Virtual SCCM

Preparing for SCCM Provisioning

Provision a machine by booting into a WinPE environment and installing an operating system using a Windows Imaging File Format (WIM) image of an existing Windows reference machine.

All

WIM Image

Preparing for WIM Provisioning