vCloud Automation Center – vCAC 5.1 – Custom Property of the Day #5 – Clone Spec

Caution: Articles written for technical not grammatical accuracy, If poor grammar offends you proceed with caution ;-)

POTD #5 Clone Spec
vCAC version: 5.1
Property Name

Property Description
This allows you to override the Customization Specification that is defined in the Blueprint.
Property Usage
I typically define this at either the Build Profile or Provisioning Group. It can be very useful if you need to utilize a different customization specification. An example would be a blueprint with a standard customization specification, but if assign a build profile that utilizes the guest agent I like to override the customization specification in the build profile to use one that installs the guest agent.
Usage: PropertyNme = CloneSpec    Property value = NameOfCustomizationSpecification
Recommended Placement
Build Profile or Provisioning Group

3 Replies to “vCloud Automation Center – vCAC 5.1 – Custom Property of the Day #5 – Clone Spec”

    1. I don’t know if I’m following your question. You can define the property in a build profile or at the provisioning group level. You don’t need to define a location for the customization specification. The value you attach to the property gets passed to the vCenter endpoint during the clone operation of a vCenter VM. The name must match the exact name of a customization specification that exists in the vCenter server that the VM is being provisioned against. I should clarify that in my post that this is a VMware vCenter only property.


      1. Hi Sid,

        it was my fault. I meant the CloneSpec, which doesn´t exists in vCenter AFAIK. I thought I can “attach” a CloneSpec (vmFolder, etc.) to a Clone Blueprint and override the VMs settings.


Leave a Reply