To allow greater flexibility when modifying template properties during instantiation, use SourcedItem instead of SourcedVmInstantiationParams when specifying instantiation details in InstantiateVAppTemplateParams.

An InstantiateVAppTemplateParams request body that incorporates one or more SourcedItem elements supports the following configuration changes:

Change the name, Description, and NeedsCustomization properties of the virtual machine.

Specify a storage profile for the virtual machine.

Specify a storage profile for any of the virtual machine's hard disks, overriding the virtual machine's default storage profile.

Increase the capacity of the virtual machine's SATA or SCSI disks.

Increase or decrease the size of the virtual machine's memory.

Increase or decrease the number of CPU cores per virtual socket.

Add or remove CPUs.

You can also modify any of these configuration settings after the vApp is deployed. See Configuring vApps and Virtual Machines.

Verify that you are logged in to the vCloud API as an administrator, Catalog Author, or vApp Author.

Review the current configuration of the vApp and its virtual machines. Configuration parameters in the VAppTemplate such as its NetworkConfigSection and LeaseSettingsSection affect all virtual machines in the vApp. Configuration parameters for individual virtual machines are defined in Vm elements in the VAppTemplate. A virtual machine's network connections are defined in its NetworkConnectionSection, and its hardware configuration is defined in its VirtualHardwareSection. To view the configuration of a virtual machine in a vApp template, you can retrieve the template and examine the VirtualHardwareSection of that Vm, or you can download the OVF descriptor of the vApp template, as shown in Download the OVF Descriptor of a vApp or vApp Template.


To change the name, Description, or NeedsCustomization properties of the virtual machine, add a VmGeneralParams element to the SourcedItem.


Examine the OVF descriptor of the template to determine the values that you can include in the VirtualHardwareSection of the SourcedItem element.


Include the SourcedItem element in an InstantiateVAppTemplateParams element.


Make a POST request to the action/instantiateVAppTemplate URL of the VDC.

Supply the InstantiateVAppTemplateParams element as the request body.

This InstantiateVAppTemplateParams request extends the request shown in Example: Instantiate a vApp Template to include a SourcedItem element that makes several configuration changes in the virtual machine referenced at

Changes the name and Description of the virtual machine, so that they are not the same as the name and Description in the template.

Sets the value of NeedsCustomization to true.

Adds a virtual CPU and changes the value of CoresPerSocket to 2. If you include a CoresPerSocket element, its value must be an integer multiple of the value of the existing rasd:VirtualQuantity of CPU items, or of the value you supply in NumberOfCpus. Example: Modify the CPU Configuration of a Virtual Machine shows the original CPU configuration, and how to make this change by reconfiguring the virtual machine in a deployed vApp.

Increases the capacity of the hard disk from 1GB to 10GB by including a Disk element that specifies a Size of 10240 for the disk that has a rasd:InstanceID value of 2000. The value you supply for Size is interpreted as megabytes. You can see the original disk configuration in Example: Retrieve the Hard Disks and Controllers in a Virtual Machine . Example: Modify the Hard Disk Configuration of a Virtual Machine shows how to make the same change by reconfiguring the virtual machine in a deployed vApp. If you include a Disk element, the value of its instanceId attribute must match the value in the rasd:InstanceID element of an existing Item that defines a virtual disk (RASD resource type 17). Disk capacity can be raised, but not lowered, for disks on SATA and SCSI controllers. The capacity of other disk types cannot be changed. Item elements that represent SATA disks have a vcloud:busType attribute with the value 20. Those that represent SCSI disks have a vcloud:busType attribute with the value 6.

With the exception of the changes specified in VmGeneralParams (name, Description, and NeedsCustomization), this example has the same effect as the example in Example: Modify Virtual Machine Hardware During vApp Template Instantiation.


You cannot mix SourcedVmInstantiationParams and SourcedItem elements in a single InstantiateVAppTemplateParams request body.


Content-Type: application/vnd.vmware.vcloud.instantiateVAppTemplateParams+xml
<?xml version="1.0" encoding="UTF-8"?>
   name="Linux FTP server"
   <Description>Example FTP Server</Description>
   <Source href=""/>
      <Source href=""/>
         <Description>Primary FTP Server Instance</Description>
            <ovf:Info>Configuration parameters for logical networks</ovf:Info>
            <NetworkConfig networkName="vAppNetwork">
                  <ParentNetwork href=""/>
            <ovf:Info>Lease Settings</ovf:Info>
            <ovf:Info>Virtual hardware requirements</ovf:Info>
               <rasd:Description>Hard disk</rasd:Description>
               <rasd:ElementName>Hard disk 1</rasd:ElementName>
               <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>
               <rasd:Description>Number of Virtual CPUs</rasd:Description>
               <rasd:ElementName>1 virtual CPU(s)</rasd:ElementName>
      <StorageProfile href="">

The response is a sparsely populated VApp element, as shown in the response portion of Example: Deploying a vApp.