[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] Don't put a HyperV role ON a transmorg'd Essentials box - THE OFFICIAL BLOG OF THE SBS DIVA
Tue, Oct 9 2012 16:40 bradley

Don't put a HyperV role ON a transmorg'd Essentials box

" In-place upgrade to Windows Server 2012 Standard

If your small business grows and exceeds the 25 user cap in Essentials 2012, Microsoft is for the first time offering an in-place upgrade to Windows Server 2012 Standard. (In the past, you had to do a more complex migration.) I’ve not fully explored this option, but according to Microsoft, this upgrade brings over all of the unique Essentials 2012 features—centralized PC backup, network health alerts, and so on—to Microsoft’s mainstream server, and provides access to Hyper-V. There is one limitation: Many Essentials 2012 features—like centralized PC backups—will still be limited to the first 25 users. But I’m surprised Microsoft’s even allowing this. Now there’s no penalty for being successful.

(And yes, I can already hear the enthusiast’s mind working here: So you’re saying I can get both Essentials 2012 and Hyper-V on one machine by doing an in-place upgrade? Yes. I am saying that.)"

http://www.winsupersite.com/article/windowsserver2012/windows-server-2012-essentials-144448

How about we get a little less enthusiastic about putting the HyperV role ON a domain controller there, Paul.

How about you get enthusiastic about the idea of having Windows 2012 as a hyperV parent and then using downgrade rights to install Essentials in one VM.  Then use the 2012 key to transmorg yourself past the 25 user limit.  (and I didn't think that the client backup was limited to 25 pcs after the transmorg?)  In fact it clearly says support for 75 here: http://technet.microsoft.com/en-us/library/jj247582.aspx

HyperV role should not be on anything but a plain server.  Don't add the hyperV role to a domain controller.  Not only does it break the 1+2 server rights (as you just used up one of your official licenses for the thing you stuck HyperV on, it just causes support issues for you.

Filed under:

# re: Don't put a HyperV role ON a transmorg'd Essentials box

Thursday, October 11, 2012 4:15 PM by Sam Manley

Really good point here as I did get too excited about the thought of Hyper-V in WSE 2012.

Another key thing I read in the Microsoft released stuff about a transmorged WSE 2012 to Standard - you'll lose the Meda Server with remote media access!!!!  Big deal if, like me, thats a dealbreaker.  

Also I really think being able to turn off the DC role of WSE 2012 would benefit those looking for a WHS replacement.

# re: Don't put a HyperV role ON a transmorg'd Essentials box

Thursday, October 11, 2012 4:38 PM by bradley

If you turn off the dc you'll break the rwa stuff.

You can make Win8 a hyperV parent btw