UEFI Boot order changing after image by SCCM

[localzuk]

I'm working through getting Windows 10 up and running on our SCCM server for deployment (when needed) and testing.

 

I have come across a rather irritating issue - when I deploy Windows 10 to a PC, it changes the boot order in the UEFI bios. So, what used to be network then disk becomes disk then network.

 

I'm probably missing something simple, but I want network boot to remain first, for re-imaging purposes. Anyone know how I stop it swapping?

[localzuk]

Anyone else seen this?

[Steve21]

When you say changing, is this changing from what the original VM image had, and going to what the local machine you deploy it to is?

 

Or changing the physical machine to another setting?

 

Steve

[localzuk]

The install is changing the physical boot order on the machine.

 

So, I manually set each machine to boot to IPv4 network first, hard disk second.

 

I then deploy Windows 10 to the machine. The machine will pick up the deployment via PXE, and install.

 

After installation, the machine now has the boot order of hard disk first, IPv4 network second.

[medford83]

Localzuk was you ever able to fix this problem with the boot sequence? We are currently experiencing the same problem

[localzuk]

No, I ended up changing how we dealt with this anyway - we no longer do "PXE boot first" on our devices.