Family, Your advice worked perfectly!

OK… So based on the excellent instructions here I tried a different Dell laptop and it worked with “undionly.kpxe” as option 67. Didn’t like “ipxe.efi”. So then I continued with the outstanding advice and upgraded the firmware on our Lenovo laptops and they worked great as long as I had “Legacy first” enabled under the UEFI.
So I am up and running 100% right now.

The fix for my specific issue in summary :

• Make sure that DCHP Scope option 66 has Fog Server IP
• Set Option 67 to be “undionly.kpxe”
• Firmware updates on any systems that won’t connect.

@sebastian-roth
Thanks. I will try a Dell and Lenovo tomorrow as well as firmware upgrades.

These are Lenovo laptops. I will try a Dell tomorrow based on these comments and also try firmware upgrades.
Bios setting is “both” with uefi first, then legacy.
I can tftp both files successfully from a linux server. None of these are virtual. All physical.

Server

• FOG Version: 1.4.4
• OS: CentOS 7

Client

• Service Version:
• OS:

Description

I have FOG running and am trying to boot machines into PXE so that I can register them.
Windows Server 2008 R2 DHCP server.
Scope attributes #66 set to FOG server IP
Scope attribute 67 set to ipxe.efi (I tried undionly.kpxe as well. Same result)

When I boot my systems using PXE I see that it tries to reach out to my fog server and download the ipxe.efi file but it returns that it is 0 KB. Gets PXE-99 error.
I can log into a Linux machine and tftp both the ipxe.efi and undionly.kpxe files without an issue.
What am I missing? I had this working a couple of months ago and loaded FOG onto a new server from scratch and am getting this error.
All machines are on the same VLAN (same switch)
I can ping the FOG server and leverage the web management console normally as needed.