WDS, iPXE, DHCP and SecureBoot

[abos_systemax]

(2017-01-11 20:00)NiKiZe Wrote:  SecureBoot is only relevant in the case where the client boots in EFI mode, as such you can look at http://ipxe.org/howto/chainloading#uefi where a simple example is made about how the dhcp arch option is used to determine if a pcbios compatible version of ipxe should be sent or a efi compatible one.

so what you would probably like to do is to always boot ipxes undionly.kpxe in legacy/pcbios mode, and in efi mode chain into the wds.efi

Even if you can detect EFI or not as a base with the above mentioned arch option, there is no option or detection AFAIK in dhcp for if secure boot is enabled or not.

And mandatory question: you are aware of wimboot which makes it possible to boot winpe via http download? which is probably many times faster then the default WDS TFTP method.

I am indeed aware of Wimboot; but the problem is that ipxe is not allowed to load when secureboot is enabled; Since we sometimes only wish to boot devices to Windows PE for registration and thus do not need to disable secureboot (because WDS can handle that), I need some means to redirect (only those) clients to WDS.

What we were doing in the old situation, was redirecting DHCP to WDS (next-server to the WDS server) and then set the boot program from WDS to pxelinux.cfg; is there a similar method known for IPXE?