Can capture windows 10 host. But when I deploy it won't boot. Just get blue Screen. Dell UEFI boot
-
@spooninbrian FOG does not capture and deploy UEFI boot entries. Though this does not cause any trouble for most people because almost all UEFI firmware is intelligent enough to still find the Windows EFI boot loader file!
Can you take a picture of the blue screen you get and post here?
-
It’s literally just a blue screen then it cuts back out.
I’m going to reimage using the Dell OS recovery as that reset the BIOS for another machine.
I’m really new to all of this. Reimaging another machine that had the same issue with Dell Recovery OS fixed the boot order in the Bios. I’m going to try to the same on this machine I deployed to and see if that fixes it. I will then attempt another deploy.
I’m not sure what to do for the BIOS exit.
Here is what I have currently.
-
@spooninbrian BIOS Exit type really should be sanboot or exit. REFIND_EFI is specific to the UEFI/EFI implementation. BIOS is legacy style boot systems.
-
I think this may be my issue.
It’s UEFI Boot, not BIOS but the terminology is loosely used.
So if it’s a UEFI boot loader using GPT then I should use REFID_EFI for the capture and deployment?
-
@spooninbrian That’s kind of redundant (just informing lol)
UEFI Boot will Always need GPT for the hdd parition table.
If your machines are already booting in UEFI mode, then you’re using the EFI Exit Type.
I’m just trying to ensure the configuration is proper for both Legacy and UEFI. It’s not that much an issue if you know all machines are booting using UEFI.
-
@spooninbrian said in Can capture windows 10 host. But when I deploy it won't boot. Just get blue Screen. Dell UEFI boot:
So if it’s a UEFI boot loader using GPT then I should use REFID_EFI for the capture and deployment?
Yes, set the exit type to REFIND in your case I would say. But be aware this setting has nothing to do with deploy/capture but is telling the client machine what to do if there is no task scheduled for it. A.K.A chainload from disk.
-
Okay,
I just captured and deployed using the REFIND_EFI exit method and the windows boot manager is not there now.
I can boot to the OS from the FOG menu, but if I attempt to just boot from the Hard Disk it does not boot.
I was using EXIT prior to this.
-
So I figured out what the deal is.
When I use REFIND_EFI, I have to pxe boot into the FOG Client menu, then select boot from Hard Disk, which then creates the windows boot manager back into the UEFI allowing windows to boot again.
-
@spooninbrian said in Can capture windows 10 host. But when I deploy it won't boot. Just get blue Screen. Dell UEFI boot:
then select boot from Hard Disk, which then creates the windows boot manager back into the UEFI allowing windows to boot again.
What happens is that it PXE boots the machine and then “chainloads” back to the local hard drive. It’s not actually creating the UEFI boot manager entry.
I can boot to the OS from the FOG menu, but if I attempt to just boot from the Hard Disk it does not boot.
It’s interesting that some machines just don’t find and use the Windows UEFI boot loader by itself. If you want to boot those machines without PXE chainloading you’d need to create the UEFI entry using post deploy scripts. Let us know if you want to do that and we can give you the details on this.
-
Thanks guys! You all have been so helpful. I figured out that you don’t have to select the FOG Boot screen to select the Hard drive boot. It goes right into pxe.
It’s cut our deploy time from an 1 hour and 15 - 30 minutes to like 10 minutes.
If it becomes a further issue I’ll keep the post deploy scripts in mind.
Thanks again!
