I was doing a Windows Server 2003 to Windows Server 2012 migration as fast as possible and one of the steps was to convert a VMWare machine (Server 2.0.2) to a Hyper-V disk using MVMC 3.0. There are plenty of articles out there on how to do this. In a nutshell, you run the following cmdlet in PowerShell after importing the psd1 module (import command included):
Import-Module “C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1”
ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath "R:\Virtual Machines\XPPro1\XPPro1-flat.vmdk" -DestinationLiteralPath "R:\VMs\XPPro1\XPPro1.vhdx" -VhdType FixedHardDisk -VhdFormat Vhdx
However, on my first try, I was running into the following error:
ConvertTo-MvmcVirtualHardDisk : No suitable drive was found at path (R:\Virtual Machines\XPPro1\XPPro1-flat.vmdk).
Parameter name: path
At line:1 char:1
+ ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath "R:\Virtual Machines\XPPro1\XPP ...
+ CategoryInfo : WriteError: (Microsoft.Accel...nversionService:DriveConversionService) [ConvertTo-MvmcVi rtualHardDisk], DriveNotFoundInPathArgumentException
+ FullyQualifiedErrorId : DiskConversion,Microsoft.Accelerators.Mvmc.Cmdlet.Commands.ConvertToMvmcVirtualHardDiskCommand
At first, I thought MVMC 3.0 didn't like XP since it's already EOL. Then I had the same thought about VMWare Server 2.0.2 since it's old and hasn't been updated in a while. Then upon five minutes more thought, I remembered that the "-flat.vmdk" file is not the actual disk despite being the multi-GB meat and potatoes of the disk. So, upon changing the above command to reflect the actual disk name:
XPPro1.vmdk (which is a 1k file)
I was well on my way again. Doh! Hopefully, you don't make the same mistake, but if you find yourself here, it might be that you did and I hope this helps.