Some cmdlets (*-VMGroup, *-VMHostCluster, etc) are only available on new enough versions of Hyper-V.
This should be detected so such actions can be handled intelligently.
Worth noting is that this should probably be done in a manner that only cares about the directly accessed machine, since that one is the one that will actually be executing cmdlets.
Some cmdlets (
*-VMGroup
,*-VMHostCluster
, etc) are only available on new enough versions of Hyper-V.This should be detected so such actions can be handled intelligently.
Vagrant's method of doing this;