Setting up my 2012R2 DHCP server to handle UEFI and BIOS PXE boot, and I need some help.

[Yeet]

To start, I’m following the following link to setup UEFI and BIOS to PXE boot correctly:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

I have the vendor classes setup, but I’m not sure what architectures to assign to bootfiles. For example, I’ve had ipxe.efi work 99% of the time, but there’s some models that only snp.efi and snponly.efi work on. As a result of this, I’m skeptical what bootfile I’m supposed to use for each architecture.

Just looking for guidance to see what has worked for others, because the tutorial I sent a link for only includes instructions for PXE client architecture 00007. Any help/ suggestions are appreciated. I want to make sure I have everything setup correctly before I put this in a live environment

[Sebastian Roth]

@yeet said in Setting up my 2012R2 DHCP server to handle UEFI and BIOS PXE boot, and I need some help.:

I’ve had ipxe.efi work 99% of the time, but there’s some models that only snp.efi and snponly.efi work on.

The issue is that those models having an issue with ipxe.efi use the same vendor class than the others and can’t be distinguished from the by vendor class identifier.

I am not very good with Windows DHCP server but in generel you’d setup a particular rule/policy for problematic clients using their MAC address to distinguish those from other machines.