Microsoft Tightening the Virtualization Gap with MVMC – Microsoft Virtual Machine Converter

Move over VMware. Once again Microsoft proves you cannot count them out. With the launch of Microsoft Microsoft Virtual Machine Converter – MVMC, it demonstrates Microsoft’s commitment to winning more market share with their Hyper-V product. Side by side migrations are always a challenge. Introducing another vendor in a side by side migration adds that layer of complexity. With MVMC users can now easily migrate their virtual machines from the traditional VMware infrastructure over to Microsoft’s Hyper-V platform. Microsoft knows it will not be easy for the die hard VMware admins to move their VMs over to the ugly big, bad hated Microsoft Platform. However, Microsoft just made the business case to management a whole lot easier to justify. Remember the reluctance when we had to move from Novell Netware over to Microsoft Windows NT / Networking. Despite the kicking and screaming, the transition happened and we survived. I have been hard on VMware over the last year. A few months ago, I wrote about the Microsoft’s competitive white paper against VMware. I often feel like VMware is running out of things to say. The ironic part is that they have some of the best speakers and thought leaders in the game. I have stated several times Dr Steve Herrod is my personal favorite.

The Microsoft Virtual Machine Converter – MVMC Solution Accelerator is a Microsoft-supported, stand-alone solution for the IT pro or solution provider who wants to convert VMware-based virtual machines and disks to Hyper-V®-based virtual machines and disks.

I typically don’t get into writing technical articles on subjects I don’t have much experience on. However this one could not be any easier. All details for MVMC are located here.

Once installed you can use Microsoft Microsoft Virtual Machine Converter to:

  • Convert VMware virtual disks using the command-line interface.
  • Convert virtual machines using the command-line interface.
  • Convert virtual machines using the GUI.
Although you probably wouldn’t need it to install MVMC msi package… Here is a link to the user manual.
Here are a few screenshots to show how easy the migration is.
Specify the source VM location
Select the VM you wish to convert.
Specify the credentials on how to connect to this VM.
Specify the workspace location. Be sure to have enough free disk space!
Select your Hyper-V destination location.

Once the conversion has completed successfully, MVMC starts the virtual machine and leaves it as it is. If you do not want the virtual machine to be started, go to the Hyper-V manager in the destination server and shut down the virtual machine. When the virtual machine conversion has completed successfully, you will see the Completion page.

Before installing Microsoft Virtual Machine Converter Plug-in for VMware vSphere Client, you will need one of the following versions of vSphere Client, in addition to the system requirements for Microsoft Virtual Machine Converter:

  • VMware vSphere Client 4.1
  • VMware vSphere Client 5.0

Hope you enjoy.