Ghost images restored to EFI configured system won't retain the proper boot order.
Article ID: 165021
Updated On:
Products
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 boot order before deploying.
Environment
Ghost Solution Suite 3.x
Deployment Solution
Windows Clients 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' to the Ghost command line.
There is currently no code to preserve (re-generate) existing boot order for EFI after deploying an image.
'-FixEfiBoot' switch moves 'Windows Boot Manager' to the first item in the list. Bitlocker and/or Secure Boot may change this behavior if enabled on the endpoint before the image deploy.
The boot order is not changed if doing partition imaging instead of disk imaging.
Feedback
