@Sebastian-Roth Sounds good to me.
Thank you for your help here, I appreciate it a ton! Off to tackle AD joining so I’ll catch ya around.
Also, to the powers that be - I’m not sure how to mark this as solved.
@Sebastian-Roth The global settings I’ve been using are REFIND_EFI for both.
I do not have any host specific settings.
This client did however have the following enabled in the BIOS.
Without changing FOG boot exit types, I changed the UEFI/Legacy Boot to: UEFI Only. PC booted right away.
Changing the BOOT EXIT TYPE to EXIT (with UEFI/Legacy Boot back to the above screenshot setting), results in chainloading failed. Tried GRUB and GRUB_FIRST_FOUND_WINDOWS and both failed - assuming GRUB will fail here since this is Windows (again, sorry the the lack of knowledge in the area).
Further answers to your questions: No, The FOG menu did not load prior to my change in the client BIOS. I do have other clients PXE booting and have only seen the original timeout error happening on a Dell Desktop client.
I guess my question now is, do Windows PCs need to have Legacy boot disabled? I believe I read about this somewhere in the FOG wiki however can’t find it now.
To answer your first question - This is the normal boot process I’ve seen prior to the device hitting the FOG menu. I’ve seen all my devices pull the above files.
I wish I could answer your second question confidently, however I’m still fairly new to this legacy/uefi bios PXE booting world.
I have an intermittent issue with clients. I’ve successfully captured and deployed images on different machines, however sometimes I will randomly run into the below. The only fix I’ve found so far is to remove the host from the GUI and re-register. This has happened pre and post-registration, as well as pre and post deployment. Everything is fine up until here and the system will hang indefinitely.
It’s more of a bother to me that a real issue, since I seem to have found a work-around, however I’d love some insight on this. Having a hard time searching the issue as it’s not directly related to the boot exit types.
Thanks in advanced.
Edit: Has happened on Lenovo and a Dell machine. Workaround the same for both.