@george1421 Today’s findings:

autoexec.ipxe is getting loaded by some default somewhere (not because of my dnsmasq entry) and it’s completely ignored. None of its contents get run. I confirmed the correct autoexec.ipxe file is actually being loaded by renaming it, attempting a boot, and observing a ‘file not found’ error message. I pulled bzImage and init.xz directly from the latest release and N-1 https://github.com/FOGProject/fos/releases to ensure compatibility. No change. This server’s NIC does not support the native iPXE drivers. Only snponly.efi works.

No joy 😞

@CanadienITGuy Just for your and anyone’s fyi the autoexec.ipxe... Not Found is not an error. It’s more of an info message than a warning or error.
I actually have tested adding an autoexec.ipxe, even just an empty file to remove that message but even an empty file or a file that is even just a symlink or copy/paste of our normal ipxe/boot menu files causes things to break in the process.
The autoexec.ipxe is meant for adding customization to the ipxe process without needing to re-build the ipxe binary. But my testing with it within the fog workflow was that it’s best to just let that message exist and to see it as it being not found means the process will not be altered from your expected Fog ipxe workflow