I'm using powershell and ConvertTo-MvmcVirtualHardDisk cmdlet to convert .vmdk disks into .vhdx disks to be able to run them in our hyper-v environment. For some reason, the .vhdx files produced are huge, sometimes as much as ten times the original file size. Does anyone know why this is?
The source files are, for the record, from one of our clients so I don't really know how they were set up.
Thanks!