Also, in the followup post on the blog they actually do another interesting lab that requires this first bit.

@darek-hamann said in Configuring Windows Server 2016 Core. Part 2: Hyper-V role installation:

@dashrender

This is actually a great article! It simplifies the procedure of installing a Hyper-V role from a GUI free Windows 2016 Core setup.

That's nice, but again - WHY. This is not the way you should NORMALLY install Hyper-V because now you have a license tied to the hardware. I get that there are reasons, but I'm asking what they are.

@dashrender said in Configuring Windows Server 2016 Core. Part1: Installation:

@jaredbusch said in Configuring Windows Server 2016 Core. Part1: Installation:

@wirestyle22 said in Configuring Windows Server 2016 Core. Part1: Installation:

@aidan_walsh afaik there is no reason to install it as a role. All it does is create unnecessary licensing dependencies.

The main reason some people do it is for auto activation of guest windows machines. That is no reason to ever do it IMO.

If every physical server is a Datacenter license then it is pretty transparent also.

But I still do not feel that Installing in this way makes sense.

Yep, KMS server to the rescue.

Correct. If you are big enough to have Datacenter licensing, spin up another VM and setup KMS.

That's a very good post that covers information people don't often think about after deploying vCenter. Additionally, it's something helpful when studying for the VCP-DCV. Thanks for sharing!