Fog Exit Windows 10
-
Ok I will try this
-
I changed this in the fog settings and it still is not booting
-
I am really wondering if we see a major issue with Windows 10 build 1703 here?! Cross linking the other posts that sound kind of similar to this one: https://forums.fogproject.org/topic/10652/windows-10-1703-won-t-boot-on-sanboot and https://forums.fogproject.org/topic/10386/windows-10-1703-system-error-on-boot
Is anyone able to replicate this issue?
-
@J-Fog I tried with a windows 10 build 1703 install and it booted just fine. Still not sure where things go wrong here but as we seem to have several people with this we should be able to figure this out.
Please edit
/var/www/fog/service/ipxe/refind.conf. Changetimeoutto zero. Save this, change EFI exit type to rEFInd and boot the client. You should see a boot selection menu. Do you see it or does it hang even before that? -
Hi Thanks for your response do you mean the fog boot menu or the bios boot menu? I see the fog boot menu but when that exits it just goes blank apart from the flashing cursor.
-
@J-Fog That’s interesting. There should be another boot menu after the FOG menu that comes from rEFInd (when changing the timeout value to zero). So from what you are saying the handover from iPXE to rEFInd is not working in your case. Really strange!
Please tell us which version of FOG you use and as well please take a picture of the screen when you see the iPXE banner message (the one before “iPXE initializing devices…”) so we know exactly which version you have.
-
@sebastian-roth I too am seeing the exact thing with Window 10 1703 with after fog boot menu all I get is a blinking cursor. My environment is Windows 10 1703 in legacy mode running Fog 1.5.0 RC-8. What information would you like to see? Would it help if I take a video of the boot process so you can see what we are seeing?
-
@ljedi said in Fog Exit Windows 10:
My environment is Windows 10 1703 in legacy mode
I am still wondering if this is all the same issue or several different ones. Can you please try all the different exit style settings. So far I wasn’t able to replicate the issue and I really wonder why so many people seem to have an issue.
-
@ljedi What hardware are you deploying to?
Did you use single disk resizable?
Did you upgrade windows to get to 1703 or did you install it from a newly created reference image?
There has to be something in common here.
-
@george1421 I have not yet created an image for this version yet. 1703 is a clean install and not an upgrade from 1607.
@Sebastian-Roth I will test with the different exit styles and get back with you soon.
-
@ljedi said in Fog Exit Windows 10:
I have not yet created an image for this version yet. 1703 is a clean install and not an upgrade from 1607
This confuses me a bit. Just so I understand what I think you said and didn’t say. You created a fresh install of 1703 that works. But when you add pxe booting first in the boot order, iPXE is not exiting correctly to boot windows? But when you have the hard drive first in the boot order the pc boots correctly??
I just trying to understand the flow here. I want to see if I can duplicate that in our lab, I just need to know how you did what you did.
-
@george1421 Correct. The boot order on the computer is IPXE first. If I take IPXE out of the boot order, Windows boots just fine.
@Sebastian-Roth I switched the HOST Bios Exit Type to GRUB and computer was able to boot into Windows. Thanks.
-
@ljedi said in Fog Exit Windows 10:
I switched the HOST Bios Exit Type to GRUB and computer was able to boot into Windows. Thanks.
Well then in your case I guess you installed windows in legacy BIOS mode but not UEFI mode… Seems this is solved for you then.
But I still have the feeling that we have others here who installed in UEFI mode and have issues booting this way now.
-
@sebastian-roth Correct. My Dell Optiplex 5040’s are in legacy mode. Never had luck with FOG and UEFI always got the “Chainloading” error message that is why they are in legacy mode. Thanks for your help.
-
@sebastian-roth , Hi, I juste upgrated to fog 1.4.4 and I’m having the exit of FOG problem too.
Windows 10 LTSB is installed on our computers and they all boot to network first. It boots out fine on older computer models ex: Dell Optiplex 755 but not on uefi computers ex: HP probook 450G3, on FOG exit, no matter what the host bios exit type is, it won’t boot but if I set the computer to boot from hard disk first it works.
I looked here and there and didn’t find a solution yet.
did you guys found something to solve this?
-
@fog_rob Just so we are clear here. BIOS and UEFI systems have their own exit mode. There are global settings and on per host exit modes. For bios the standard exit mode is SANBOOT, for UEFI systems the default exit mode should be rEFInd. Each firmware type will choose its own exit mode.
-
@fog_rob said in Fog Exit Windows 10:
Hi, I juste upgrated to fog 1.4.4 and I’m having the exit of FOG problem too.
Which version of FOG did you use before? Are you saying that it worked with the old version?
-
@george1421 Thank you for the reply George, but tried that and no go.
I found a solution tho, I had to re install Windwos 10 but before, I removed all Secure boot key management Options and set the secure boot operation to Legacy support enable and secure boot disable
Boot Option to legacy boot Only.
it worked normally after that.
so from now on, I will set all uefi comptuters that way before foging
-
@sebastian-roth , was old FOG .25 and didn’t have UEFIcomputer then. Now with windows 10, it goes way faster to use FOG then our cloning system (SCCM). I posted my solution here explaining how I solved my problem until a better solution is found.
thank you guys for your support, we all appreciate !!!
-
@fog_rob Just for clarity on this issue, fog works perfectly well with uefi systems. You do need to send the right iPXE kernel to the target computer to boot into a FOG uefi iPXE menu. When you have a uefi system you must disable secure boot to allow non-microsoft systems to boot, sometimes turn on the uefi network stack (dells typ) and update dhcp option 67 to send ipxe.efi as the boot kernel name to the target computer. If you do that a uefi system will boot and image without issue. The only exception is typically Dells that will default the disk mode to raid-on. At the moment uefi linux can not boot with the disk controllers in raid-on mode, if you switch the disk mode to ahci then uefi works. This is a limitation we’ve only found so far with Dells and unsupported disk modes.
