You can clone an identical copy of a vApp template with the vCloud.Template.MakeIdenticalCopy custom property.

When set to True, the VCloud.Template.MakeIdenticalCopy custom property instructs vRealize Automation to ignore the customization specified in the vApp blueprint selected for provisioning and its vApp component blueprints. In this example, only the vApp template, and not the vApp and vApp component blueprints, are used to provision the vApp and its virtual machines. The default setting for the property is False.

A vApp and its component machines are provisioned as an identical copy of the vApp template. The only changes from the vApp template are the names of the cloned vApp and its virtual machines, which are generated from the machine prefix. See Custom Properties for vApp Blueprints.

To use the VCloud.Template.MakeIdenticalCopy property, a tenant administrator or business group manager enters the custom property on the Properties page of the vApp blueprint or as part of a build profile. The property can also reside in a business group that includes the selected vApp blueprint, although using this approach affects all vApp blueprints in the business group.

vApps provisioned as identical copies can use networks and storage profiles that are not available in the vRealize Automation reservation. If you clone a vApp template and use the identical copy option, the machine is successfully provisioned. The network and storage settings are used without their allocation being accounted for in a reservation. To avoid having unaccounted reservation allocations, verify that the storage profile or network specified in the template is available in the reservation.

Table 1. Property and Template Settings for Making an Identical Copy

Make Identical Copy Using a Blueprint Property

Make Identical Copy Using a vApp Template

Result

True

Ignored

Clone from the vApp template only.

  • Do not configure networks.

  • Do not customize hardware.

  • Do not change the computer name.

  • Do not join vApp virtual machines to the AD domain.

Only the names of the vApp machine and its component machines are changed from the template names.

The SysPrep. custom properties are ignored.

False

Selected

Clone from the vApp template. Also use the vApp and vApp component blueprints, but do not configure networks.

Use the storage path specified in the vApp component blueprint, or one specified for a component during a request for a vApp machine.

The SysPrep. custom properties are recognized.

False

Not Selected

Clone from the vApp template. Also use the vApp and vApp component blueprints.

If the custom property is set to True for the vApp blueprint, and an assigned vApp component blueprint specifies a minimum and maximum range for machine resources, changes made to the machine resources when using those blueprints are ignored. You can change the machine resources after provisioning the machine and while it is powered on.

If the custom property is set to True for the vApp blueprint, and an assigned vApp component blueprint specifies a different storage path than the one specified in the vApp template, the storage path specified in the vApp template prevails.