Because? and who? change Sequence boot UEFI?

[Gilberto Ferraz]

Hi, I’m using fog to manage more than 100 machines in my company, the machines have different hardware.

I use Centos 7.0 and Fog 1.5.7, everything works fine, I just have a little problem.

I set up dnsmasq on the fog server by following this link https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

I configure the BIOS of my UEFI machines to boot to 1 option with ipxe (machines can handle fog tasks)

If you deploy, the machine starts up with the task and everything works fine.

The problem is that the boot sequence in the BIOS changes without me doing anything.

In order to manage all these machines I need that even after deploying an image of an Operating System, the machines will continue booting with IPV4 in 1 Option

I found someone with the same problem here on the forum https://forums.fogproject.org/topic/13775/boot-option-issue-pxe-booting/10 but the Dell CCTK tool doesn’t work with me because I don’t have dell machines.

I don’t know if it’s FOG that changes UEFI’s sequence boot, or if it’s really Windows 10

Thanks for the help you can give me

[george1421]

Just be aware with uefi machines, windows has the ability (and will) change the boot order to make windows boot manager first in the list. This is a Microsoft thing and not something that FOG is doing.

How can you tell? Right after imaging but before windows OOBE start, go into the firmware and look at the boot order. If FOG was doing it, right then it should be pointing to the windows boot manager. But since FOG is not doing this (AFAIK) it still should be pxe boot. But then look at it after windows OOBE runs, my bet it will be windows boot manager, thank you microsoft. So why doesn’t this happen for bios computers? Because bios doesn’t have the ability for the operating systems to change the boot order.

[Sebastian Roth]

@Gilberto-Ferraz I might add posts from other users seeing the same thing:

• https://forums.fogproject.org/topic/12014/multiple-windows-boot-manager-using-uefi
• https://forums.fogproject.org/topic/12946/windows-10-change-bios-boot-order-after-deploy

[Gilberto Ferraz]

@george1421 hello thanks for the help. yes already realized that it is the win10 operating system that changes the boot to “Windows boot management” but do you know any script to run in win 10 to put ipv4 back in the 1 option? I already followed some solutions from here. but I can’t come up with a solution without having to go to each of the machines.

[george1421]

@Gilberto-Ferraz

PS Code example that looks close, but the OP claims it throws an error from the ITNinja site https://www.itninja.com/question/how-to-programmatically-reset-uefi-to-boot-to-ipv4-first-after-scripted-windows-install-sets-windows-as-first-boot

# Create text file containing firmware settings
bcdedit /enum firmware > firmware.txt

# Find the line containing "IPV4", and read the line just before that
$FullLine = (( Get-Content .\firmware.txt | Select-String "IPV4" -Context 1 ).context.precontext)[0]

# Delete our temporary file
del firmware.txt

# Split line into fields using the first left-curly as the delimiter,
# and then grab the second field (and restore the first left-curly)
$GUID = '{' + $FullLine.split('{')[1]

# Set the boot order
bcdedit /set {fwbootmgr} displayorder $GUID {bootmgr}

At least it appears possible to do from within windows.

[Greg Plamondon]

@Gilberto-Ferraz
Try this running this PowerShell script as a snapin. What it does is moves the first non-windows boot selection to the top, in your case it will move “IP4 Intel Ethernet Connection I217-LM” to the top of the boot order.

Works for me…