Windows 10: Installing a Macrium image backup on a new Hyper-V VM.

I am sure this is obvious to many users, but I puzzled about it a lot today but got there in the end.

I had created a Macrium image backup from audit mode as per the video links on Saturday as described by Kari.

The image I created is a dual boot image - W10 (oobe), and Macrium Reflect.

I could not initially see how to recover that image to a new VM, as it did not have anything, and I could not see how to connect a boot usb.

I realised, you have to actually use the Macrium Rescue iso, as the boot device, and then I pondered how Macrium could pick up the image, as on my PC, Macrium will not see my second hard drive due to a driver missing in default (I have injected the actual drivers but could not get it to work - separate problem).

Unlike installing PRO, the VM booting from Macrium can only be used in basic mode, so I have to take the second drive offline to see it of course.

Obviously I could not put image on my main drive, and take my main drive offline as you could not run Hyper-V.

So initially, I could not see anyway of seeing my image from Macrium without installing Windows first.

Then a light-bulb switched on in my head when I realised within Hyper-V, Macrium knows nothing about the drivers needed to see my second drive. It is Hyper-V that manages the interface to my second hard drive with the Host. I realised it is irrelevant that booting from Macrium in the Host cannot see my second drive.

So I put my Macrium image on second drive, took it offline, created a new VM, and set the scsi driver to use my second external drive.

I then booted PM to Macrium Rescue iso, and Macrium saw my second drive with no problem, selected the image backup and restored it and it worked great!

I can now reinstall Windows 10, Macrium ready as dual boot on Hyper-V in a matter of a few minutes.

Thanks Kari for a great presentation. I just thought I would share my experience in case anybody else needs to restore a Macrium image to a new drive. It was actually easy once I worked out the steps involved.

:)

 

Remote Desktop Connection problem with Virtual Machine

We made the big mistake of configuring a WINDOWS-10 VM to allow for Remote Desktop Connections. We are unable to disassociate the VM from RDM. We can no longer access the VM!!! The following is the pertinenet
information:

• Server is running Windows-10 Professional 64 with Hyper-V installed.
• VM is Windows-10 Professional 64.
• In VM allowed Remote Desktop Connections.
• From server successfully connected to VM via RDM.
• Closed RDM connection. Unable to access VM.
• Turned off VM from Hyper-V Manager.
• Attempted to restart VM, unable to connect via Hyper-V from message box the following is displayed:
  
  Video Remoting was disconnected. The virtual maching is currently using the Remote X 3D video adapter. A user is currently connected via Remote Desktop Connect to the virtual machine by using Remote Desktop Connection.
• Connected via Remote Desktop Connection. Attempted to turn off allowing Remote Desktop Connection. VM hung.
• VM Wouldn't turn off via Hyper-V manager.
• Shutdown host system and rebooted.
• Unable to connect via console or RDM.
• Shutdown host system and rebooted.
• Deleted VM via Hyper-V Manager.
• Restored VM system disk from backup prior to RDM usage.
• Created new VM. the messages in itm 7 above are displayed.

What can be done to recover? Why does Hyper-V retain a broken connection?

 

No Internet in Hyper-V VM's

Hi, I have Windows 10 Enterprise and just added Hyper-V. I had 3 VM's on VMware Player and deleted and uninstalled Player. I have 3 Vm's on Hyper-V. My problem is I get no Internet on my Vm's. I am new to Hyper-V and would like to know how to connect these
to the internet. I have "Virtual switch (automatic)" selected. They show no connections available in the VM's. How do I connect to the internet? (I'm on wifi.) I'm attaching a screenshot. Thanks

 

Have you seen this ? Macrium Software | Macrium viBoot

 

Correct.

 

Sorry, folks, I must have misunderstood the OP's post. I thought he wanted to create a VM from a Macrium Reflect image backup.

 

No problems, my post was only to clarify this.

 

No worries - I did but did not want to run via viboot (which I do use). There would always be a performance hit using viboot as it has to decompress files on the fly.

I solved issue anyway. It just sometimes takes a while to get your head around the interactions between host os and vm.