@Kari , one wild or nooby question. Will this also work with Windows 7?
Last edited by Kari; 14 Jun 2016 at 09:38. Reason: Typos
Trying this out today....
This link (year old) says virtualbox and vmware support is coming response to a question) but I could not find anything on Macrium site to support this. It would be a really major enhancement if this was true.....
Introducing Macrium viBoot (Technology Preview)
I am a Hyper-V fan and have not used any version of VMware or VirtualBox in years. That being said, don't they also support creating a vm using an existing VHD?
If so, have you tried opening an image in Macrium Reflect and converting it to a VHD:
@Kari, Windows update isn't showing up at this point so what I did was just to apply some minor changes to the VM session by installing some programs and apply it to the Macrium Image. But I did something different in extracting the updated Macrium Image. I skipped Part Four of your tutorial where you apply changes to the image and extract the new image. What I did was quite very simple and it worked, too. After applying the changes, I ran Macrium Reflect inside the VM and created a new image within and wrote the new image directly to my NAS where I can readily access the new updated image from a physical machine.
This way, I didn't have to delete the VM and create it again after. I grabbed the new image from the NAS and restored it and it was flawless. All the changes I made are there. You may want to add this method as an optional way of extracting updated image via Hyper-V/viiBoot.
By the way, I selected NAS as the destination for the new image because I can't figure out how to directly access my physical drives from inside Hyper-V.
To access the NAS, I had to go to Virtual Switch Manager, highlighted the network switch and ticked "Enable virtual LAN identification...." (see image below). However, by doing this, I temporarily lost internet connection on my physical machine but it didn't affect any process within Hyper-V while creating a new image to the NAS. When the new image is done, I just unticked the VLAN ID and I got network connection on the physical machine again.
Sorry, forget what I said about ticking VLAN ID to get access to NAS. That was last night.
This morning I don't have it ticked but somehow I can still access my NAS.
Last edited by badrobot; 18 Jun 2016 at 12:11.
In Virtual Machine Connection, select View > Enhanced session:Select your preferred resolution, select Show Options:
Local Resources tab, click More:
Select Drives, click OK:
Sign in, each and every host drive (yellow highlight) is shown and available in This PC as network drives:
Last edited by badrobot; 18 Jun 2016 at 13:42.