Configure the offboard DHCP server

When you turn on a device for the first time, you can select the NIC or Network Boot option from the BIOS boot menu. Windows deployments require target devices to boot from somewhere other than the local drive. When you select the NIC or Network Boot option, the device sends an PXE request to the DHCP server to locate the iPXE server. In this case, the appliance is the PXE server. You can configure an offboard DHCP server to acknowledge the appliance to enable target devices to UEFI boot from the appliance.

The steps might vary depending on which DHCP server you are using. Use the following settings for options 066 and 067 on any DHCP server.

If you are not using the Microsoft DHCP, see the following Knowledge Base article for additional information: https://support.quest.com/kace-systems-deployment-appliance/kb/112037

1.	Open the configuration application for your DHCP server.

2.	Set the following options for each subnet or scope that you want target devices to be able to boot from the appliance:

◦	Set Option 066 to the IP address of the appliance.

This option might appear as Next-Server, Boot Server Host Name or TFTP server name.

NOTE: You might not be able to set Option 66 on some Cisco networking equipment. As an alternate configuration, you can set the sname and 244 options to the appliance IP address.

◦	Set Option 067 to the string ipxe.efi (for UEFI devices), and undionly.kpxe (for BIOS devices).

This option might also appear as Boot File Name. Copy and paste the ipxe.efi or undionly.kpxe string as the Boot File Name option.

NOTE: You can only have one PXE or TFTP server on a subnet. Disable other imaging tools on the subnets where you want to test the appliance.

The DHCP server automatically redirects PXE-compliant Windows devices to the appliance the next time the devices start up while connected to the network. The devices download the bootstrap file, and use the environment setup to boot.