Microsoft Virtual Machine Converter: Converting to Hyper-V

Microsoft Virtual Machine Converter (MVMC) converts virtual machines (VMs) and disks in VMware hosts to VMs that can run on Microsoft Hyper-V hosts or Microsoft Azure. The utility is also used for converting server machines running Windows Server 2008 and above and client computers running Windows Vista and above to Hyper-V VMs. Retired in 2017, MVMC has since been superseded by System Center Virtual Machine Manager (SCVMM).

Standard Features in Microsoft Virtual Machine Converter 3.0

MVMC 3.0 was the last version officially supported by Microsoft. Released in 2014, its standard features include:

Conversion of Physical Machines and VMDK to Hyper-V

Conversion of a physical machine to a VM is commonly known as “physical to virtual,” or P2V, conversion. On the other hand, conversion of a VM to another VM format is known as “virtual to virtual,” or V2V, conversion. MVMC 3.0 supported both types of conversions. Either the GUI or a specific set of PowerShell functions can be used during the conversion process.

Hot or cold migration of physical machines and VMs is allowed in MVMC. Hot migration is when the OS is turned on; cold migration means the opposite.

When converting physical machines, you have the option to convert to Hyper-V or Microsoft Azure. Depending on your choice, you are asked for the destination path, then the conversion source, which can either be a VMware vCenter or an ESXi host. You can use either the GUI or PowerShell cmdlets to perform the actual conversion.

For VMware VMs, there are two conversion approaches:


Present Status of Microsoft Virtual Machine Converter

MVMC is still used unofficially in some quarters, but SCVMM is now widely used for managing VMware VMs in Hyper-V and Microsoft Azure. SCVMM integrates with VMware vCenter Server and supports VMs from VMware ESXi hosts, among other hypervisor platforms.

The Successor to the Microsoft Virtual Machine Converter

SCVMM enables deployment and management of VMs across multiple hypervisor platforms, including VMware vSphere hosts and vCenter servers. Using SCVMM, you can add a vCenter server and ESX/ESXi host to your Hyper-V or Microsoft Azure environment. Like MCVC, SCVMM can convert VMware VMs to Hyper-V-supported formats.

Other standard features of VMM include:

Parallels RAS Supports Hypervisor Flexibility

Parallels® Remote Application (RAS) is capable of managing VMs from major hypervisors such as Hyper-V and VMware ESXi, and it supports various hyperconverged infrastructures, including Scale Computing HC3 and Nutanix Acropolis. It also supports Microsoft Azure as a virtual desktop infrastructure (VDI) platform.

Parallels RAS simplifies VDI management through the use of customized templates for provisioning VDI desktops and guest VMs on demand. You need only to specify the number of VMs to be created using a template, and Parallels RAS will create and deploy the VMs across your organization.

Parallels RAS uses linked clones to replicate a virtual disk from an existing VM instead of creating another new VM. Thus, multiple virtual machines can share the same software installation. This helps organizations lower deployment costs significantly, also saving precious disk space and time.

With Parallels RAS, your organization can create a VDI that is multi-cloud ready and meets your unique requirements. Download the trial, and see how Parallels RAS can help simplify your VDI infrastructure.