Summary: Use Hyper-V cmdlets in Windows Server 2012 to identify what a virtual machine needs.

 Is there a way to use Windows PowerShell to easily find why I can’t import virtual machine configurations when I perform a disaster recovery test on a Hyper-V Server?

 Use Compare-VM, target the .xml file with the configuration data,
          and then examine the Incompatibilities property in the output:

$TEST=COMPARE-VM –path C:\VM\\B0F4430E-6EC9-46DD-B4DD-E7EF8C5A1FC8.xml

$TEST.Incompatibilities