Global Catalog Server

  • Thread starter Thread starter Andrew
  • Start date Start date
A

Andrew

Hi All,

I have read that a global catalog server is required to process logon
requests.

If you have multiple domain controllers for a given domain, does this mean
that both require to be Catalog Servers in order for the domain to process
logins whilst one of the domain controllers is unavailable?

E.G. DC1 is the catalog server, DC2 is not a catalog server. If DC1 goes
offline, will clients be able to login using DC2?


Regards,
Andrew
 
So they both need to be GC's in order to allow the secondary to authenticate
logins? Well im glad i know that, thanks!

I have heard that having many GC's can create bandwidth issues due to
replication, is that correct?

Andrew
 
Andrei said:
in a single domain scenario there's no need to worry.
Click to expand...
In a single *site* scenario, surely? Though it should not be
a problem if there aren't too many satellite sites.

Cheers,

Cliff
 
Andrew said:
Hi All,

I have read that a global catalog server is required to process logon
requests.
Click to expand...

Not always true -- it is true of Native+ mode.
If you have multiple domain controllers for a given domain, does this mean
that both require to be Catalog Servers in order for the domain to process
logins whilst one of the domain controllers is unavailable?
Click to expand...

No, and in a large multi-domain forest you should think of GCs
as something you need PER SITE (they are really a forest wide
job).

But in such large forests there are likely many domains so they
GCs can be fault tolerant without every DC being a GC.

BUT, in a small forest, especially a single-domain forest you
should generally just make every DC a GC.
E.G. DC1 is the catalog server, DC2 is not a catalog server. If DC1 goes
offline, will clients be able to login using DC2?
Click to expand...

Perhaps, but there is no reason to do that in a small forest or
any single-domain forest.

Just make them all GCs.
 
Back
Top