sglee
asked on
Disk2vhd vs Microsoft Virtual Machine Converter 3.0
Hi,
I just wanted to understand the differences between Disk2vhd and Microsoft Virtual Machine Converter 3.0. First let me share with you my experience with each.
I have used Disk2vhd to create VHDX file from a standalone/physical Windows 7 and SBS2011 and created VMs in Windows 2012 R2 Hyper-V by choosing "existing virtual hard disk". I found it reliable even though it is basically 2-step process. On a large size of OS such as SBS2011, it was time consuming because I had to wait for the time to create VHDX on an external USB HD and copy VHDX file to Hyper-V server. But I was able to convert both desktop OS and server OS.
Now regarding Microsoft Virtual Machine Converter: My understanding was that this was one step process. Once this tool is installed on physical Windows 7 or SBS2011 computers, I could create respective virtual machines on an existing Hyper-V server across the network. But my attempt was not successful on either OS.
Having said that, I read the following on Microsoft website:
https://www.microsoft.com/en-us/download/details.aspx?id=42497
System Requirements
-------------------------- ---------- -----
Supported Operating System
Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2
Before you install Microsoft Virtual Machine Converter (MVMC), you must install the following software on the computer on which you want to run MVMC:
Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 SP1 operating systems
Microsoft .NET Framework 3.5 and .NET Framework 4 if you install MVMC on Windows Server 2008 R2 SP1
Microsoft .NET Framework 4.5 ....
-------------------------- ---------- -----
I don't see Windows 7 in the list of "Supported Operating System". Was that the reason why my attempt failed? Also I failed with SBS2011 too even though it is essentially Windows 2008R2 which is in the list of "Supported Operating System".
I saw a youtube video where I learned that you must install "enable Background Intelligent Transfer Service" (as seen on the screenshot) this morning.
Have said that, was the lack of "Background Intelligent Transfer Service" the reason why I failed to create Virtual machines in Hyper-V server directly from physical Windows 7 and SBS2011 computers?
Thanks.
I just wanted to understand the differences between Disk2vhd and Microsoft Virtual Machine Converter 3.0. First let me share with you my experience with each.
I have used Disk2vhd to create VHDX file from a standalone/physical Windows 7 and SBS2011 and created VMs in Windows 2012 R2 Hyper-V by choosing "existing virtual hard disk". I found it reliable even though it is basically 2-step process. On a large size of OS such as SBS2011, it was time consuming because I had to wait for the time to create VHDX on an external USB HD and copy VHDX file to Hyper-V server. But I was able to convert both desktop OS and server OS.
Now regarding Microsoft Virtual Machine Converter: My understanding was that this was one step process. Once this tool is installed on physical Windows 7 or SBS2011 computers, I could create respective virtual machines on an existing Hyper-V server across the network. But my attempt was not successful on either OS.
Having said that, I read the following on Microsoft website:
https://www.microsoft.com/en-us/download/details.aspx?id=42497
System Requirements
--------------------------
Supported Operating System
Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2
Before you install Microsoft Virtual Machine Converter (MVMC), you must install the following software on the computer on which you want to run MVMC:
Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 SP1 operating systems
Microsoft .NET Framework 3.5 and .NET Framework 4 if you install MVMC on Windows Server 2008 R2 SP1
Microsoft .NET Framework 4.5 ....
--------------------------
I don't see Windows 7 in the list of "Supported Operating System". Was that the reason why my attempt failed? Also I failed with SBS2011 too even though it is essentially Windows 2008R2 which is in the list of "Supported Operating System".
I saw a youtube video where I learned that you must install "enable Background Intelligent Transfer Service" (as seen on the screenshot) this morning.
Have said that, was the lack of "Background Intelligent Transfer Service" the reason why I failed to create Virtual machines in Hyper-V server directly from physical Windows 7 and SBS2011 computers?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
to convert it ?
ASKER
Can I create a virtual machine in Hyper-V server from a physical Win10 PC?
ASKER
So I can't Convert physical machines such as Windows 7 or Windows 10 to Hyper-V using Microsoft Virtual Machine Converter 3.0?
You can only convert support Operating Systems are SUPPORTED.
ASKER
But in your article, "Supports Windows Server® 2012 R2, Windows Server® 2012, and Windows® 8 as guest operating systems that you can select for conversion.". If it supports Windows® 8, why wouldn't it support Windows 10?
Correct, thats taken from the Microsoft guidelines.
MVMC was launched BEFORE Windows 10 was released! It may work, and Microsoft have not launched a new version of MVMC for a while, in fact they withdrew 3.1!
So there is NO GUARANTEE it will work! as it's not listed as supported!
Try it!
MVMC was launched BEFORE Windows 10 was released! It may work, and Microsoft have not launched a new version of MVMC for a while, in fact they withdrew 3.1!
So there is NO GUARANTEE it will work! as it's not listed as supported!
Try it!
ASKER
I tried on Windows 10, but did not work and that was the reason I was curious.
BTW your article mentioned V3.1, but I could not find that version. Only v3.0 was available for download.
BTW your article mentioned V3.1, but I could not find that version. Only v3.0 was available for download.
Please see my last post!
MVMC was launched BEFORE Windows 10 was released! It may work, and Microsoft have not launched a new version of MVMC for a while, in fact they withdrew 3.1!
after I'd written the article!
I believe there are plans for a new version!
MVMC was launched BEFORE Windows 10 was released! It may work, and Microsoft have not launched a new version of MVMC for a while, in fact they withdrew 3.1!
after I'd written the article!
I believe there are plans for a new version!
ASKER
is this 2008 or 2008 R2 ?
because...
Windows 2008 is not on the supported list.
Supported Operating System
Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2
also this Question, was differences between Disk2VHD and MVMC, I believe this has been answered.
because...
Windows 2008 is not on the supported list.
Supported Operating System
Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2
also this Question, was differences between Disk2VHD and MVMC, I believe this has been answered.
ASKER
It is 2008, not 2008 R2.
Not Supported as per Microsoft documentation.
ASKER