The Macrium Reflect knowledgebase has been upgraded.
Please go here for the latest information.


v5: How to use Macrium ReDeploy

Expand / Collapse

v5: How to use Macrium ReDeploy

What is Macrium Redeploy?

There are a variety of scenarios where you might need to move a windows installation to a new machine. Some examples are listed below:
  • Migrating to a new machine due to hardware failure or planned upgrade such as a new motherboard etc.

  • Moving between a physical and a virtual machine (P2V / V2P ).

  • Changing a non-raid to a raid installation or legacy SATA to AHCI  SATA

There are various aspects of the windows boot processes that will typically cause a boot failure after significant changes to the hardware. The purpose of ReDeploy is to attempt to overcome these issues enabling a Windows installation to run on new hardware.

The discovery of hardware and association with a matching device drivers is a time consuming process. It must be undertaken when windows is being installed but then is skipped during a normal windows boot to make the boot delay acceptable.

Early in the boot process, the boot loader loads the windows kernel (the core of the operating system) and selected “critical” drivers required to get Windows up and running. If the new hardware configuration requires a new driver to read the disk containing the operating system then Windows will fail to boot.

Once the kernel and the critical drivers are loaded, the kernel is started. The kernel and its associated HAL need to match the motherboard for best enabling. A driver is optionally loaded to handle specific CPU features. Again, for a stable system,this driver needs to match the hardware – in this case, the CPU  model.

ReDeploy is designed to detect changes to these critical system features,locate relevant drivers and inject them into your windows operating system to enable it to boot.

You will need to run ReDeploy from the Windows PE Reflect rescue CD. This allows the new hardware to be detected and the configuration of the Windows system modified to enable it to boot.

ReDeploy is designed make the complex process of getting an off-line windows operating system running as easy and intuitive as possible. What it will not do is install the complete driver set for the new hardware. You will be able to complete the driver installation for devices such as network and graphics adapters once your windows installation has booted on your new hardware.

Note: Image deployment to multiple PCs requires a deployment license for each PC deployed. Please see here for information on purchasing deployment licenses.

If you deploy an image to a different PC then you should make sure your installed software, including Windows and Macrium Reflect is suitably licensed for the new PC.

Platform support

 If you need to transfer a Windows Server install to new hardware, you need Reflect v5 Server edition for ReDeploy. Alternatively, if you have a non-server (workstation) install, then use ReDeploy which is included with v5 Professional edition or the Server edition:

  Workstation Server
 v5 Professional
 v5 Server
x x

The Standard edition of Macrium Reflect v5 does not contain ReDeploy, neither do any of the 30 day trial editions.

Using Macrium ReDeploy

Note: ReDeploy will modify an existing offline operating system to work with new hardware. You should restore your system image to the PC being deployed before running ReDeploy. There is no need to reboot your PC after restoring an Image and before you run ReDeploy.

  1. Boot the target PC with the Windows PE rescue CD or USB equivalent.  (At bottom of this tutorial is a link to a video on creating a Windows PE rescue CD).
  2. Take the ReDeploy Restored Image to new hardware option.
  3. If you have a multi-boot system, then you will be presented with a list of operating systems, select the operating system to be redeployed. Click on 'Next'.
  4. The following dialog will ask you to specify driver locations for your mass storage devices (such as RAID card). If you haven't already done so, please insert a driver disk for the hardware you are going to boot from. This will typically be the motherboard or RAID card driver CD, click on Add to add driver locations. You can also specify additional paths such as network folders, click on 'Map Drive' to add a network share. Then Click on 'Next'
    Note: ReDeploy will first search through any user specified driver locations. If none are specified or no matching drivers are found then removable devices such as CD's and floppy drives are searched. ReDeploy will also search through Windows' database of drivers.
  5. ReDeploy will now seek drivers for all discovered mass storage devices and a list will be displayed with details to the right. Click 'Next'

    ReDeploy will now seek drivers for all discovered mass storage devices and a list will be displayed with details to the right.

    For each mass storage device, there are three possibilities:

    • The driver is already installed. It might still need to be enabled at boot – this will be done automatically.
    • The driver has been located, either from a CD, user specified path or from the Windows database. This driver will be installed on completion of ReDeploy.
    • No matching driver has been located.

    If no driver has been located or you wish to override the displayed driver, then the 'locate driver' button can be used to manually specify an .inf file.

    Note: If you have multiple mass storage interfaces in your system, then you only need to locate drivers for the hardware that contains the Windows system and active partitions.
  6. The options on the next dialog maybe left at the defaulted values. If you have trouble booting then these options can help resolve issues. Click Next.  For more information about the options please see below:

    1. Disable reboot on system stop
      Set this option to stop automatic rebooting if a BSOD occurs while Windows is loading or running. If this option is not set and Windows generates a BSOD, there will be no time to note the BSOD error codes.
    2. Display boot drivers as they load
      Set this option to show which drivers are being loaded as Windows loads. Once Windows is loading and running without issue this option can be reverted using the Windows MSCONFIG utility. You can use the Pause/Break key to freeze the list as it scrolls past, use space to un-pause.
    3. Enable boot logging
      Set this option to enable logging of drivers being loaded by Windows as it loads. The resulting log file 'ntblog.txt' can be found in the windows folder. Once Windows is loading and running without issue this option can be reverted using the Windows MSCONFIG utility.
    4. Disable CPU Driver
      Set this option to disable CPU drivers. This may be useful if you see BSOD's in the selected Hardware Abstraction Layer drivers or system lockup on entering standby or shutdown.
    5. Set Hardware Abstraction Layer
      Set this option to choose which Hardware Abstraction Layer is to be used in the selected Windows operating system. The recommended HAL for this machine will be the one initially selected. If you have the incorrect HAL configured, your Windows installation will typically be unstable and you will often see random BSOD's or lock ups after Windows has booted. In particular, if you are redeploying from or to Virtual Box with APIC unchecked (the default) or very old physical hardware, the you will need to set a new HAL.
    6. Allow Windows to detect Hardware Abstraction Layer
      Set this option to allow Windows to determine the best Hardware Abstraction Layer to use at boot time. For Vista, use this in preference to the “Set Hardware Abstraction Layer” option. This is a Vista and later only option.
    7. Enable SATA AHCI
      Set this option to enable support for generic SATA AHCI hardware. You will typically also need to enable an option in your BIOS for your mass storage hardware to operate in this mode. This is a Vista and later only option.
  7. You will be presented with a list of actions that will be performed and clicking Finish will apply these options to the target operating system. A log file 'ReDeploy.log' will be saved to the drive containing the operating system redeployed.

    After clicking 'Finish' to inject drivers and apply your settings you get a confirmation dialog, and you can reboot your OS which should now be compatible with your new hardware!


Note: Make sure there is a tick in the checkbox against 'Check for unsupported devices eachtime the rescue media loads' before you burn the Windows PE rescue CD, this will enable you to add additional drivers when you boot on new hardware.

Search Terms
How do I use ReDeploy
Can I restore an image to a different PC
Moving Windows to different hardware

Last Modified:16 Dec 2013

Last Modified By: Administrator

Type: Tutorial

Article not rated yet.

Article has been viewed 78,096 times.