Group: Forum Members
Given that Reflect doesn’t run on Linux, it’s unlikely to be helpful to you, except possibly indirectly. If you wanted to use it, you’d have to plan to use a VM hypervisor that ran on both Windows and Linux, or at least a hypervisor that supported a virtual disk file format that could be used in both Windows and Linux. The idea here is that you would capture an image of your Windows system, then restore it to a virtual disk, mounted on your Reflect system, that was hosted in a virtual disk file format that would be usable by your Linux-based hypervisor. And then you’d use that file as the hard disk for your VM.
The next step you might need to perform would be to boot the VM into Reflect Rescue Media (have Reflect generate a Rescue Media ISO for this) and run ReDeploy within the VM so that Reflect will modify that Windows environment to boot on the VM’s “hardware” rather than the hardware it was previously running on.
And then the last step would be to install the hypervisor’s guest/integration tools into the VM, if applicable based on the hypervisor you choose.
Note that even after all this you might run into licensing issues with Windows and possibly other applications as a result of the system now running on completely different hardware.
Note also that some hypervisors include P2V (physical to virtual) utilities specifically designed to facilitate this process of moving an OS environment currently running on physical hardware over to a VM running on a particular hypervisor. If you select a hypervisor from a vendor that provides that type of tool, that might simplify this process. But you would still face the potential OS and software licensing issues I mentioned above.