Howdy Skev33!
Can't always have things as you would like but I think that - generally
speaking - this is way too many domain controllers. But then again, I can
not really make that statement as we have not a lot of information about
your environment.
In the single server environment ( possibly Small Business Server 2000 and
2003 ) all of your eggs are typically in one basket. There is usually a
reason for this ( money, money, money ). The concept of PDC and BDC does
not really exist anymore in the WIN2000/WIN2003 environment but I understand
what you are saying.
The Exchange Server running on a Domain Controller is alright, I guess. I
would typically prefer that the Exchange Server be running on a Member
Server. The Web Server being a Domain Controller is gonna be a big no-no!
I hope that it is only your Intranet 'Web' Server and not the machine that
hosts your publicly accessible web site. That would be, err, interesting.
The two File Servers also being Domain Controllers - this would normally not
make me peep too much. So, in a perfect world - with very little
information - I would say that the DC on which Exchange is running *COULD*
be a great candidate for dcpromo and that the DC on which the 'Web Server'
is running *WOULD* be a really great candidate for dcpromo.
But, again, we have very little information from you so I can not make
anything but very general observations.
HTH,
Cary
skev303 said:
Hi Cary,
We have our PDC which is ok
Our Exchange server is a DC
Our web server is a DC
Our 2 x file servers are both DC's !
Im used to either single server enviroments or a PDC with a BDC in reserve.
----- Original Message -----
From: "Cary Shultz [A.D. MVP]" <
[email protected]>
Newsgroups: microsoft.public.win2000.active_directory
Sent: Thursday, October 28, 2004 12:46 AM
Subject: Re: Multiple Domain controllers
Skev33,
Where do you get the idea that having multiple Domain Controllers is a bad
idea and how is the 'general flakiness on the network' caused by having
multiple Domain Controllers?
Cary
flakiness