Steps for redeploying Win10 to new hardware and migrating from legacy bios to UEFI


Steps for redeploying Win10 to new hardware and migrating from legacy...
Author
Message
johannes
johannes
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)
Group: Forum Members
Posts: 2, Visits: 12
Hello,
I'd like to confirm that these are the correct steps to redeploy a Win10 installation from 'old' to 'newer' hardware. The old PC is a Lenovo Workstation with a HDD and legacy BIOS. The new PC is a Lenovo Workstation with UEFI and an M.2 drive. I have one license of Macrium Reflect Home v8.

Reference: https://kb.macrium.com/KnowledgebaseArticle50151.aspx

On the old PC:
1. Sysprep: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation?view=windows-10
2. Install and register Macrium Reflect
3. Backup full disk and store on network drive
4. De-register Macrium Reflect

On the new PC:
1. Install and register Macrium Reflect
2. Create USB rescue media and include devices / drivers from new PC (?)
3. Boot into windows PE and format disk according to: https://kb.macrium.com/KnowledgebaseArticle50151.aspx
4. Complete steps to restore windows and fix UEFI boot.

Is my understanding here correct? Any pitfalls I should be aware of?

Thanks!
 Johannes

jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)
Group: Forum Members
Posts: 14K, Visits: 82K
1. Don’t Sysprep. Use the ReDeploy function within Rescue Media after running Fix Boot Problems instead. Running Sysprep without supplying an unattend XML file will send you through the full Windows out-of-box experience when you next start that environment, which you typically don’t want in this use case. Additionally, even if you DID want to Sysprep, that would have to be the very LAST thing you do before capturing the image. You wouldn't Sysprep and then install Reflect. You would actually Sysprep and then immediately restart into Rescue Media to make the image backup.

2. This link is a newer version of that KB article https://knowledgebase.macrium.com/display/KNOW80/Restoring+an+MBR+System+image+to+UEFI-GPT

Otherwise, yes that’s the right idea.
Edited 9 April 2023 10:25 PM by jphughan
Danskeman
Danskeman
Expert
Expert (726 reputation)Expert (726 reputation)Expert (726 reputation)Expert (726 reputation)Expert (726 reputation)Expert (726 reputation)Expert (726 reputation)Expert (726 reputation)Expert (726 reputation)Expert (726 reputation)
Group: Forum Members
Posts: 509, Visits: 4K
The tricky part is that new pc has an m.2 drive.  Depending of type, it may need irst drivers which you will need to be included on the Macrium Reflect usb drive or else usb drive will not boot.

Personally, I would clean install Windows 10 on new pc first and then backup all drivers using dism command (many web guides how to do this).

Then I would temporarily install the free version (trial copy) on pc to create a USB rescue drive - this will automatically end up with key drivers needed to boot usb drivw on new pc rather than guessing. 
johannes
johannes
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)
Group: Forum Members
Posts: 2, Visits: 12
It worked!

I went through the process a first time and encountered an error in the ReDeploy step. After rebooting it couldn't find a partition to boot. So I did the 'fix boot issues' and 're deploy' a second time to take some pictures, encountered the same error when re-deploying:

But then it booted just fine, and everything seems to work! I'm not sure what I did differently the second time though...

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search