7.0

Table Of Contents
3 As a temporary workaround, turn off the firewall to see whether that resolves the problem.
a Open the command prompt by clicking Start > Program > Accessories > Command
prompt.
b Type the following command to temporarily turn off the firewall. Do not turn off the firewall
in a production environment.
netsh firewall set opmode disable
c Attempt to provision the host with vSphere Auto Deploy.
d Type the following command to turn the firewall back on.
netsh firewall set opmode enable
4 Set up rules to allow DHCP network traffic to the target hosts.
See the firewall documentation for DHCP and for the Windows system on which the DHCP
server is running for details.
vSphere Auto Deploy Host Does Not Network Boot
The host you provision with vSphere Auto Deploy comes up but does not network boot.
Problem
When you attempt to boot a host provisioned with vSphere Auto Deploy, the host does not start
the network boot process.
Cause
You did not enable your host for network boot.
Solution
1 Reboot the host and follow the on-screen instructions to access the BIOS configuration.
2 In the BIOS configuration, enable Network Boot in the Boot Device configuration.
Recovering from Database Corruption on the vSphere Auto Deploy Server
In some situations, you might have a problem with the vSphere Auto Deploy database. The most
efficient recovery option is to replace the existing database file with the most recent backup.
Problem
When you use vSphere Auto Deploy to provision the ESXi hosts in your environment, you might
encounter a problem with the vSphere Auto Deploy database.
Important This is a rare problem. Follow all other vSphere Auto Deploy troubleshooting
strategies before you replace the current database file. Rules or associations that you created
since the backup you choose are lost.
VMware ESXi Installation and Setup
VMware, Inc. 211