Hello, I’ve got a Windows 10 golden image for UEFI all configured and up and running. It works magically!
But, I’m running into an issue where after setting the boot order to PXE first, I’ll deploy my shiny image and when it runs through configuring the machine Windows will revert the boot order to put Windows Boot Manager first. I don’t want that at all since it means the box won’t PXE boot on it’s own anymore. Any idea how to stop windows from screwing around with boot order?
I’ve maybe figured that Fast Startup “feature” is the culprit responsible, and am currently re-capturing my image with a sysprep stage 4 specialize command of “powercfg /H off” to disable hibernate (and disable Fast Startup by association), so I’ll find out in a moment whether this idea worked or not, but I’m not very hopeful as the OS reboots a few times during device installation portion of OOBE and I’m thinking the specialize steps may not take effect before these reboots. Guess I’ll see in a bit…
Is Windows 10 One touch imaging for UEFI possible now, given the OS’s propensity to make these arbitrary boot order changes? It worked great under 7, and I’m thinking 10 under legacy/mbr works fine as well, but MBR’s not an option for us anymore due to Bitlocker/TPM 2.0