If you want to move a VM or vApp 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 or vApp from a Private vSphere Cloud to a Public vCloud apply.


In the Browser panel on the left, expand the Clouds tree and select a vSphere cloud.


In the Inventory panel, click the Virtual Machines tab or the vApps tab.


Select the virtual machine or vApp that you want to move to the public vCloud.

Available action buttons appear at the top of the panel.


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


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.


In the Select a target page, the destination cloud is already selected and you cannot change it because the network of the VM or vApp is already extended to the selected cloud and it cannot be extended to another cloud.

The name of the routed vApp deployed in the public vCloud is also specified and you cannot change it.


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

vCloud Connector uploads the VM or vApp to the public vCloud as a vApp template; this is a vCloud Director requirement.


Click Next.


In the Select resources page, the virtual datacenter and network configuration is already selected and you cannot change it because the network of the VM or vApp has already been extended to this location in the public vCloud.


Click Next.


In the Proxy page, click Next.

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


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


Click Next, review your selections, then click Finish.


If the VM that you stretch deployed has a Manual Static IP mode, then, after the Stretch Deploy command finishes


Log on to the public vCloud.


Locate and double-click the stretched vApp.


Right-click the VM that had the Manual Static IP mode and power it off.


Right-click the VM again and select Properties, then select the Hardware tab.


Change the IP mode of the VM from DHCP to Manual Static, then click OK.


Power on the VM.

vCloud Connector uses the SSL VPN tunnel it created when the network was first stretched to copy and deploy the VM or vApp 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 or vApp to a public vCloud with the Stretch Deploy command, do not power on or delete the VM or vApp 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.