The host you provision with vSphere Auto Deploy fails to get a DHCP Address.
When you attempt to boot a host provisioned with vSphere Auto Deploy, the host performs a network boot but is not assigned a DHCP address. The vSphere Auto Deploy server cannot provision the host with the image profile.
You might have a problem with the DHCP service or with the firewall setup.
- Check that the DHCP server service is running on the Windows system on which the DHCP server is set up to provision hosts.
- Click .
- Double-click Services to open the Services Management panel.
- In the Services field, look for the DHCP server service and restart the service if it is not running.
- If the DHCP server is running, recheck the DHCP scope and the DHCP reservations that you configured for your target hosts.
If the DHCP scope and reservations are configured correctly, the problem most likely involves the firewall.
- As a temporary workaround, turn off the firewall to see whether that resolves the problem.
- Open the command prompt by clicking .
- 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
- Attempt to provision the host with vSphere Auto Deploy.
- Type the following command to turn the firewall back on.
netsh firewall set opmode enable
- 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.