I’m revisiting my “hyper V role ON Essentials post” and reposting what I posted into the Home Server forums as a response ….
Okay let me explain why I think Paul has a screw loose.
1. Let’s go down the road of licensing. The only way you can afford doing what he’s recommending is to use Technet licenses. Technet are only to be allowed for testing. We go down the road of “wink wink” we do a LOT of testing. It’s a gray area. To properly license using that “stick a Windows 2012 key and flip it to a standard” you’d be buying $425 Essentials and a $800 standard plus user cals. Yeah, right. That’s realistic. Like not. $425 isn’t a realistic home server price tag either if you really want to be honest with ourselves.
2. The 1+2 right problem and the HyperV role on a domain controller problem. Let’s say that you are the wealthiest person on the world and think nothing of spending $1200 on a home setup. Okay so you put the Server 2012 key in the Essentials box and transformed/transmorg’d it to a standard sku. This keeps the goodness of Remote web access and client backup but destroys media streaming as that’s no longer supported and now gone as part of this transform thing. Paul didn’t talk about that, did he? Then we have the problem of his recommendation of the HyperV role. Microsoft does not recommend installing the HyperV role ON a domain controller. And when you transform that Essentials box with a Standard key, it’s still a domain controller. You can’t dcpromo it down without it destroying client backup/remote web access. You have to leave it as a domain controller. The only time I see Microsoft talk about having your DC have the HyperV role is when they have one on a demo laptop going out in their “Evangelist role” talks. On a production machine you don’t want a domain controller to also have the HyperV role. For one you now take one of the virtualization rights away from the 2012 as by EULA you can’t run any other role on top of the HyperV without breaking that 1+ right thingy.
Having additional services running with HyperV isn’t tested or supported by Microsoft. On SBS standard , having that synthetic nic be there with real one would really screw with the brains of the sBS wizards. The essential wizards are in the same boat. It was not built/tested/designed to have the HyperV role running on it.
3. Paul forgot that Windows 8 can how be a hyperV host so if you REALLY want to have a hyperV box and have your cake and home server too, I’d make Windows 8 (a much cheaper solution) be the HyperV base.
Bottom line it’s a licensing issue (that Paul glosses over and doesn’t touch on), it’s a support issue (you just destroyed media streaming, the HyperV role on a DC isn’t something that is supported/recommended, Microsoft support can’t back you up, etc etc).
It’s just a messy solution when there’s now a much more elegant solution – use Windows 8 as your HyperV base.