[Solved] Boot to ipxe on UEFI machine to menu
|
2017-02-03, 13:43
(This post was last modified: 2017-02-12 21:23 by sebus.)
Post: #1
|
|||
|
|||
[Solved] Boot to ipxe on UEFI machine to menu
I have a simple setup of
server1= SCCM 2012 R2 server2= MS DHCP server MS DHCP option 66/67 are configured for ipxe clients (legacy) to boot to undionly.kkpxe created with embedded script that does: #!ipxe dhcp net0 set 209:string pxelinux.cfg/default set 210:string http://sccm.domain.com/tftpboot/ chain ${210:string}pxelinux.0 That works perfect for legacy PXE boot Tried to follow DHCP policies as per: https://wiki.fogproject.org/wiki/index.p...HCP_Policy to get it boot to ipxe.efi (build from source with same script) from EFI network boot on physical hardware But none of my attempts was ever successful each time such machine boots directly only to SMSBoot\x64\wdsmgfw.efi from SCCM server I do NOT think using DHCP only options is even possible with MS DHCP (no matter what somebody else says, but please prove me being wrong) http://www.wardvissers.nl/2016/02/12/don...-with-mdt/ Anybody any ideas how/what to change to make it boot to the menu? (but still have WDS, as it must be used for SCCM to do imagining) sebus |
|||
2017-02-03, 23:42
Post: #2
|
|||
|
|||
RE: Boot to ipxe on UEFI machine
Hi a few things i wish to comment on..
Why are you using undionly.kkpxe ? it might cause you some grief and you might want to use undionly.kpxe instead. You will want to have a bootx64.efi (ipxe.efi) that you load when arch is efi, For the windows DHCP it is some poorly documented magic somewhere that you need to change. Maybe something from 2pint sw could help you identify how to do this: quick google gave me: https://2pintsoftware.com/whitepaper-usi...e-booting/ Use GitHub Discussions VRAM bin |
|||
2017-02-04, 14:17
(This post was last modified: 2017-02-12 16:45 by sebus.)
Post: #3
|
|||
|
|||
RE: Boot to ipxe on UEFI machine
Been using undionly.kkpxe for years, as it was the only one that worked in my tests with pxelinux.0 menu
Never had major problems with any cards that I was using. Thanks for the link, this document is not any different than the link I provided already, and somehow I can not get it behaving that way... 2pintsoft pdf states: 7 EFI BC boot\x64\wdsmgfw.efi smsboot\x64\wdsmgfw.efi Definbitely NOT what I see in my setup my UEFI machines only boot from \Boot\x64\wdmgfw.efi from SCCM server without any special config (as I can not even figure out where to config that setting!) |
|||
2017-02-07, 13:56
(This post was last modified: 2017-02-11 17:30 by sebus.)
Post: #4
|
|||
|
|||
RE: Boot to ipxe on UEFI machine to menu
No, can not make it boot via DHCP options.
Have them configured exactly as per pdf, but now ONLY boot happens from smsboot\x64\wdsmgfw.efi (tested on Gen2 Hyper-V VM) - that is due to ProxyDHCP WDS replying (if I disable it, then DHCP options are not used at all!) I have Policy for UEFI based network booting with Vendor Class PXEClient (UEFI x64) as PXEClient:Arch:00007 configured and specified option 67 in that Policy Yet, UEFI client takes no notice at all of these settings sebus |
|||
2017-02-09, 10:16
(This post was last modified: 2017-02-09 16:08 by sebus.)
Post: #5
|
|||
|
|||
RE: Boot to ipxe on UEFI machine to menu
Anybody having any ideas why that does not work?
BIOS legacy network boot with Policy PXEClient:Arch:00000 works OK, but UEFI network boot via Policy PXEClient:Arch:00007 gets ignored & only SMSBoot\x64\wdsmgfw.efi gets pulled from TFTP server sebus |
|||
2017-02-09, 17:14
(This post was last modified: 2017-02-11 19:35 by sebus.)
Post: #6
|
|||
|
|||
RE: Boot to ipxe on UEFI machine to menu
I can "cheat" and rename ipxe.efi to wdsmgfw.efi (which is only good till WDSServer service restarts - as it copied back the original file!)
("hardcoded" SMSBoot\x64\wdsmgfw.efi comes form ProxyDHCP of WDS reply) That way it will boot to ipxe from UEFI network stack fine, but get error 0xc000000f I have been doing wimboot via legacy PXE for years (with ipxe--> pxelinux.0 menu) Now I need to move to UEFI, so the whole lot gets re-designed So created new EFI BCD Code: #Create a BCD store using bcdedit.exe: UEFI PXE IPv4 boots fine to iPXE menu, all wimboot-2.5.2-signed files get downloaded: Code: #!ipxe at which point it dies with error EFI\Microsoft\Boot\BCD 0xc000000f Obviously the BCD is there (downloaded), so have no idea why it fails BCD is being read, as I can chose the correct Windows Boot Manager by Enter at error screen (which then fails again) sebus |
|||
2017-02-12, 21:11
Post: #7
|
|||
|
|||
RE: Boot to ipxe on UEFI machine to menu
SOLVED (with help from Misty on reboot.pro)
In uefi mode, wimboot does not appear to tolerate files with different than expected being mapped. It is expecting boot.wim and the original file being mapped as boot.wim must also be named boot.wim. E.g. Code: initrd http://10.0.0.55/wim/wim/Win10PESE_x64.WIM BOOT.WIM . Will not work. However... Code: initrd http://10.0.0.55/wim/wim/Win10PESE_x64/BOOT.WIM BOOT.WIM . ....does work fine. |
|||
2017-02-12, 22:03
Post: #8
|
|||
|
|||
RE: Boot to ipxe on UEFI machine to menu
(2017-02-12 21:11)sebus Wrote: SOLVED (with help from Misty on reboot.pro) What you need here is Code: initrd -n boot.wim http://10.0.0.55/wim/wim/Win10PESE_x64.WIM BOOT.WIM If you don't want to create a BCD by yourself you can use the one at https://github.com/NiKiZe/wimboot-bcd/bl...gen/PXEBCD in that repo is also script to generate it from scratch and examples of how to use bcdedit. and for your scripts Code: #!ipxe bootmgr is extracted from provided wim, and -n is "missing" on lots of lines. but in reality you only need: Code: #!ipxe example script with all files available over ipfs: http://ipfs.io/ipfs/QmWhRKfSy9s3fRaNVTJN...eDbPdUREow Use GitHub Discussions VRAM bin |
|||
2017-02-14, 09:17
Post: #9
|
|||
|
|||
RE: [Solved] Boot to ipxe on UEFI machine to menu
@NiKiZe
Using the initrd -n switch is working - I can't find any reference to this switch anywhere though. Please can someone explain a bit more about this switch. And also any other undocumented wimboot switches that might be useful. Regards, Misty |
|||
2017-02-14, 12:45
Post: #10
|
|||
|
|||
RE: [Solved] Boot to ipxe on UEFI machine to menu
(2017-02-14 09:17)misty Wrote: Using the initrd -n switch is working - I can't find any reference to this switch anywhere though. -n is short for --name option to initrd which is used in efi to set "local" name of the file in EFIFS, documentation is available at http://ipxe.org/cmd/imgfetch in regards to which options the wimboot binary takes you can take a look at http://ipxe.org/wimboot and http://ipxe.org/appnote/wimboot_architecture Use GitHub Discussions VRAM bin |
|||
2017-02-14, 18:46
Post: #11
|
|||
|
|||
RE: [Solved] Boot to ipxe on UEFI machine to menu
(2017-02-14 12:45)NiKiZe Wrote: ...in regards to which options the wimboot binary takes you can take a look at http://ipxe.org/wimboot and http://ipxe.org/appnote/wimboot_architecture...Thanks. Having re-read the wimboot_architecture page in conjunction with your post(s) I understand it a bit more. Cheers. Misty |
|||
2020-05-13, 19:42
Post: #12
|
|||
|
|||
RE: [Solved] Boot to ipxe on UEFI machine to menu
.
Thanks Misty... your '-n' was a time-saver... and tanks Nikize for the well formulated questions... . |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)