Hi, long time visitor first time poster. I'm sys-admin for a small education company and have recently been given control over our servers (all sever 2003). Problem is that the network I've inherited is a bit of a mess and I need some advice to sort it out. Basically I've got one server doing virtually everything: Server1: File, Print, Exchange, Application, Backup, AV, DHCP, DNS, WINS & Domain Controller (AD). I've got another server running ISA, and another doing basic file and print. But I've just decomissioned an fairly new server (server2) and have an older spare (server3) that I can use to help take the load off the main one. My question is; in my situation how would you spread out the services most effectively and with minimum interruption? My thinking is Server3 could take over DHCP & WINS and Server2 could take on exchange, but my knowledge of designing a server setup are limited. Does anyone have any suggestions or advice? Thanks Mark

My question is; in my situation how would you spread out the services most effectively and with minimum interruption? Well, I'd want redundancy for Active Directory so I'd make one of the server's a redundant DC. That server could still do something else besides so after looking at your ideas on how to spread things out a bit, I'd go with that. I'm thinking Server 2 would be a good candidate for a redundant DC since it's been decommissioned and you'll likely be redoing it. What you've detailed seems like a good idea on how to spread the load around. My skills and knowledge of Exchange are limited so I couldn't tell you how much work it would be to move it from one server to another. Hopefully, someone else with more experience and knowledge of Exchange will tell you if it's a good idea or not.

Thanks CurtR, To be honest I hadn't even considered a second DC, but that's a great suggestion. I think what I'm really asking is that I've got 3 servers and I need to distribute the DHCP, WINS, DC, DNS, file, and print services across them properly. Anyone with some knowledge of the best combination for a small (50+) office would be very helpful. Thanks Mark

both dcs would hold the global catalog both dcs would be dns servers [ad intergrated] leave exchange where it is move print services to server2 don't concern yourself over dhcp - very small load consider DFS/FRS to replicate the shares between the servers so it one goes down you still have data access I would be concerned though when I hear about new server admins and decommissioned servers. Make sure you have a complete understanding of how things are put together [as well as documenting them] before you make changes. Company downtime can cost you plenty, including your job

Cheers Wanderer, I made tripley sure that the old server was no longer in use before decomissioning and then switched it off and left it for two weeks in case anybody freaked out. I should also have mentioned that this network is part of a two office WAN. Users at my officer have been complaining about the speed of the network (accessing files and emails) and that's down to virtually everything being on one server here. If I stick DC and print on Server 2 I'm thinking that that'll take a sizeable load off of Server 1 (which is being thrashed to death at the moment). Would it be worth migrating AD onto server 2 as I understand that it doesn't get on well with exchange, or would simply having 2 DC's be enough? Mark

Need to know your hardware specs for each of these servers. memory cpu disks and how configured [standalone or raided] network backbone [what the server and pcs connect to] You have 2003 enterprise listed. Is this SBS by chance? Do you have defrag secheduled on the servers? There are more factors to poor network performance than just the servers which is why I am asking.