I have my ipxe server that works great.
I just have a problem when I want to start my client computers on a winpe image in tftp.
I have to have 2 configurations for legacy positions and for uefi posts. For uefi, I put "kernel wimboot" then "initrd BCD"... For legacy, I have to put "kernel wimboot wimboot" then "initrd BCD BCD" ...
Is it possible to have the same config for all positions in legacy or uefi? Thank you in advance
same config for uefi and legacy
Posted 02 May 2019 - 05:02 PM
Posted 03 May 2019 - 09:05 AM
Config for Legacy :
initrd /tftpboot/bcd BCD
initrd /tftpboot/boot.sdi boot.sdi
initrd /tftpboot/boot.wim boot.wim
Thanks in advance
Posted 05 May 2019 - 12:49 PM
it loads the 4 files well and here is the error after: "bad cpio magic. Fatal: could not extract initrd files".
Posted 05 May 2019 - 12:57 PM
that vaguely rings a bell : wimboot cannot extract files from wimboot.
i remember something about wimboot version.
try latest one and then try them down going one major release down each time (2.6.x; 2.5.x, 2.4.x, etc).
your script is probably fine.
your issues lays with wimboot (releases here).
or else your bcd may be wrong as well in which case you could try this one from ipxe dev team.
Posted 13 May 2019 - 03:02 PM
Finally I completely redo my ipxe server and it works with the same script ...
Here it is:
initrd BCD BCD
initrd boot.sdi boot.sdi
intird BOOT.WIM BOOT.WIM
The only difference is the boot.wim file which is in uppercase. It is true that the one that is contained in the iso of my winpe is written in uppercase.
I guess the problem came from there ...
Posted 13 May 2019 - 03:09 PM
yes i am pretty sure wimboot is case sensitive although i see conflicting feedback here and there.
to be safe, dont test your luck and dont ignore the case
furthermore, the wim name must match the one in your bcd.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users