Aller au contenu principal

Cannot use bitlocker on redeployed images

Thread needs solution

Hello,

I have created a backup of our HP Elitebook 840G3 and redeployed it to an identical device.

On the master system, I am able to enable TPM and Bitlocker without isssue, however, on any redeployments of this image on other machines, Bitlocker will not enable. I get the Error

the path specified in the boot configuration data (bcd) for a bitlocker drive encryption integrity-protected application is incorrect. please verify and correct your bcd settings and try again. 

I have attempted to use this KB from microsoft https://support.microsoft.com/en-us/kb/929834   
but have had zero luck. 

I noticed that on my Master system. I have 3 partitions

System Reserve (System, Active, Primary Partition) 500MB NTFS
C: (Boot, Page fire, Crash Dump, Primary Partition) 237.21 GB NTFS
 Unlabeled (Recovery Partition) 794MB

These all show to be selectable in the the Acronis TrueImage 2015 Bootable media. However after deployment, I only see 2 Partitions on the other machine

Unlabled (EFI System Partition) 100MB
C: (Boot, Pagefile Crash dump, primary partition) 238.25GB NTFS

Why is the System Reserve partition and other partitions gone? Why is the EFI one here now? Shouldn't it be a carbon copy?

Thanks
 

0 Users found this helpful

Aaron, welcome to these user forums.

There is a noticeable difference between your systems from your post above.  Your source / master system has no EFI partition and therefore this is a Legacy / MBR BIOS booted system, whereas on your target system you show that you do have an EFI partition, therefore that system boots differently using UEFI and probably with Secure Boot too.  See the ATIH 2015 User Guide: Migration methods section which shows the large number of different permutations that can be encountered with BIOS and UEFI systems - expand the section to see detailed information. See screen shot.

I would recommend creating your master system on a system that will match your target systems fully.

Secondly, when you restore a backup image to different hardware then you also need to use the Acronis Universal Restore utility boot media to prepare that different system to work on the new hardware.

Fichier attaché Taille
396475-134602.png 45.81 Ko

Both machines are identicle....

Why wouldn't acronis back up the drives exactly as they are? I don't understand why it would change it from Legacy/MBR to UEFI?  Do I need to launch Acronis recovery media in legacy mode instead to ensure it captuers correctly?

I was able to find a solution, but It ended up having me use a Win7 Repair disk and then restoring the REagent.xml in system32

At this time, I cannot completely recreate the image on my master machine as there is way to much involed in doing that for my business.

Aaron, the Acronis rescue media should always be booted in exactly the same boot mode as is used by your Windows OS installation.

See webpage: Check if your PC uses UEFI or BIOS to determine the boot mode of the source / master system.  Your target system should support the same boot mode to avoid any conversion being performed, so given you are seeing an EFI partition you will need to check the options in the BIOS settings for that system to see if it supports being booted in Legacy mode.

Aaron Johnson wrote:

Why wouldn't acronis back up the drives exactly as they are? I don't understand why it would change it from Legacy/MBR to UEFI?  Do I need to launch Acronis recovery media in legacy mode instead to ensure it captuers correctly?

How you boot the media determines the formatting / scheme of the disk.  This applies not just to Acronis, but even with your Windows installation media.

Example:  You have a brand new legacy/MBR formatted disk, but you boot your Windows installer media in UEFI mode.  When asked where to install your new OS, your new disk will not be an available option because the Windows install media was launched in UEFI and Windows will only allow you to install UEFI to a GPT formatted disk.

Vice-versa... You have a newly formatted GPT disk, but you boot your Windows installer media in legacy mode. When asked where to install the OS, you will not see your new disk as an option because Windows will not allow you to install a UEFI OS onto a legacy formatted hard drive.

Taking a page from Microsofts playbook, if you boot the Acronis media in legacy mode and restore, your OS is rstored as legacy/MBR - however, if the OS was originally UEFI, it will not boot.  You can't go from UEFI back to MBR.  If you boot the Acronis media in UEFI mode, your OS is restored as UEFI/GPT.  In some cases, you can successfully convert a legacy/MBR installed OS to the newer UEFI/GPT scheme with Acronis (pending your bios supports it and is properly configured afer the restore... such as making sure the bios is set to allow UEFI boot and that "windows bootmanager" is the top boot priority after the restore).