WDS, iPXE, DHCP and SecureBoot
|
2017-01-12, 12:10
Post: #4
|
|||
|
|||
RE: WDS, iPXE, DHCP and SecureBoot
(2017-01-12 09:35)abos_systemax Wrote: For SecureBoot enabled devices, I'd like to always boot to WDS If you insist on having a boot loader like syslinux, grub2 or ipxe you will have to disable secure boot on all machines as they come into the workshop. Until a time that ipxe.efi + wimboot is secure boot enabled, you will have to configure your DHCP server to serve Boot\x64\wdsmgfw.efi (from WDS) to clients in EFI mode. There are other boot loaders, AFAIK grub2.efi is the only secureboot enabled EFI booter, but currently fails to chainload WDS or wim files anyway, even after modifying BCD and other various options, plus is buggy, painfully slow, and cant timeout, exit then boot from the local disk (which ipxe can) With your current setup modify your existing dhcp scope to something like this (example for isc-dhcpd) Code: option space pxelinux; untested |
|||
« 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: 2 Guest(s)