On October 1st Microsoft released their Microsoft Virtual Machine Converter Solution Accelerator which includes Microsoft Virtual Machine Converter Solution Accelerator and the Microsoft Virtual Machine Converter Plug-in for VMware vSphere Client. This solution accelerator kit enables to covert Virtual Machines from VMware vSphere to Microsoft Hyper-V. I also tested the release candidate of Microsoft Virtual Machine Converter Solution Accelerator in July.
Some more information about the Microsoft Virtual Machine Converter features:
- Converts and deploys virtual machines from VMware hosts to Hyper-V hosts including Hyper-V on Windows Server 2012. As part of the machine conversion MVMC converts the virtual disks attached to the source virtual machine. It also migrates configuration such as memory, virtual processor and so on from the source virtual machine to the converted virtual machine deployed on Hyper-V. It adds virtual network interface cards (NICs) to the converted virtual machine on Hyper-V.
- Converts VMware virtual disks to Hyper-V based virtual hard disks (VHDs).
- Supports conversion of virtual machines from VMware vSphere 4.1 and 5.0 hosts to Hyper-V.
- Note MVMC also supports conversion of virtual machines from VMware vSphere 4.0 if the host is managed by vCenter 4.1 or vCenter 5.0. You have to connect to vCenter 4.1 or 5.0 through MVMC to convert virtual machines on vSphere 4.0.
- Offers fully scriptable command-line interfaces for performing virtual machine and disk conversions that integrates well with data center automation workflows and Windows PowerShell scripts.
- Has a wizard-driven GUI, making it simple to perform virtual machine conversion.
- Uninstalls VMware tools prior to conversion to provide a clean way to migrate VMware-based virtual machines to Hyper-V.
- Supports Windows Server guest operating system conversion, including Windows Server 2008 R2, Windows Server 2008 and Windows Server 2003 SP2.
- Enables conversion of Windows client versions including Windows 7.
- Installs integration services on the converted virtual machine if the guest operating system is Windows Server 2003 SP2.
First you have to install the vSphere Client, the Microsoft Virtual Machine Converter Solution Accelerator and optional the Microsoft Virtual Machine Converter Plug-in for VMware vSphere Client. The Microsoft Virtual Machine Converter Plug-in for VMware vSphere Client allows you to convert a Virtual Machine directly from the VMware vSphere Client.
Here you can download the Microsoft Virtual Machine Converter Solution Accelerator.
To convert a Virtual Machine you have two options. First you can open the Microsoft Virtual Machine Converter. You can connect to your stand-alone ESX host or your vSphere vCenter server.
After you have connected to your vSphere environment, the Virtual Machine Converter will scan for Virtual Machines which can be converted, and you can select the VM you want to convert to Hyper-V.
The second way is by using the Virtual Machine Converter Plug-in from VMware vSphere Client. You can right click on the Virtual Machine you want to convert and select Convert to Hyper-V virtual machine and this will launch the Virtual Machine Converter.
In both cases you have to connect now to the guest in the virtual machine.
Select a Workspace where the virtual machine disk will be converted.
Configure the destination Hyper-V host.
After that you will get a summary and you can start the conversion.
The Virtual Machine Converter does also offers fully scriptable command-line interfaces for performing virtual machine and disk conversions that integrates well with data center automation workflows and Windows PowerShell scripts.
for example:
MVMC.exe /SourceHost:esx01 /SourceHostUser:MVMCAdmin /SourceHostPwd:Passw0rd /GuestVM:test03.cloud.win /TargetHost:hyperv02.cloud.win /TargetVHDPath:\\hyperv02\D$\Test03
Tags: convert, ESX, ESXi, Hyper-V, Microsoft, Microsoft Virtual Mach, Microsoft Virtual Machine Converter, MVMC, Plug-in for VMware vSphere Client, Virtual Machine, VMware, VMware ESXi, vSphere, Windows Server, Windows Server 2012 Last modified: October 15, 2012