WDS, iPXE, DHCP and SecureBoot
|
2017-01-11, 20:00
Post: #2
|
|||
|
|||
RE: WDS, iPXE, DHCP and SecureBoot
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. Use GitHub Discussions VRAM bin |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
WDS, iPXE, DHCP and SecureBoot - abos_systemax - 2017-01-11, 16:24
RE: WDS, iPXE, DHCP and SecureBoot - NiKiZe - 2017-01-11 20:00
RE: WDS, iPXE, DHCP and SecureBoot - abos_systemax - 2017-01-12, 09:35
RE: WDS, iPXE, DHCP and SecureBoot - ndog - 2017-01-12, 12:10
RE: WDS, iPXE, DHCP and SecureBoot - NiKiZe - 2017-01-12, 19:11
RE: WDS, iPXE, DHCP and SecureBoot - abos_systemax - 2017-01-13, 07:13
RE: WDS, iPXE, DHCP and SecureBoot - NiKiZe - 2017-01-13, 18:18
|
User(s) browsing this thread: 3 Guest(s)