Virtual Machine Converter 3.0 released! P2V came back!

Microsoft has released new version of Virtual Machine Converter. Since from System Center 2012 R2 P2V support has been removed from functionality and some people had to use third-party solutions (sysinternals disk2vhd, citrix xenconvert, vmware converter and etc) or SC 2012/SP1 . Now we have a native tool from MS to performing physical-to-virtual conversion:

    Microsoft® Virtual Machine Converter (MVMC) is a Microsoft-supported, stand-alone solution for the information technology (IT) pro or solution provider who wants to convert virtual machines and disks from VMware hosts to Hyper-V® hosts and Windows Azure™ or alternatively convert a physical computer running Windows Server 2008 or above server operating systems or Windows Vista or above client operating systems to a virtual machine running on Hyper-V host
    MVMC can be deployed with minimal dependencies. Because MVMC provides native support for Windows PowerShell®, it enables scripting and integration with data center automation workflows such as those authored and run within Microsoft System Center Orchestrator 2012 R2. It can also be invoked through the Windows PowerShell® command-line interface. The solution is simple to download, install, and use. In addition to the Windows PowerShell capability, MVMC provides a wizard-driven GUI to facilitate virtual machine conversion.
    New Features in MVMC 3.0
    The 3.0 release of MVMC adds the ability to convert a physical computer running Windows Server 2008 or above server operating systems or Windows Vista or above client operating systems to a virtual machine running on Hyper-V host.

Sample:

 

virtual machine converter_1

virtual machine converter_2

virtual machine converter_3

virtual machine converter_4

virtual machine converter_5

virtual machine converter_6

virtual machine converter_7

virtual machine converter_8

virtual machine converter_9

virtual machine converter_10

Hyper-V: The destination is not valid because it’s compressed

Live migration (LM) between Hyper-V hosts may fails with

“The virtual machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible with the hardware requirements on this virtual machine. Virtual machine operation failed at migration destination. The destination ‘PathToVM’ is not valid because it’s compressed”

dd

Reason:

We know that there are no special requirements for live migration in 2012/2012 R2:

http://technet.microsoft.com/en-us/library/hh831435.aspx

But if you have enabled “Compress this drive to save disk space” on the disk level and compression on the folder level, live migration fails.  Hyper-V doesn’t support compressed destination folder. I’ve never seen any official notes about it. If you have, please comment this post or contact me. IMO, it must be in the requirements for LM.

Disk:

live migration_hyperv_compression_1

Folder:

live migration_hyperv_compression_2

Based on the Russian TechNet thread:

http://social.technet.microsoft.com/Forums/ru-RU/cda694c2-2053-45ef-b360-7d25dded0e83/-hyperv-the-virtual-machine-cannot-be-moved-to-the-destination-computer?forum=WS8ru#55b1d6cf-3bc3-4b56-8c98-5fceb2f29a6b