Before you turn on a host for PXE boot with vSphere Auto Deploy, you must install prerequisite software and set up the DHCP and TFTP servers that Auto Deploy interacts with.


If you set up Auto Deploy to boot a host, vSphere checks each of the local storage devices on the system for existing partitions. To avoid the possibility of data loss, vSphere does not create partitions under the following conditions:

A local storage device contains a GPT partition map.

A local storage device contains an MBR partition table that defines at least one partition.

Storage is remote.

If hosts have local storage with a partition table that vSphere does not recognize, such as Linux Logical Volume Manager, vSphere overwrites the storage and creates new partitions. To make sure local storage is not considered for partitioning, you can physically disconnect that storage.

Ensure that the hosts you will provision with Auto Deploy meet the hardware requirements for ESXi 5.0.

See ESXi Hardware Requirements.


You cannot provision EFI hosts with Auto Deploy unless you switch the EFI system to BIOS compatibility mode.

Ensure that the ESXi hosts have network connectivity to vCenter Server and that all port requirements are met.

See Required Ports for vCenter Server.

Do not use VLAN tagged networks at the boot NIC. If you want to specify VLAN IDs, you must make sure that the host can reach the DHCP server when the host starts the boot process. Check with your network administrator how VLAN IDs are used in your environment.

Ensure that you have enough storage for the Auto Deploy repository. The Auto Deploy server uses the repository to store data it needs, including the rules and rule sets you create and the VIBs and image profiles that you specify in your rules.

Best practice is to allocate 2GB to have enough room for four image profiles and some extra space. Each image profile requires approximately 350MB. Determine how much space to reserve for the Auto Deploy repository by considering how many image profiles you expect to use.

Obtain the vCenter Server installation media, which include the Auto Deploy installer, or deploy the vCenter Server Appliance.

See Installing vCenter Server.

Ensure that a TFTP server is available in your environment. If you require a supported solution, purchase a supported TFTP server from your vendor of choice.

Obtain administrative privileges to the DHCP server that manages the network segment you want to boot from. You can use a DHCP server already in your environment, or install a DHCP server. For your Auto Deploy setup, replace the gpxelinux.0 file name with undionly.kpxe.vmw-hardwired.

Secure your network as you would for any other PXE-based deployment method. Auto Deploy transfers data over SSL to prevent casual interference and snooping. However, the authenticity of the client or the Auto Deploy server is not checked during a PXE boot. See Auto Deploy Best Practices and Security Consideration.


Auto Deploy is not supported with NPIV (N_Port ID Virtualization).

Set up a remote Syslog server. See the vCenter Server and Host Management documentation for Syslog server configuration information. Configure the first host you boot to use the remote syslog server and apply that host's host profile to all other target hosts. Optionally, install and use the vSphere Syslog Collector, a vCenter Server support tool that provides a unified architecture for system logging and enables network logging and combining of logs from multiple hosts.

Install ESXi Dump Collector and set up your first host so all core dumps are directed to ESXi Dump Collector and apply the host profile from that host to all other hosts. See Configure ESXi Dump Collector with ESXCLI and Set Up ESXi Dump Collector from the Host Profiles Interface.

See Install vSphere ESXi Dump Collector.

Auto Deploy does not support in a pure IPv6 environment because the PXE boot infrastructure requires IPv4.


Install the vSphere Auto Deploy server as part of a vCenter Server installation or standalone on a Windows system, or deploy the vCenter Server Appliance to an ESXi system of your choice.



vCenter Server system

Use the vCenter Server installation media to install Auto Deploy on the same host as the vCenter Server system itself. That vCenter Server system manages all hosts that you provision with this Auto Deploy installation.

See Install vSphere Auto Deploy.

Windows system

Use the vCenter Server installation media to install Auto Deploy on a Microsoft Windows system that does not have a vCenter Server system installed. The installer prompts you for a vCenter Server system to register Auto Deploy with. That vCenter Server system manages all hosts that you provision with this Auto Deploy installation.

See Install vSphere Auto Deploy.

vCenter Server Appliance

Deploy the vCenter Server Appliance to the ESXi host of your choice. The appliance includes an Auto Deploy server, which is disabled by default.

By default, the vCenter Server system on the appliance manages all hosts you provision with the appliance Auto Deploy installation. Other configurations are supported. See Using Auto Deploy with the VMware vCenter Server Appliance.


Configure the TFTP server.


In a vSphere Client connected to the vCenter Server system that Auto Deploy is registered with, click Home in the navigation bar and select Auto Deploy in the Administration tab to display the Auto Deploy page.


Click Download TFTP ZIP to download the TFTP configuration file and unzip the file to the directory in which your TFTP server stores files.


Set up your DHCP server to point to the TFTP server on which the TFTP ZIP file is located.


Specify the TFTP Server's IP address in DHCP option 66 (frequently called next-server).


Specify the boot file name, which is undionly.kpxe.vmw-hardwired in the DHCP option 67 (frequently called boot-filename).


Set each host you want to provision with Auto Deploy to network boot or PXE boot, following the manufacturer's instructions.


Locate the image profile you want to use and the depot in which it is located.

In most cases, you point to an image profile VMware makes available in a public depot. If you want to include custom VIBs with the base image, you can use the Image Builder PowerCLI create an image profile and use that image profile. See the Image Builder PowerCLI documentation.


Write a rule that assigns an image profile to hosts.


(Optional) You can use your own Certificate Authority (CA) by replacing the OpenSSL certificate (rbd-ca.crt) and the OpenSSL private key (rbd-ca.key) with your own certificate and key file.

On Windows, the files are in the SSL subfolder of the Auto Deploy installation directory. For example, on Windows 7 the default is C:\ProgramData\VMware\VMware vSphere Auto Deploy\ssl.

On the vCenter Server Appliance, the files are in /etc/vmware-rbd/ssl/.

When you start a host that is set up for Auto Deploy, it contacts the DHCP server and is directed to the Auto Deploy server, which provisions the host with the image specified in the active rule set.

Install PowerCLI. See Install PowerCLI and Prerequisite Software.

Use the PowerCLI cmdlets to define a rule that assigns an image profile and optional host profile to the host. See Prepare Your System and Install the Auto Deploy Server.

Configure the first host your provision to use the storage, networking, and other settings you want for your target hosts to share. Create a host profile for that host and write a rule that assigns both the already tested image profile and the host profile to target hosts.

If you have to configure host-specific information, set up the host profile of the reference host to prompt for user input. See Customizing Hosts with Answer Files.