Veeam restore to different hardware

Maybe this could help you:

https://helpcenter.veeam.com/docs/backup/cloud/cloud_connect_guest_restore_agent.html?ver=95

Should normally not be a problem...

So it finds the Windows installation as it boots into recovery?

Hardware should not be a problem, normally we see driver problems with RAID controllers or network cards, but other hardware should not be a problem.

Are the boot options (BIOS/UEFI, secure boot) the same on both devices?

File level restore would work but I'd rather just restore the entire volume for the purposes of saving time...

Since it's an existing laptop (OS install), it finds the C:\ partition (but says I have to manually map the restore in the recovery console - I try to select full computer but it complains about it).  So I go in to the partitions that are there (EFI, WINRETOOLS, C:\, etc.) and map what is in the backup to where it needs to go on the drives.  I don't have the old laptop in front of me so I don't know if the BIOS settings are exactly the same...

It does not make any difference if the computer is physical or virtual, if you follow my article as is, and just PRETEND the VM is the laptop, and follow the procedure it will RESTORE.

We use this to restore laptops in our office!!!

ONE CAVEAT!

If the OS is OEM, it might fail to activate, as OEM OS, should stay with the physical hardware!

It's completely normal if the hard disk is a different size and layout to map the partitions manually.

BUT....... Veeam will state if the Backup is UEFI or MBR Leacy, just make sure you set the BIOS the same on the new Laptop as the old laptop.

But this should not make any different to the restore, just if your LAPTOP bios is set to MBR, and you have UEFI partitions, it will not BOOT, change it in the BIOS and it will BOOT.

But note the warning about OEM OS !!!

If it's OEM OS, it may fail to activate because the hardware is different, and then you could be wasting your time.

What is the error message if you did a complete restore as described in the Article from Andrew?

Thanks Andrew.  I followed it step by step - except for the section about "Entire Computer, System Volume only, Manual Restore."  I select entire computer but it doesn't like the volume mapping...So I have to go in and map the volumes manually.

No error message.  Just boots up and Windows attempts a repair but can't.  At that point, I can go into advanced settings (system restore, cmd prompt, etc.)

Question:  Should the recovery .iso that I'm booting off of be of the old laptop or the new one?  Veeam support said to use the recovery iso from the new laptop but to choose the restore from the old...Didn't really make a difference as I've tried both.

Map the volumes manually, we use manual and different...

at the end of the Restore, Veeam reminds you about BIOS types.

Do you know if he old laptop was UEFI or Legacy MBR ?

I don't have the old laptop in front of me at the moment unfortunately...I should be able to get it back from the user sometime today or tomorrow (she's remote).  I was just trying to get something for her quickly...

Would it matter if BitLocker was enabled on the old laptop?

Bitlocker would ask for a recovery key, if the old disk is cloned.

But Veeam Endpoint Backup / Veeam Agent reads the backup from the unlocked disk, so your backup data are not encrypted, and your restore is also not encrypted.

(If you want to use bitlocker in the future, you would have to enable it again)

Agreed.  It has to be something in the BIOS that is preventing the boot...

Andrew, you mention "But this should not make any different to the restore, just if your LAPTOP bios is set to MBR, and you have UEFI partitions, it will not BOOT, change it in the BIOS and it will BOOT."

I'm not an expert with BIOS and hardware...Can you be more specific with this?  Thanks again for the help...

Please describe on your screen, what you have when you BOOT ?

Personal Computers have two methods of booting

1. Legacy MBR
2. UEFI

As for the backup and restore - it does not cause any issues.

You will need to manually set and configure the BIOS to match the restored VOLUME.

BUT if you made a backup of an UEFI configured OS, you will need to enable UEFI BOOT on the destination laptop.

if you made a backup of a Legacy MBR configured OS, you will need to enable Legacy MBR BOOT on the destination laptop.

I would be more CONCERNED with is this OS OEM, e.g. was the OS on the old laptop supplied with the laptop, because no matter what you do, or using any technology, it will fail to activate when you move it to a new OS.

(is there an OEM Product Key sticker on the laptop!)

You can read more here about OEM...

Original Equipment Manufacturers (OEM) versions

Note: Physical-to-virtual hard drive migration of a Windows installation is a valid function for customers with Software Assurance and full retail copies of Windows XP, Windows Vista, and Windows 7. Software Assurance provides users valuable benefits—please contact Microsoft Corporation for further information. Windows XP, Windows Vista and Windows 7 installed by Original Equipment Manufacturers (OEM) using OEM versions of these products may not be transferred to a virtual hard drive in accordance with Microsoft licensing terms.

Source
http://technet.microsoft.com/en-us/sysinternals/ee656415

https://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/A_3721-Can-I-transfer-my-OEM-version-of-Windows-to-another-PC.html

https://www.experts-exchange.com/questions/28950405/Virtual-Machine-XP-license-problems.html?anchorAnswerId=41642367#a41642367

there is an EE Question here, on this very subject of OEM conversions!

https://www.experts-exchange.com/questions/28950405/Virtual-Machine-XP-license-problems.html?anchorAnswerId=41642367#a41642367

and two EE Articles

https://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/A_3721-Can-I-transfer-my-OEM-version-of-Windows-to-another-PC.html

https://www.experts-exchange.com/articles/3218/XP-OEM-and-the-repair-reinstallation-which-disk-do-I-need.html