RE: Exchange 2k Server as Domain Controller

  • From: "Lorie Gordon" <lgordon@xxxxxxxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 7 Nov 2002 11:40:38 -0600

My 2 cents...
In our environment it would have been a big mistake to make our Exchange the
DC and the GC.  Our DC is having serious problems right now and it is nice
that I don't have to worry about rebuilding my Exchange server even though I
have to rebuild the DC.  Rebuilding the DC will be a major job by itself.  

-----Original Message-----
From: Scott Van Singel [mailto:svansingel@xxxxxxxxxxxxxxxxx]
Sent: Thursday, November 07, 2002 9:49 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Exchange 2k Server as Domain Controller

I have had our server go down 4 times since we implemented Exchange2000. 
The first thing the techs (at Microsoft) would ask is, "is your Exchange
server a Domain controller?"
It always seemed that they sounded relieved that the server was not a DC. 
I also talked to some Techs about the Global Catalog being on another
server. If you have Exchange as a DC and GC Server then there is a large
load on the server. If your server is a Gig connection and depending on the
amount of traffic it should be ok but, it is always better to offset the
amount of traffic on that server. 

Long story short, if you have enough servers keep the Exchange a Member

Just my option. 

-----Original Message-----
From: Whitaker, Matthew [mailto:Matthew.Whitaker@xxxxxxxx]
Sent: Thursday, November 07, 2002 9:49 AM
To: [ExchangeList]
Subject: [exchangelist] Exchange 2k Server as Domain Controller

I have found many articles stating you should NOT make your Exchange
2000 server a domain controller.  However, I have found just as many
articles stating that it is OK as long as you have a good server.  I am
looking for opinion only.  Don't need facts (I have them pointing both
ways.)  Please let me know what your personal experience or opinion is
with having Exchange 2000 server as a Domain controller....
*** Confidential ***
The information in this email is confidential and may be proprietary or
legally privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended recipient,
please reply to the sender that you received the message in error and then
delete or destroy the message along with any attachments. Thank you.

Other related posts: