@george1421 Finally figured it out. I feel like an absolute idiot, but I’m blaming Microsoft for a big portion of it.

The “Policies” under IPv4 MUST be enabled, even if there are no policies under that folder. That fixed the problem completely.

By default, this was disabled, and since I did not have policies in that particular folder, I did not see the need to enable it.

@george1421 Finally figured it out. I feel like an absolute idiot, but I’m blaming Microsoft for a big portion of it.

The “Policies” under IPv4 MUST be enabled, even if there are no policies under that folder. That fixed the problem completely.

By default, this was disabled, and since I did not have policies in that particular folder, I did not see the need to enable it.

I’ve been doing a lot of reading about DHCP polices and such, and I still have no idea why this is not working. I’ve followed multiple other guides, with no change. It’s like the policy is just not enabled or something (however, it clearly is).

A lot of people have suggested using IP helpers instead of DHCP policies. Does anyone know what this is? I have tried researching it, but I can’t seem to figure out what it is.

@george1421 Yes, the IP is of the main (only) DHCP server.

I removed the :UNDI:003016 policy and class, since, like you said, its redundant and too specific.

I just confirmed the DHCP offer’s IP, and it is indeed on the same network as the policy is applied to on my DHCP server.

I also checked my firewall to make sure it was not blocking anything. It does not appear to be blocking any traffic between the test PC and the DHCP server.

Any other ideas? I feel like I’m missing something basic, but I have gone over the settings many times and it looks right.

@george1421 Ok, I just installed Wireshark and did as you suggested. The Arch type is: PXEClient:Arch:00007:UNDI:003016

I added a new Vendor Class and created a new policy with it, and then reran the test, but I got the same result - the DHCP server sent undionly.kpxe.

Here are some screenshots:

@george1421 I guess I just don’t get it. I have the DHCP settings exactly like yours, down to the descriptions for the Vendor Classes. My polices are also only applied to a single scope, not the IPv4 global policies.

Here are the current screenshots:

I also tried UEFI PXE booting on a Probook 440 G5, and it did not work. It’s like the polices are just doing nothing at all, which makes no sense.

Thanks again for your help!

@george1421 I actually had my vendor classes named similarly to the Arch number before. I just removed all of them and copied exactly what you have in the screenshots you sent. Here is what it looks like now:

It still doesn’t seem to work on the 3080:

@george1421 Ok, I fixed that. I removed my current policy, and created two new policies. I didn’t change any of the Vendor policies. I just made policies for 00007 and 00009 for now.

This is what it looks like now:

Does this look like it should work? I tested it with the Dell 3080, and it still gets the undionly.kpxe file, not the ipxe.efi.

Thanks again!

@george1421 Ok, here are some screen shots showing the DHCP setup:

Thanks!

@george1421 Sorry for being unclear. I changed my default option 67 to ipxe.efi, just to make sure my new machines could PXE boot via UEFI, which they can. I then switched it back to undionly.kpxe and followed the coexistence guide. Now I can boot into PXE via BIOS, but not UEFI. It seems as though the changes I made on the DHCP server are not doing anything at all. I can provide screenshots of my DHCP settings if you would like. Thanks!

Hello. I have been using FOG for a few years now in my environment, and its been working great. I have using it to deploy Windows UEFI images using BIOS PXE. I just switch the PC to BIOS, deploy the image, and then switch it back to UEFI. This has worked great until I recently got some new devices that no longer support BIOS/Legacy booting. So now I would like to have PXE booting for both PXE and BIOS.

I have read, and followed the UEFI/BIOS Coexistence guide, but I can’t seem to get it to work in my environment. Just for testing, I changed the default option 067 to ipxe.efi, and my new machines boot to PXE just fine. I am using a Windows Server 2016 for DHCP. The devices I would like to have boot to UEFI PXE are a Dell 3080, and an HP Probook 440 G8.

Thanks for your help!