problems Loading Windows iso in advanced menu.
-
@sacha-marin I’ll be working on converting this to a WiKi article in the future. Excellent work, Bravo!
-
@Wayne-Workman Noice. Tell me if you need more info. im not the best at documenting.
-
Hi, I have the same problem, but not in all computers.
Some computers work fine, and load WinPE correctly.
But others computers loaded at 100% iso file, and did a self restart.
Someone with a idea ?
I cheked cables and switches too.
-
@Rayco I have a tutorial for loading the winpe iso image, let me link it in here.
https://forums.fogproject.org/topic/6284/booting-mdt-2013-litetouch-with-fog
The other thing you need to be aware of with your winpe image is that you have all of the winpe hardware drivers embedded into the iso image or some systems may fail to boot. You also need to be mindful of the bios (firmware) settings to ensure they are the same between the winpe booting devices.
-
@george1421 Thank you for ur fast answer.
All computers have bios updated and WinPE’s has drivers incluided.
I got a screenshot with the trouble. I think we have a problem with a trunked image when go to mapped in memory. (But not all computers fails, several do it nice)
Maybe we have a problem with image or drivers?
Thank you a lot.
-
@Rayco This is an interesting puzzle.
- The system boots one some and not other systems.
- You are using the same WinPE image for all
- I assume you’ve confirmed that the iso image on the FOG server is exactly the same as in your windows environment by using md5sum utility in both environments and compared signatures??
Do you have 2 computers of the same model where 1 works and 1 doesn’t?
If so have you compared the firmware settings?
Are these systems all uefi or bios (legacy) format?
Are the systems with error in one geographic network location?
Any other times you can think of where we could draw a conclusion?On a side note (not related to your problem) you can eliminate the pause at the bottom of the boot (as in your picture) by removing a file from your iso image. If you remove /boot/bootfix.bin the iso image will boot without the pause of “Press any key to boot from CD or DVD…”
-
@george1421 Thanks for your interest.
We have one WinPE for each Laptop model. In some models work fine, in other not, but in one cd bootable work fine in all.
Each one has his own WinPE, some models use the same WinPE.
Yes, they have the same size in bytes.
When one model work fine, work fine in all of the same model.
We think the problem is on some hardwares configurations.I will test your suggestion of remove bootfix.bin.
-
@Rayco If One model is broken, does all of the same model also fail? (Or multiples of the same model more accurately.)
-
If one model fail, all of this models fails too. But if burned in to bootable cd, work fine.
Thank you a lot.
-
@Rayco I don’t know how you created the menu, but maybe this can help:
http://ipxe.org/howto/winpe -
@Rayco Can you share the PXE boot commands you have?
-
initrd http://${fog-ip}/fog/service/ipxe/iso/asus/TOOL_NB64_W10GPT_V1.3.3.iso chain memdisk iso raw || goto MENUThis is a config menu.
@Tom-Elliott
If some computers work well, I must think that those that do not work is by the configuration of ipxe?I will check it, in few hours I answer you.
-
@Rayco said in problems Loading Windows iso in advanced menu.:
initrd http://${fog-ip}/fog/service/ipxe/iso/asus/TOOL_NB64_W10GPT_V1.3.3.iso
Not specifically related to your issue, but I wouldn’t place your files in the FOG package path if you want your files to survive an update. I would recommend you move the iso director to a root level directory on your fog server. i.e. http://${fog-ip}/fog/service/ipxe/iso -> http://${fog-ip}/iso
-
@Rayco I would try the wimboot way that’s listed on iPXE website if I were you. I find it this is far more successful to boot WinPE than trying to boot the ISO
-
@Rayco said in problems Loading Windows iso in advanced menu.:
TOOL_NB64_W10GPT
Just hacking your file name here. So all of these systems you are pxe booting are in uefi mode? If so we have seen some pretty flaky uefi firmware especially on Lenovo systems. I’m not saying this is your issue, just we have seen the issue. It is the handoff between either PXE rom and iPXE or between iPXE and FOS.
There is also another way to pxe boot instead of an iso image (I understand that is desirable for portability). In the link I previously posted, there is an second method for pxe booting into WinPE: https://forums.fogproject.org/topic/6284/booting-mdt-2013-litetouch-with-fog/6 I’m not suggesting this will fix your issue, but its something you could try.
-
Thanks you guys, I appreciate your advice, I will change the path of the iso folder, adopt wimboot system, and will check it tonight.
THX a lot !!!
-
Hello guys.
Finally, with wimboot systems work fine in all computer.
This was the code:
#!ipxe cpuid --ext 29 && set arch amd64 || set arch x86 kernel http://${fog-ip}/iso/asus/133/wimboot initrd http://${fog-ip}/iso/asus/133/BOOT/BCD BCD initrd http://${fog-ip}/iso/asus/133/BOOT/BOOT.SDI boot.sdi initrd -n boot.wim http://${fog-ip}/iso/asus/133/SOURCES/BOOT.WIM boot.wim bootThank all, a lot.
