...more on REDEPLOY


Author
Message
Diazruanova
Diazruanova
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 27, Visits: 126
Hi,

At last I am replacing my old Motherboard and CPU (Intel H55 Chipset) for a more recent MoBo and CPU (Intel Z97 Chipset).
The rest of the hardware remains the same, case included, so my rig will consist, among other stuff, of the following:

New MoBo and CPU (Intel Z97 Chipset)
One SATA SSD (C. drive) containing Windows 10Home x64
One SATA 7200 rpm HD (D: drive) on which I have among other stuff a recent Macrium Image of the complete SSD (C.drive)
One Optical drive (HL-DT-ST DVDRAM) and...
One USB device containing Windows PE 10.0 Rescue Media


After putting together everything and double checking all connections, I will select to boot from the USB device containing Windows PE 10.0 Rescue Media and restore the image located in D: onto  the  SSD  drive overwriting all the partitions included of course,  the C: one with the Windows 10 operating system.

After the restore operation finishes and before rebooting, I will use the "Redeploy Restored Image to new hardware" option (restore tab) and insert the DVD which comes along with the new Motherboard, directing Redeploy to it so it can find the necessary NEW drivers for the new Z97 Chipset.  After redeploy finishes, then I´ll reboot the PC and hopefully, it will boot fine with the new MoBo and CPU. ...so far so good!

But I have a couple of questions:
  • Is it  MANDATORY  to restore the recently created Image from D: to C: before the redeploy process?
  • Can´t I simply boot from the  Windows PE rescue USB and just go to the redeploy option and skip the image restore process completely?
I don´t understand why should I restore the image located on D:  if I am NOT replacing my SSD ( C: )  for a new one and also, if I just recently created the image!

...isn´t the same exact data contained on the SSD ( C: )  the one that is copied to the Macrium image on D: that I just created minutes ago? 
...so what is the purpose of doing the restore process IF everything on the SSD ( C: ) will remain the same as if I never did it (the restore process)?

Thank you very much for your understanding and hopefully, despite my very limited experience BUT with your support, I will be able to perform this procedure without many problems.

Greetings








Tags
Edited 16 November 2016 3:35 PM by Diazruanova
Froggie
Froggie
Master
Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)
Group: Forum Members
Posts: 1.2K, Visits: 10K
Don't forget to run the "Remove license" feature in Reflect (Help/Remove License) following the making your final image... and make sure you have your License # to re-activate it on the new machine.
Diazruanova
Diazruanova
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 27, Visits: 126
Froggie - 16 November 2016 3:29 PM
Don't forget to run the "Remove license" feature in Reflect (Help/Remove License) following the making your final image... and make sure you have your License # to re-activate it on the new machine.

Thanks Froggie for the tip, I´ll do that.
Still waiting for the replies to my questions.  ;-)

Froggie
Froggie
Master
Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)Master (2K reputation)
Group: Forum Members
Posts: 1.2K, Visits: 10K
None of us really know the "guts" of the reDeploy process but yes, you are right, that the image on the surface of the SSD is exactly as it would be following a restore which appears unnecessary.  BUT, reDeploy may use some sort of semiphore (digital flag) to determine how to proceed.  That flag may only be present following a restoration operation.

Hopefully Nick, Stephen, et al will be able to provide an answer for you.
Nick
Nick
Macrium Representative
Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)Macrium Representative (3.5K reputation)
Group: Administrators
Posts: 2K, Visits: 12K
Hi Diazruanova

Thanks for posting.

Can´t I simply boot from the Windows PE rescue USB and just go to the redeploy option and skip the image restore process completely?


Yes  you can. There's no need to restore, you can just run ReDeploy on your existing file system.


Kind Regards

Nick - Macrium Support

Next Webinar


Diazruanova
Diazruanova
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 27, Visits: 126
Thanks a lot Froggie and Nick,

You are very kind and certainly my questions were answered!

Greetings from central Mexico to both of you     Wink



Drac144
Drac144
Expert
Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)
Group: Forum Members
Posts: 583, Visits: 2.3K
Please consider the following:  When replacing your motherboard you are changing ALL your device interfaces (such as USB, and possibly sound and graphics, etc.)  The Redeploy will only update the CPU related drivers.  You may still have to (or at least want to) update other drivers to those that are supplied with your new MoBo.  If your current drivers are fairly generic, they may work with your new MoBo, but maybe not as well as the drivers supplied with your new MoBo. 

Diazruanova
Diazruanova
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 27, Visits: 126
Thanks Drac144,

I am aware of it, but fortunately, the other devices like the graphics card (Nvidia Geforce GT730), the audio card and the Wi-Fi receiver, are not changed and their drivers are up to date, but anyway, I am pretty sure that something will pop out, it always do Smile

Regards




Diazruanova
Diazruanova
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 27, Visits: 126
Here it is an update on what happened after replacing my new Motherboard and CPU:

After putting together everything, the moment of truth arrived and I turned ON my PC waiting to enter the new BIOS and so be able to BOOT from the USB flash drive containing the Macrium Windows PE 10.0 Rescue Media, so I could apply the REDEPLOY procedure, BUT unfortunately (or should I say fortunately?)  I missed the F2 keystroke to enter the new BIOS set-up.

I was already waiting for a BSOD or some weird behavior, but to my surprise, the Windows 10 OS, made some preparations asking to wait and not to turn OFF the PC and after one minute or so, it started fine!!!.

I immediately went to Device Manager to see what SATA, AHCI driver was enabled and working and I discovered that Windows automatically installed the
generic Microsoft SATA, AHCI controller replacing the old Intel H55 one, so there was NO need to use Macrium redeploy at all, I simply ran the Motherboard DVD and installed all the drivers, re-started the PC and everything is running fine, included the re-activation of Windows 10 Home, but that is another story!

Greetings



Drac144
Drac144
Expert
Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)Expert (872 reputation)
Group: Forum Members
Posts: 583, Visits: 2.3K
Thanks for the update.  You should buy a lottery ticket - you seem to be very lucky! Tongue
Apparently your old CPU drivers were close enough to the new ones that they worked well enough for the system to run and take care of the update. 


Edited 21 November 2016 9:00 PM by Drac144
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