@george1421 Thank you for the response and the pointer to previous thread on examples of how to branch the iPXE menu with the platform option. With this info, I am thinking along the lines of customizing the default.ipxe to present different menu based on the platform field. I will explore this method and see how far I can take it on presenting separate menu for legacy vs UEFI clients.

Hello,

I am working on automating os deployment for a lab setup. There are multiple systems that need to be imaged based on the host OS needs (mostly a lab test env). Some OSes need to be presented for UEFI only clients (for example rhel9.x) and some OSes only for legacy BIOS clients (for example windows server 2016). I created multiple entries under “iPXE Menu Customization” but all entries created are shown to all clients that boot to FOG PXE. I have a separate DHCP server which points to fog pxe server as “next-server”. DHCP server has class entries to point filename “undionly.kkpxe” or “ipxe.efi” based on PXE client arch. But once those are loaded on the client, it looks like default.ipxe is chain loaded which points to the same PXE menu for all clients. Does anyone know how to customize the FOG boot menu to present separate entries for UEFI vs legacy bios clients?

Please let me know if anyone has any pointer or help for this.
Yonatan