In terms of licensing, that can be an issue, and Reflect makes no attempt to deal with it (nor would they likely be allowed to for Microsoft licensing reasons). That sounds like a lot of extra time to me, but then again I'm perfectly comfortable downloading driver packages from vendor websites and extracting them to folders. As to whether it would be easier to just build Rescue Media on the new PC prior to restoring the backup you intend to ReDeploy, that may vary from person to person. So if you're dealing with Windows 10 (rather than trying to ReDeploy an old Windows version onto modern hardware), you may not need to provide any drivers for boot-critical devices at all.
#Macrium reflect free edition full file install#
The idea is that you'd ReDeploy your system just to get Windows to start properly, and once you're in Windows you'd install all other appropriate drivers for you new hardware within Windows. However, ReDeploy also only concerns itself with boot-critical hardware. To my knowledge, ReDeploy will search the driver library of the Windows environment that's being deployed to see if it has native support for the new hardware, and otherwise you'll be prompted to supply said drivers. I'm not 100% sure on this, but I don't think that auxiliary drivers loaded into Rescue Media can be used for "injection" into the Windows environment that's being ReDeployed.
0 kommentar(er)
