Hi there, hope someone can help.

I am developing VMM 2016 bare metal deployment to an R620 and am having an issue with the UEFI boot order changing right after the VHD is deployed to the server and it reboots.  Before the deployment the boot order reported by racadm is.

UefiBootSeq=RAID.Integrated.1-1,Optical.SATAEmbedded.E-1,NIC.Integrated.1-1-1,NIC.Integrated.1-2-1,NIC.Integrated.1-3-1,NIC.Integrated.1-4-1,NIC.Slot.3-1-1,NIC.Slot.3-2-1,RAID.Integrated.1-1

After the reboot it is.

UefiBootSeq=Optical.SATAEmbedded.E-1,NIC.Integrated.1-1-1,NIC.Integrated.1-2-1,NIC.Integrated.1-3-1,NIC.Integrated.1-4-1,NIC.Slot.3-1-1,NIC.Slot.3-2-1,RAID.Integrated.1-1,RAID.Integrated.1-1

It is if the steps that VMM performed to prepare the hard disk to boot to the VHD alters the BIOS UEFI boot order which is applied at the next boot, which prevents the system from booting to the hard disk.  This then breaks the automation of the bare metal deployment.  I have been looking but have found no fix for the problem.

I just tried updating all BIOS and firmwares but that didn't help.  Anyone have any pointers on how to fix or work around this issue?

Cheers.

Gary.