Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

What are the pros and cons to making our Exchange 2003 server a DC? 1

Status
Not open for further replies.

mb96net

IS-IT--Management
Feb 4, 2004
6
CA
Is there any reason I would not want to make my Exchange 2003 server a domain controller as well? It wouldn't be the only DC in the site, but having another DC in this site would be nice, and if it's a Global Catalog Server wouldn't it speed things up and reduce network load as well?
 
The advantage of having your Exchange be a DC is that you can make it a Global Catalog. If Exchange looses contact with a GC it shuts down email, so having it be local can be a big help.

Microsoft typically recommends that you not set Exchange on a DC, but the reasons for this only apply to very large Enterprises. Small to medium IT shops don't need to worry about that.

The one pitfall of this is that if Exchange is on a DC, and if you have a public IP enabled on that server, then you are increasing your risk. (Public IP + AD Access = Increased Security Risk).


I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
I think the article above backs up what I have said. A small to medium sized business isn't going to have a cluster, and the extra DC/GC is probably a good thing.

I would disagree about the /3GB switch, particularly with Windows 2003 which supports the new /userva switch.

The slow shutdown can easily be overcome by manually stopping the Exchange System Attendant and its dependancies before teling the system to shut down.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
You are absolutely right Mark, and I should have been more careful when providing a link that may have confused the poster when a staisfactory answer had already been provided.

Regards

Darren

 
mlichstein, THANKS, you solved a problem I was researching but letting me know about this KB.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
The issue I have found (and now I can't easily go back) is with the disaster recover if the server fails.

Microsoft KB:822945

Rook
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top