Create a VMware ESXi 5 PXE unattended scripted installation using Windows

The most information available on how-to perform a unattended scripted installation of VMware ESXi 5 is based on Linux. Here is a procedure how-to create a scripted installation of VMware ESXi 5 using Microsoft Windows.

Here is an overview of the boot process:





What do we need

The following software must be downloaded:

Syslinux 3.86 (This is the Syslinux version VMware supports)

FileZilla Server 0_9_39

TFTPD 4.00

Notepad ++

VMware ESXi 5 ISO


Step 1 Windows XP

This procedure is tested with Microsoft Windows XP SP2. The following requirements must be met:

– In Windows XP use a fixed IP. In this example we use IP address

– Make sure there is enough free disk space available (approximately 500 MB needed)

– Disable the Windows firewall

Step 2 Create directory structure

Create the following directory structure in the root of the C: partition:


Step 3 Copy the content of the ESXi 5 ISO

Mount the VMware ESXi 5 ISO and copy the content to the c:\PXEboot directory

Step 4 Copy the Syslinux files

The Syslinux files allow the target ESXi server to boot the ESXi installer.

– Extract Syslinux 3.86 and:

– Copy the pxelinux.0 and menu.c32 files to the C:\PXEboot directory.

– Overwrite the menu.c32 file


Step 5 Install & Configure tftpd32

The Tftpd32 utility gets the function DHCP and TFTP server.

– Run Tftpd32.exe and make the following configuration settings:


image image
– TFTP Server
– DHCP Server
Point the base directory to c:\PXEboot
image image
Create a DHCP range Edit the ini file c:\program files\tftpd32\tftpd32.iniAdd the DHCP options
066 with DHCP server IP address
067 pxelinux.0


– Restart and run the tftpd32.exe utility


Step 6 Install  & configure FileZilla server

– Install the FileZilla Server with the default settings

– Create a user username: vmware password: vmware


– Add a shared folder c:\PXEboot\Kickstart folder with the default rights

2011-09-19 18h32_16


Step 7 Create default file

Create a file named default (Use notepad ++ for the file creation) and save the file in the  C:\PXEboot\pxelinux.cfg directory. Here is an example default script:


DEFAULT menu.c32
MENU TITLE ESXi 5 Boot menu

LABEL install 
 KERNEL mboot.c32 
 APPEND -c boot.cfg 
 MENU LABEL ^ESXi-5 Interactively install

Label ESXi 5 install scripted 
 KERNEL mboot.c32 
 APPEND -c boot.cfg ks=ftp://vmware:vmware@ +++ 
 MENU LABEL ^ESXi5-01 Scripted install 

LABEL hddboot 
 MENU LABEL ^Boot from local disk

If you want to install more VMware ESXi 5 servers you can add extra entries in the default file and point them to separate Kickstart file.

Step 8 Create ks.cfg file

Create a Kickstart file named ks.cfg (Use notepad ++ for the file creation ) and place the file in the c:\PXEboot\Kickstart directory. Here is a sample ks.cfg script:

#Sample kickstart scripted installation
rootpw VMw@re
install --firstdisk --overwritevmfs
network --bootproto=static --ip= --gateway= --nameserver= --netmask= --hostname=esxi5-01.beerens.local --device=vmnic0 --addvmportgroup=0

%firstboot --interpreter=busybox
# Rename local datastore name
vim-cmd hostsvc/datastore/rename datastore1 "$(hostname -s)-local-storage-1"
# DNS names
esxcli system hostname set --fqdn=esxi5-01.beerens.local
esxcli network ip dns search add --domain=beerens.local
# DNS server addresses
esxcli network ip dns server add --server=
esxcli network ip dns server add --server=
# SSH and ESXi shell
vim-cmd hostsvc/enable_ssh
vim-cmd hostsvc/start_ssh
vim-cmd hostsvc/enable_esx_shell
vim-cmd hostsvc/start_esx_shell


Step 9 Test the installation

Boot the server and select ESXi5-01 Scripted Install option to test the scripted installation.





Things to consider when upgrading to vSphere 4.1


The new vSphere 4.1 release offers a lot of new cool features and enhancements. Here’s a list What’s New in vSphere 4.1.  When upgrading to vSphere 4.1 there are a couple of things to think about before starting: