![]() ![]() My method ensures that the only virtual drive used by the VM in on the PC's own internal drive which would be faster, particularly if it is an SSD. It will work, but may be a little slow if the original. If that sounds too complicated, the just use viBoot as you intended. Once the restore was complete the second drive was no longer needed I removed it from the VM and deleted the. I then used Disk Management to dismount it and added it as a second hard drive in the VM's settings under the SCSI controller. vhd file in File Explorer, then copy the. When I got to the Installation Options I selected 'Install an operating system from a bootable CD/DVD-ROM' and selected the Macrium Recovery ISO I had made earlier as the image file.Īs I recall, the easiest way to make the ,mrimg file available for the restore was to use Hyper-V manager to create a new virtulal hard disk, mount that. I created a new virtual machine in Hyper-V Manager. Click 'OK' button to start converting img file to iso. Set the output file format to iso file, and enter the output file name. Choose the source IMG file you want to convert. Doing so may well make the VM disappear from the list of VMs in viBoot, though it will still appear in Hyper-V manager.Īre you saying you restored it with the Macrium ISO that you booted into in Hyper-V? To convert IMG file to iso file, please follow the steps, Run PowerISO. If you don't, when you shut down the VM Hyper-V will create an automatic checkpoint. Important: as soon as you have created a VM with viBoot, go to its settings and turn off 'automatic checkpoints'. ![]() I often use viBoot as a quick way to run an image for test purposes. ![]() If you do decide to use viBoot, then that should have no problems either. So I now can make a Macrium image of the VM to restore back to a real machine. I then upgraded it in stages, first to Vista, then Win7 and finally to Win10. If XP can cope with the different hardware, then Win7 should have no trouble. I took a Macrium image of the drive, restored it to a VM, and it ran without a problem. The last time I did this was to rescue some software installed on a dead XP machine, the only remaining working part was the HDD. Windows will sort out the drivers required on the first boot. I have never had any problems when I have done it. ![]() Is the notion of redeployment an issue or factor in doing so since the Win7 VM will be on different hardware? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |