@myles said in Issues with one time PXE Boot on HP Workstations:
The time it takes for PXE boot to fail might be something we can get away with, but for them to watch an undesired PXE boot to happen will almost certainly trigger complaints,
This process of pxe boot into FOG and then fog menu timeout (default of 5 seconds) should take no longer than 15 seconds to start booting windows. If it taking minutes then something is wrong. As I mentioned I don’t have the client computer boot through the ipxe menu, but the IT tech select pxe boot when imaging is needed. This way the users computer boots normal 99% of the time, without delay.
Also I mentioned that changing the boot order isn’t what FOG does, but I also said a FOG Postinstall script is all you need. Changing the boot order is simply one line script. The (kind of) instructions for the uefi boot manager is here: https://www.linuxbabe.com/command-line/how-to-use-linux-efibootmgr-examples
If you want to do a little debugging using the efibootmgr program you can easily with FOG. Just schedule another capture deploy (doesn’t matter) but before you press the schedule task button, tick the debug checkbox. Now schedule the task. PXE boot the target computer. After several screens of text you need to clear with the enter key you will be dropped to the FOS Linux command prompt. From there look at/follow section 2 from the link I provided. That will give you an idea of what command parameters you need. Once you find the parameters you need to give you the boot order you desire then…
On the FOG server, in /images/postdownloadscripts/ directory there is a file called fog.postdownload Just add that efibootmgr command to the end of that file. Save it and test to see if it gives you the desired results.
Now you might need to make that call to the efibootmgr a bit more intelligent in that lets say you have two different sets of hardware that have different uefi boot orders. You might need to have different efibootmgr commands for different models or manufactures of computers. We can deal with that later if in general the basis work as you need.
Finally you will need to kill that debug task you scheduled at the beginning of this debugging because that job will stay active until imaging is complete in debug mode.