6.2

Table Of Contents
Cloning requires a template to clone from, created from a reference machine. You are not required to
install the guest agent or the WMI agent, and you are not required to specify Visual Basic scripts. These
options provide you with the ability to further configure machines provisioned from a clone template.
If you are provisioning a Windows machine by cloning, the only way to join the provisioned machine to an
Active Directory domain is by using the customization specification from vCenter Server or including a
guest operating system profile with your SCVMM template. Machines provisioned by cloning cannot be
placed in an Active Directory container during provisioning. This must be done manually after
provisioning.
Table 32. Preparing for Virtual Provisioning by Cloning Checklist
Task Location Details
Identify or create the reference
machine.
Hypervisor See the documentation provided by your
hypervisor.
(Optional) Install the
vRealize Automation guest agent on your
reference machine to customize deployed
machines.
Reference machine See Using vRealize Automation Guest
Agent in Provisioning.
(Optional) Install VMware Tools on the
reference machine.
vCenter Server See the VMware Tools documentation.
Use the reference machine to create a
template for cloning.
Hypervisor The reference machine may be powered
on or off. If you are cloning in
vCenter Server, you can use a reference
machine directly without creating a
template.
See the documentation provided by your
hypervisor.
Create the customization object to
configure cloned machines by applying
System Preparation Utility information or a
Linux customization.
Hypervisor If you are cloning for Linux you can install
the Linux guest agent and provide
external customization scripts instead of
creating a customization object. If you are
cloning with vCenter Server, you must
provide the customization specification as
the customization object.
See the documentation provided by your
hypervisor.
(Optional) If you installed and
configured an EPI agent, specify Visual
Basic scripts to run outside
vRealize Automation as additional steps in
the machine life cycle.
Machine where the EPI agent is installed See Enabling Visual Basic Scripts in
Provisioning.
IaaS Configuration for Virtual Platforms
VMware, Inc. 64