Thanks for the reply.
We have tried to use the "ConvertTo-NaVmdk" commandlet and get the following error.
PS C:\windows\system32> ConvertTo-NcVmdk -SourceVhd x:\d37fb41f-556d-47c0-ab60-656444be2e5b.vhd
ConvertTo-NcVmdk : Specified argument was out of the range of valid values.
Parameter name: File is not a fixed-size VHD.
At line:1 char:1
+ ConvertTo-NcVmdk -SourceVhd x:\d37fb41f-556d-47c0-ab60-656444be2e5b.vhd
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [ConvertTo-NaVmdk], ArgumentOutOfRangeException
+ FullyQualifiedErrorId : File not fixed VHD,DataONTAP.PowerShell.SDK.Cmdlets.HyperV.ConvertToNaVmdk
Does the VHD need to be a fixed size VHD to work? We can't do this with a thin VHD?
Thanks!