Migrating SBS server to 2012 Essentials but very confused
I have a small network setup that I am responsible for at work. I basically have less than 10 computers all using Win 7 and about 12 total users (never concurrent). I currently am using SBS 2008 but want to upgrade the server software to Server 2012 Essentials and a second server running 2012 standard running exchange. I am somewhat torn between ESXi and Hyper-v. Especially with ESXi's licensing costs increasing. My other confusion is with the release of the R2 variants and their licensing issues..
My initial thought is to use Server 2012 (not R2) to set up the Hyper-V and then run Essentials 2012 R2 virtualized as the DC and another instance running Server 2012 (not R2) and install Exchange 2013 on it. I feel that R2 would be the better choice for the DC because of the updates over the original essentials and making management somewhat simpler. What I'm not sure of is on the virtualization part.
Should I just install Essentials R2 on the physical server and just virtualize the 2012 standard with Exchange? This route kinda does away with the benefits of virtualization though (at least for the DC anyway).
So basically what do you think is the best configuration for 1 box with 2 Virtual servers?? Also what opinions on ESXi or Hyper-V???
1)I have a license and CALs for 2012 standard but NOT Standard R2
2) I was under the impression that there was an issue running Exchange 2013 on Standard 2012 R2.
Steve
Olaf De Ceuster
HyperV and Essentials work very nicely together.
With the essentials install you can even choose a HyperV or physical install and it will configure the system for you.
As far as licensing is concerned: You are allowed a physical + a VM with same license and 25 licenses included.
However if you only have 10 users consider still running SBS 2011 and migrate to save a few $.
Hope that helps.
Olaf
Cliff Galiher
For your two issues:
1) use the free hyper-v server then. You won't have the CAL issues and you can still meet the advice I gave.
2) never said otherwise. I didn't say the guest had to be the same version as the host, just that the not should always be the same version as the highest guest. So if one VM is essentials 2012 R2 and another is 2012 standard, you want the host to be based on 2012 R2 because of that first VM.
you want the host to be based on 2012 R2 because of that first VM.
Therein lies my quandary. I have the 2012 Standard license. (I also have essentials standard too) but was going to buy essentials R2 because I thought it offered enough improvements to make it worthwhile. I cant swing buying standard R2 also. Do they have a free hypervisor based on R2????
Cliff Galiher
Yes there is a free version of hyper-v based on R2. So use that, buy your essentials R2, and use your standard license for a second VM.
wrfdchief
ASKER
Yeah...I guess that's best. Why do they have the Hyper-V on Essentials R2 and tout it as a feature when you really shouldn't use it that way??
Hold on. Is it true that to use the remote management tools for Hyper-V you have to have Win 8??
Cliff Galiher
RSAT tools have always been version specific. To properly manage hyper-v 2008, you needed a vista (or higher) machine with RSAT. XP wouldn't do. 2008 R2 needed a win7 machine. vista RSAT didn't support the new features. 2012 needs win8, and 2012 R2 needs 8.1.
That is JUST for the RSAT GUI tools. You can always execute PowerShell commands, either locally or remotely, and 2012 R2 has a pretty full features set of PowerShell cmdlets.
1)I have a license and CALs for 2012 standard but NOT Standard R2
2) I was under the impression that there was an issue running Exchange 2013 on Standard 2012 R2.
Steve