Global Catalog question

  • Thread starter Thread starter GK
  • Start date Start date
G

GK

In a W2K domain or 2003 domain structure and you have the global catalog on
the first DC. should you have another global catalog that will get
replicated onto another DC?

Thanks
 
The number of GCs that you deploy on your network depends on a few factors.
This is discussed in the Branch Office Deployment Guide at
http://www.microsoft.com/technet/tr...windows2000/deploy/adguide/adplan/adpch02.asp .
The information here should help you decide if you need multiple GCs.

--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
-----Original Message-----
The number of GCs that you deploy on your network depends on a few factors.
This is discussed in the Branch Office Deployment Guide at
http://www.microsoft.com/technet/treeview/default.asp?
Click to expand...
url=/technet/prodtechnol/ad/windows2000/deploy/adguide/adp
lan/adpch02.asp .
The information here should help you decide if you need multiple GCs.

--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


the global catalog
on


.
Click to expand...
GK,

Please take a look at the document that Tim posted. It
is really good.

I will tell you that a lot of people like to have two
DCs, each of which is a GC and each of which is running
DDNS. This creates an environment where there is about
as much redundancy as possible. And having Hardware RAID
is a really good idea as well.

Essentially the only thing that you would have to worry
about then would be the FSMO roles that the dying or dead
DC holds. You would simply use NTDSUtil to transfer or
seize as necessary.

However, please remember that this is a very general
guideline that may night work in your environment - so
please read that document...

HTH,

Cary
 
Thanks for the link. I guess i should explain more. If we have multiple DC
in a single domain and the global catalog server dies that is the reason why
I am asking the question. If the GC is no longer available and there is not
one on the domain won't this cause a problem. Our multiple DC's are
generally with an Exchange server.

Thanks


Tim Hines said:
The number of GCs that you deploy on your network depends on a few factors.
This is discussed in the Branch Office Deployment Guide at
Click to expand...
http://www.microsoft.com/technet/tr...windows2000/deploy/adguide/adplan/adpch02.asp .
 
If you only have one DC and it dies then Exchange will fail because it has
to talk to a GC.
Logon requests may also fail if you are in a multidomain environment. The
GC requirement does not apply for a single domain environment so if that is
the case the users will still be able to logon.

--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


GK said:
Thanks for the link. I guess i should explain more. If we have multiple DC
in a single domain and the global catalog server dies that is the reason why
I am asking the question. If the GC is no longer available and there is not
one on the domain won't this cause a problem. Our multiple DC's are
generally with an Exchange server.

Thanks
Click to expand...
http://www.microsoft.com/technet/tr...windows2000/deploy/adguide/adplan/adpch02.asp .
 
This is a single domain enviroment. But if we would setup another DC to be
a GC too would be the best bet in an exchange enviroment. That way there is
a backup of the GC on the domain. Would that be the best way to do it?

Thanks


Tim Hines said:
If you only have one DC and it dies then Exchange will fail because it has
to talk to a GC.
Logon requests may also fail if you are in a multidomain environment. The
GC requirement does not apply for a single domain environment so if that is
the case the users will still be able to logon.

--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


multiple
Click to expand...
http://www.microsoft.com/technet/tr...windows2000/deploy/adguide/adplan/adpch02.asp .
 
Yes you should have always have an additional DC/GC for redundancy if you
have the resources for it.

--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

GK said:
This is a single domain enviroment. But if we would setup another DC to be
a GC too would be the best bet in an exchange enviroment. That way there is
a backup of the GC on the domain. Would that be the best way to do it?

Thanks
Click to expand...
http://www.microsoft.com/technet/tr...windows2000/deploy/adguide/adplan/adpch02.asp .
 
Tim -

A question I've had for a while that you can probably answer...
How are login requests serviced in a single-domain environment when the GC
is down?

\\ MadDHatteR
 
Back
Top