If you want to stretch deploy a VM that is part of a network that has already been stretched, you can only move it to the same destination.

That is, if you already stretch deployed a VM from a private cloud to a public vCloud and vCloud Connector created a routed vApp network for it in the public vCloud, when you move any other VMs from the same private network, they are moved to the same routed vApp network on the public vCloud.

All the prerequisites and restrictions listed in Stretch Deploy a VM from a Private vCloud Director Cloud to a Public vCloud apply.


In the Browser panel on the left, expand the Clouds tree, and select a private vCloud.


In the Inventory panel, click the Virtual Machines tab.


Select the VM that you want to stretch deploy to the public vCloud.

Available action buttons appear at the top of the panel.


If the VM is powered on or suspended, click the Power Off icon at the top of the panel to power it off.


The VM that you want to stretch deploy must be powered off but its parent vApp must be powered on.


Click the Stretch Deploy icon.

If the Stretch Deploy icon is disabled, hover over the icon to view tooltip information on why the action is unavailable. For more information, see the Prerequisites listed above.

The Stretch Deploy wizard appears.


Select a catalog in the source cloud for vCloud Connector to store a temporary vApp template.

vCloud Connector needs to create a temporary vApp template while moving a VM to a vCloud; this is a vCloud Director requirement. The temporary vApp template will be deleted after the VM is deployed in the public vCloud.


Click Next.


In the Select a target page, the Cloud field and the Stretched vApp Name field are already selected. These indicate the Organization VDC and the vApp in which the VM will be deployed in the public vCloud. You cannot change these fields.


Select a catalog in the public vCloud in which to store the vApp template for the VM. All the catalogs available to your organization are listed.


Click Next.


In the Select Resources page, the Organization VDC, network configuration, and external IP are already selected. Click Next.


In the Proxy page, click Next.

The fields on the Proxy page are disabled when you are moving a VM from a network that has already been stretched.


If you want to power on the VM after moving it to the public vCloud, select Power on deployed entity.


Click Next, review your selections, then click Finish.

vCloud Connector uses the SSL VPN tunnel it created when the network was first stretched to copy and deploy the VM into the routed vApp network in the public vCloud.

You can track the progress of the Stretch Deploy command in the Tasks panel. See Track the Progress of the Stretch Deploy Command for more information.


After you move a VM to a public vCloud with the Stretch Deploy command, do not power on or delete the VM in its original location.


In the public vCloud, do not modify the Routed vApp network created by vCloud Connector. Specifically, do not change any network configuration settings (such as DHCP, NAT, or firewall settings) on the vShield Edge of the Routed vApp network.