Deploying new Windows server
Posted on 2013-05-20
I need some suggestions regarding deploying a new server.
We're a medium sized company that's not an IT oriented.....now this makes the managers think that you don't need quicker and faster hardware and ONE server is sufficient to run everything.Well, the time has come where we have to implement a new server to take the load of the current(Windows SBS 2011) one.
The three main culprits that takes up most of the RAM and processing speed is the following order:
1)Mic Exchange 2010 (majority)
2)SQL server 2008
3) Web apps and apps.
I'm looking at getting Win 2012 srv.Obviously there is a budget to adhere to.I'm thinking of converting the next srv into the db server because we don't need to buy CAL's for all the db users.We have one SQL license that covers all our Windows srv users on current srv but if i had to move all the Win srv users over from the SBS srv side i have to pay for +- 50 client CAL's because you can't migrate the SBS 2011 CAL's to the WIN SRV 2012.
The current srv will stay the main DC and the new srv the secondary.
I have not done a setup like this before where i have to do a migration from SQL srv and setup a WIN srv from scratch.