Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 297
  • Last Modified:

Server migration

We've got two servers:
1) SBS 2011 - Functions as application, file, Exchange server. (domain controller)
2) WIN 2012 - DB server.

We've reached almost 65 users (max 75) on the SBS '11 and as you can imagine the i/o and memory consumption on this machine is intense especially when the RAM's limited to 32GB.

I want to leave Exchange on the SBS and migrate the rest to the WIN 2012 srv.
This means i only have to acquire CAL's for the WIN 2012 srv and don't have to buy Exchange 2013 with the very expensive Exchange CAL's.

So my question is,can we have change the 2012 srv into the domain contoller and leave the SBS 2011 as the Exchange mail server?
0
The_Nibbler
Asked:
The_Nibbler
3 Solutions
 
Cliff GaliherCommented:
Nope. -One of the trade offs for the price break you get on SBS and SBS CALs is that you cannot split apart the components. SBS must be a domain controller, and must in fact hold all of the DC FSMO roles. No exceptions.
0
 
Simon Butler (Sembee)ConsultantCommented:
You can make the other server an additional domain controller though (which would be a good idea for this number of users), and it can also be a global catalog. However you cannot move the FSMO roles to that server. You will also be unable to upgrade the forest/domain to Windows 2012.

Simon.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
I'll differ slightly from Cliff's comment.

He's absolutely correct in that SBS must be a domain controller and hold the FSMO roles and that you cannot remove exchange from it.  

BUT, you explicitly asked:
So my question is,can we have change the 2012 srv into the domain contoller and leave the SBS 2011 as the Exchange mail server?
And, in fact, you CAN make the 2012 server a DC in the domain.  It just can't hold the FSMO roles and you cannot remove the DC functionality from the SBS server.

BUT (a different BUT), it's almost pointless to do so anyway.  BY FAR, the most intensive application on the SBS server is going to be Exchange.  AD function is MINIMAL in terms of system resources.  So while you can add a second DC (and *IF* you ACTUALLY understand AD recovery, I'd recommend you do so), it's not going to do anything noticeable in terms of lightening the load on the SBS server.

You MIGHT be able to improve the SBS server performance a little by setting up WSUS on another server and tweaking the SQL instances and their memory usage... but in general, you're likely stuck with what you have and the only way you're going to get much more performance is going to be to replace the hardware with faster hardware (disks, most likely).  Though even that is no guarantee as it REALLY depends on where your bottle neck lies (determined through analysis of performance counters).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now