So I should clarify. These PCs can Legacy PXE boot just fine, and it works with FOG as expected when it boots (I.E: I can select “Deploy” from the menu and image it, as well as set a deploy or capture task and then it will automatically start imaging when I go and manually PXE boot). The real issue is that the FOG client isn’t booting into the hard disk when the default (
fog.local) option is called. I haven’t been able to get it to work at all with any exit type, on both BIOS and UEFI options.
Now also to clarify, when
Legacy + UEFI is selected, the traditional PXE boot as well as the UEFI Windows Boot Manager are both available, so there theoretically should be nothing stopping FOG from seeing that, at least in my eyes.
So is the issue then that the FOG client over the Legacy PXE boot is a different client that can only see Legacy boot devices (I.E: the HardDisk and not Windows Boot Manager)? Do you think that UEFI Network booting with those DHCP changes will allow the FOG client to see the disk for some reason?
I’ve dug all over the internet for FOG not booting into Windows and the best I could find were unresolved posts on this forum.
Also, here are the MoBo/BIOS specs for these PCs: