Ghost images restored to EFI configured systems don't retain the proper boot order

Products

• Ghost Solution Suite

Issue/Introduction

After deploying a EFI image to a Client machine, the boot order in the bios/firmware will list the Windows Boot Manager/Hard drive last regardless of the boot order before deploying. 

Environment

GSS 3.x 
DS 8.x
Windows Client OS's loaded in EFI mode rather than Bios/Legacy

Cause

When an EFI ghost image is restored to an EFI system, ghost will update the Firmware to point to the Windows Boot Manager as the last item to boot from.

Resolution

If a customer needs to have the 'Windows Boot Manager' as the first boot item, they can add the '-fixefiboot' switch to the Ghost command line.

There currently is no code to preserve (re-generate) the existing boot order for EFI after deploying an image.

The '-FixEfiBoot' switch moves the 'Windows Boot Manager' to the first item in the list. Bitlocker and/or Secure Boot may also change this behavior if enabled on the endpoint before the image is deployed.

The boot order is not changed if doing partition imaging instead of disk imaging.