To create a vApp based on an existing vApp, you can copy a vApp and change the copy so that the copy meets your needs. You do not have to power off virtual machines in the vApp before you copy the vApp. The memory state of running virtual machines is preserved in the copied vApp.
Starting with VMware Cloud Director 10.4.2, you can create, copy, and edit VMs with Trusted Platform Module (TPM) devices. For more information on VMs with TPM devices, see Working with Virtual Machines in the VMware Cloud Director Tenant Portal.
Prerequisites
- You are at least a vApp user.
- The organization virtual data center is backed up by vCenter Server 5.5 or later.
- To enable operations across vCenter Server instances where the source and destination vCenter Server instances are not the same, verify that the vCenter Server instances trust each other independently of VMware Cloud Director. To view the certificates that a vCenter Server instance trusts, see the Explore Certificate Stores Using the vSphere Client in the VMware vSphere Product Documentation. Verify that each vCenter Server instance trusts the other vCenter Server instances that it needs to interact with. See also KB 89906.
-
- The copy operation is not across vCenter Server instances.
VMware Cloud Director does not support copying a powered-on vApp across vCenter Server instances.
- A VDC that supports TPM backs the VM.
- The copy operation is not across vCenter Server instances.
Procedure
Results
A copy of the vApp is created and the vApp copy is in a suspended state. The copied vApp is enabled for network fencing.
What to do next
Modify the network properties of the new vApp or power on the vApp.