Windows Server 2008 R2 Thread, Best practice for use and number of servers in Technical; Hey there everyone,
Our school network is running around 600 clients, with 16 servers – 4 physical, and 12 virtual. ...
31st May 2012, 06:03 PM #1
- Rep Power
Best practice for use and number of servers
Hey there everyone,
Our school network is running around 600 clients, with 16 servers – 4 physical, and 12 virtual. The servers are, or at least were all 2003 or 2008, with all Dcs all running 2008.
We are making relatively good progress on a project to rollout Windows 7. As part of this, there is quite a lot of backend stuff that we need or would like to do, upgrade AD Schema, raise AD domain functionality level, replace as many of the 2003 servers as possible, upgrade the DCs to 2008r2 and introduce some newer technologies and features such as DFS.
As part of all of this, i’ve been thinking a little bit about the actual use and number of servers in our domain. There seems to be some a good number of considerations and implications for this. For example, how much does one try to separate various services and software - at what point are the gains in management and redundancy outweighed by extra costs considerations (hardware, licensing, power ect). How many servers is “too many”? What about how to go about mixing and matching various services and software? is it good to separate 3rd party software from Windows services or even themselves? What are suitable services to run on DCs? (KMS comes to mind). What about Windows services that run best on a dedicated server (Exchange being a good example).
I’d love to hear any thoughts and feedback on this, in particular how your own servers are setup, and how you would go about setting them up if building your network again from scratch.
(bit of a general topic, I did have a quick look for similar topics but didn’t find anything too similar, apologies in advance if I missed any useful, recent and similar threads)
IDG Tech News
31st May 2012, 06:28 PM #2
For Exchange I would use a dedicated server (Physical or virtual). Depending on the HA/DR number of users etc will determine the number of servers you need and of course the speco fhte physcial/virtual services.
1st June 2012, 01:55 PM #3
When dealing with virtual servers, I have always believed it is most sensible to allocated only what resources are required and then run everything on its own machine. Sure, its more of a pain to patch lots of windows boxes, but having a dedicated box for everything makes backups and restores easier, reduces impact of errors and downtime, things like that.
1st June 2012, 02:31 PM #4
Now we're on VMware I keep everything separate... whereas before I had a "management server" that had all the irritating apps like door control, photocopier accounting etc they all get their own VMs now. Less chance of something conflicting (usually IIS) and gives a bit more control for upgrades etc.
By tarquel in forum Windows 7
Last Post: 24th September 2013, 11:17 AM
By Resolver in forum Windows Server 2000/2003
Last Post: 28th July 2011, 03:37 AM
By Stuart_C in forum Windows
Last Post: 30th April 2009, 04:45 PM
By dezt in forum Wireless Networks
Last Post: 30th June 2006, 12:51 PM
By FITS in forum Courses and Training
Last Post: 8th September 2005, 03:24 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)