asked on

Need Advise Active Directory Domain controller

I am an Admin of a 200+ windows 2003 AD domain. It has been the practice where I work to use the (sole) domain controller as a application server, file server, dns server in addition to being the domain controller. The problem I see with this is that all my eggs are in one basket. If I have to reboot the server for any reason I take the entire network down. It seems a good idea to keep the DC as clean as possible and free from other applications/responsibilities. I would also think it puts a heavy load on that server. Can anyone point me litertature or books that I can show my boss a better way to set things up. Thanks in advance.

ASKER CERTIFIED SOLUTION

fetch_

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Juneaucounty

ASKER

One physical server. There are virtual and physical servers that could be made available but it does not seem to be a high priority to the higher ups to utilize them.

Juneaucounty

ASKER

Fetch:what is BCD?

fetch_

BCD --> BDC = backup domain controller. (Typo of BDC.)

This was the term used in Win NT networks. Now, with Active Directory, BCD, and DC are the same, but it's good to have more than 1 server running AD for the reasons you fear in your question.

Juneaucounty

ASKER

thanks fetch, I need some reassurance that the way we are running things is not good.