The following sections show various ways to deploy OVF packages. What to read next Deploying an OVF Package Directly on an ESXi HostThe following command deploys an OVF package on an ESXi host. Deploying an OVF Package using Pull ModeOVF Tool 4.4.1 with vSphere 6.7 introduced the pull mode flag, which allows an ESXi host to directly download (pull) from a remote URL, assuming connectivity. Previously, data had to pass through another system, adding an unnecessary hop if an ESXi host can directly access the remote URL. Deploying an OVF Package through vCenter ServerThe following command deploys testVM.ovf from a local Windows disk to a data store named storage1 on host (10.2.3.56) from vCenter (10.2.3.4). the VM will be named myVM on the host. (To test this on your system, replace the incorrect IP addresses in this example with your actual data store and host IP addresses.) Deploying an OVF Package and Powering It OnOVF Tool can power on a virtual machine or vApp after deployment. This action can be done on all supported platforms. The following example powers on the VM or vApp on a particular host through vCenter Server: Deploying an OVF Package into vCloud DirectorYou can deploy an OVF package from OVF Tool into vCloud Director. The following example connects to vCloud Director and deploys the OVF package LAMP.ovf. Deploying an OVF Package into a vApprun WorkspaceA vApprun workspace allows Workstation and Fusion users to run vApps. It provides a complete vApprun execution environment, that includes nested vApps, OVF properties, and an OVF environment. The environment is fully compatible with vSphere 4 and all later releases. Parent topic: Examples of OVF Tool Syntax
