Windows 2016 has some impressive improvements to Hyper-V, in fact, some of them look like they may well give VMWare a bit of a run in so it'll be interesting to see how things stack up once 2016 has had time to be deployed to a few datacenters.
My first test for any new Windows based OS is to test out the WIM file deployment through WDS. With Windows 2016 TP5, this worked perfectly and it even allowed me to use the same unattend file I created for Windows 2012 R2
My first test in HyperV was to migrate a machine from Windows 2012 R2 Hyper-V to 2016 TP5, as this is going to be something a lot of IT departments will look at first, after all, if you can't get your VM's into 2016 then the take up will almost certainly be slower.
I was a bit surprised when the move didn't work, it generated an error saying I never had permissions which was a bit strange.
A move from one 2016 server to another went without error.
Aside from that little bit of strangeness, the move from 2012 R2 to 2016 worked pretty flawlessly.
Upgrading a VM's configuration from 2012 R2 (Version 5) to 2016 (version 7.1) is straight forward and takes no time at all but like VMWare, it has to be done whilst the machine is powered off.
One other improvement that has been long overdue is the ability to add a vnic to a live VM. This is something that has been in VMWare for years and yet was strangely absent from Hyper-V until now.
After using Hyper-V in 2016 for a few hours, I'm impressed with the changes, many of which are long overdue to bring Hyper-V onto a level playing field with VMWare. The MMC for it though is still many times more clunky that that offered by VCentre.