The Standard edition of Macrium Reflect v5 does not contain ReDeploy, neither do any of the 30 day trial editions. Alternatively, if you have a non-server (workstation) install, then use ReDeploy which is included with v5 Professional edition or the Server edition:
If you need to transfer a Windows Server install to new hardware, you need Reflect v5 Server edition for ReDeploy.
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. Please see here for information on purchasing deployment licenses. Note: Image deployment to multiple PCs requires a deployment license for each PC deployed.
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. What it will not do is install the complete driver set for the new hardware. ReDeploy is designed make the complex process of getting an off-line windows operating system running as easy and intuitive as possible. This allows the new hardware to be detected and the configuration of the Windows system modified to enable it to boot. You will need to run ReDeploy from the Windows PE Reflect rescue CD.
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. Again, for a stable system,this driver needs to match the hardware – in this case, the CPU model. A driver is optionally loaded to handle specific CPU features. The kernel and its associated HAL need to match the motherboard for best enabling. Once the kernel and the critical drivers are loaded, the kernel is started. If the new hardware configuration requires a new driver to read the disk containing the operating system then Windows will fail to boot. It must be undertaken when windows is being installed but then is skipped during a normal windows boot to make the boot delay acceptable.Įarly 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. The discovery of hardware and association with a matching device drivers is a time consuming process. The purpose of ReDeploy is to attempt to overcome these issues enabling a Windows installation to run on new hardware. There are various aspects of the windows boot processes that will typically cause a boot failure after significant changes to the hardware. Moving between a physical and a virtual machine (P2V / V2P ).Ĭhanging a non-raid to a raid installation or legacy SATA to AHCI SATA Migrating to a new machine due to hardware failure or planned upgrade such as a new motherboard etc. There are a variety of scenarios where you might need to move a windows installation to a new machine.