Add configuration version option when creating VM's via SCVMM and WAP
When adding a new Windows 2016 Hyper-V cluster to SCVMM, all VM's deployed to the new Windows 2016 cluster automatically deploy from SCVMM as a configuration version 8.0 machine. In order to allow time to upgrade all other Hyper-V Servers still running Windows 2012, it would be good to have the option to have a choice of configuration version of the VM. This is currently only possible if creating a VM directly on the Windows 2016 Hyper-V server itself. When creating VM's directly on a Windows 2016 Hyper-V server one can use the cmdlet "New-VM" and specify the configuration version using "-Version". The problem is that you cannot migrate any VM's off a Windows 2016 Hyper-V server back to a Windows 2012 R2 Hyper-V Server without the configuration version being 5.0. If any of our new Windows 2016 Hyper-V servers had an issue we will be in deep trouble, being unable to migrate any configuration version 8.0 VM's off to any other of our Windows 2012 R2 Hyper-V servers. Please consider adding this same option to SCVMM (New-SCVirtualMachine) and Windows Azure Pack (New-WAPackVMRole). This would be extremely helpful to maintain VM's across SCVMM, while we make progress in converting to Windows 2016 Hyper-V across all infrastructure.