So M$ released HyperV as a standalone installation so you don’t need to install Server2016 just to run HyperV.
Now, there are three ways to manage this HyperV thing.
- Use Powershell. You can do it, but it is for experts only. Faffed around a bit, but was like “nah, if something borks, I want my PFY or somebody else to be able to fix things and not faff around in a CLI”…
- Use SSL certificates. Naaah, was not up to that, too schleppful. If anybody managed to pull this off, do post here.
- Use a domain. Which I did. Quick (well, almost) and painless.
1x server running HyperV 2016 (make sure you gots the RAM, HDD etc)
1x laptop/desktop running Windows10.
Server2016 licence (for 8 cores).
Install the HyperV role on the Windows10 PC.
Create a new VM.
Install Server2016 into this VM.
Make it a Primary DC.
Once the primary DC is up and running, join both the Windows10 PC and the HyperV server to it.
Open the HyperV mmc on the Win10 PC, and connect to the HyperV server. Now you can add and manage your VM’s the easy way.
Oh, the extra Win10 licence? Install win10 as a VM and use that VM to manage HyperV that way.
The Server2016 licences is 4 for the PDC, and 4 for another Win2k16 install. M$ licences it per CPU core.
EDIT : post to be edited or amended, still new with this doohicky thing.