In this article, we will see how to configure the DHCP service so that you can use WDS to install Windows on computers with UEFI enabled, which is the case for Generation 2 virtual machines on Hyper-V.
In a “standard” Active Directory deployment where DHCP and WDS services are installed on different servers that are members of the domain, no configuration is required to boot on the network (PXE) with computers that do not use UEFI.
In an environment where multiple configurations coexist, a DHCP server configuration is required for the network boot to work without the need to disable UEFI on computers
DHCP service configuration
Option 60 – PXEClient
Option 60 must be added to the DHCP server only if it has the WDS role installed.
By default this option is not available the list.
To add it open a command prompt as administrator on the DHCP server and enter:
netsh netsh>dhcp netsh dhcp>server netsh dhcp server>add optiondef 60 PXEClient STRING 0 comment=option added for PXE Support netsh dhcp server>set optionvalue 60 STRING PXEClient
Configuring a UEFI Provider Class
The classes allow users and providers to create policies based on the DHCP lease requestor identification, which will allow us to identify the request from a UEFI PXE boot.
Configure a policy
Configure the condition as shown below:
- Criteria: Provider Class 1
- Operator: Is equal to 2
- Value: select the supplier class previously added 3
- Check the box Add a wildcard (*) 4.
Click on Add 5.
Now, we will configure DHCP options 66 and 67 to indicate the PXE server and the boot file.
The different boot images are located in the RemoteInstall \ Boot \ <version> \ * folder on the WDS server.
WDS services do not normally require DHCP configuration, and by experience the PXE boot responds more quickly with this configuration on machines with UEFI enabled.