Expiring Today—Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

I have two 2003 DCs.  Should BOTH of them be Global Catalog servers as well?

Posted on 2008-06-10
11
Medium Priority
?
238 Views
Last Modified: 2011-09-20
Just curious, because when one of them goes down, no one can connect to Exchange or anything......I'm wondering if making them both Global Catalog servers would fix this issue, as I believe that5's what having two DCs is all about in the first place!  Good idea?  Bad idea?  If I make them both GC servers, do I have to do anything on the Exchange side so that Exchange is aware of both?
0
Comment
Question by:tenover
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
  • 2
  • +3
11 Comments
 
LVL 35

Expert Comment

by:rakeshmiglani
ID: 21752361
no changes are required on exchange.
it will pickup the GC/DC automatically
0
 
LVL 1

Expert Comment

by:SowelaIT
ID: 21752482
This really depends on your domain set up.  If this is a single domain then you really only need one GC.  I'm told that unless you need a second GC you really should not put multiple GC's on your domain controllers due to increased replication traffic which could place a large overhead on those servers.

As for the Exchange problems:
The suggested ratio is 1 Global Catalog for every 4 Exchange 2003 servers. Now, if you have a small number of users on Exchange and a few well powered servers, you can put it on each DC.  The best and only true way to test if this setup will work for you is to make a copy of your GC on your other DC and watch the processor and memory on each server, as well as watch for slow logins, Exchange issues,  and other issues caused by domain and GC latency (such as problems in the Universal Group Membership lookup areas, etc.).
And if you find that it puts too much of a strain on the domain, just put it on your most reliable DC and cross your fingers.
0
 
LVL 8

Expert Comment

by:Jeff Perry
ID: 21752484
What version of exchange server are you running?

I have noticed that when my GC is rebooted that users loose connectivity to our exchange 2007. I am considering putting GC back on our other DC to see if it prevents this as well.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 1

Expert Comment

by:SowelaIT
ID: 21752517
Also, when moving the GC, remember to check into FSMO roles best practices.

http://www.windowsdevcenter.com/pub/a/windows/2004/06/15/fsmo.html
0
 

Author Comment

by:tenover
ID: 21752591
I'm not moving the GC.  I wanted to know if adding the GC role to my second DC would resolve the issue of Exchange 2003 not being available when the DC/GC is down or being rebooted.  I'm running Exchange 2003 Enterprise with about 150 mailboxes.  Single domain at a single site.  All servers are Dell Poweredges bought in the past 3 years.
0
 
LVL 1

Expert Comment

by:SowelaIT
ID: 21752781
To be honest, I have run dual GC's on our domain.  We were having problems with one and instead of running out at midnight to reboot the dead machine I just duplicated it and rebooted in the morning.    

The good thing about running two GC's is that it the computers needing access to the GC may be sped up due to the round robin questioning of the GC.  

Personally I would go for it but I would try it out on a weekend or some time when traffic is not at the greatest.
0
 
LVL 27

Expert Comment

by:DrDave242
ID: 21753065
I'd say go for it.  With a single domain and single site, replication traffic won't be much of an issue, if at all; it's not like you're replicating over a slow WAN link.  Making that second DC a GC will give you redundancy in case the other one goes down, although if your DC is going down more than once in a blue moon, there's a problem that you'll really want to look into.
0
 

Author Comment

by:tenover
ID: 21753239
That's what I thought.  And no, the DC's have never gone down, but occasionally I'll need to reboot or something.  Should just making both GCs allow access to Exchange if one is down, or is it ALSO dependent on the FSMO roles?
0
 
LVL 27

Expert Comment

by:DrDave242
ID: 21753330
During installation, Exchange needs to contact the Schema Master in order to extend the AD schema, but I don't believe it's dependent on any of the FSMO roles during normal operation (although it needs to sync time with the PDC Emulator like everything else in the domain).
0
 
LVL 6

Expert Comment

by:raptorjb007
ID: 21753377
It is best practice to have at least two GC's configured in any domain. Any additional GC's depend on your environment, ie remote sites with no redundant wan link, overloaded DC's etc etc.

My option is that you should definitely configure the second DC as a GC as the additional load in a smaller environment is negligible.
0
 
LVL 1

Accepted Solution

by:
SowelaIT earned 2000 total points
ID: 21753494
The five FMSO roles (PDC Emulator, RID Master, Infrastructure Master, Domain Naming Master, and Schema Master) are not neccessary for Exchange to do it's job.  If they are off line for a few minutes for a reboot, you may not be able to do things like add computers or install Exchange, but your email should work just fine.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses

718 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question