08-22-2015 08:26 PM
If you're anything like me and happen to already have Hyper-V running on your machine (personal-use machine) and you want to keep Hyper-V running, you should quickly learn that Hyper-V and VMware Player aren't compatible on the same Operating System. I suppose you could spin up VMWare Player within a Hype-V image and get something to work, but I didn't want to even attempt going down that road. Instead, I looked into rconverting an VMware image to Hyper-V.
Let me provide some help in converting a VMware image to a Hyper-V image, in the hope that it will help someone else out:
#Pre-Check: Make sure you have privileges to execute the PowerShell script by running it as the Admin, or perhaps changing the Set-ExecutionPolicy variable. #Make sure proper cmdlet is loaded before attempting to run Import-Module “C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1" #Just for reference for any future improvements if needed get-command -Module mvmccmdlet #Where the actual conversion takes place ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath “<FULLY QUALIFIED SOURCE PATH WITH FILE NAME>.vmdk” -DestinationLiteralPath “<FULLY QUALIFIED TARGET DIRECTORY" -VhdType DynamicHardDisk -VhdFormat Vhdx
As you can see, the hard work is done by the MVMC tool and I just supply a few arguments to define the source file, output directory, and vhd type I want, and it does the rest. It does take a bit to convert an image, so don't do it when you're in a rush.
Hope this helps you out!