Re: Global Catalog problems?
- From: "Harvey Colwell" <harveyc@xxxxxxxxxx>
- Date: Thu, 5 Oct 2006 09:48:29 -0500
AD doesn't use GC in a single domain forest. It's only needed in a multiple
domain forest. That is, unless you have Exchange. Exchange and Outlook
requires a GC for access to the Global Address Lists (GALs). But since
there's only one server with Exchange, and its the GC, this has worked fine
for you so far.
You should definitely put DNS on your second DC. And I suggest making it AD
Integrated. Zone transfers are much more efficient that way. And while your
at it, make it a GC as well. Since there will be very little changes to the
GALs and probably no group changes, GC replication traffic will be next to
nothing.
I hope that this is a test domain and not a production domain.
BTW: adprep /forestprep only needs to be ran once on a single DC in the
forest root domain. This is so it can reach the Schema Master of the forest
(I suggest running it on the Schema Master itself). And adprep /domainprep
only needs to be ran once in each domain that will host a longhorn DC. This
is so it can reach the Domain Naming Master of that domain (again I suggest
running it on the Domain Naming Master itself). In a single domain forest,
you only need to run each one time.
I'm guessing thagt DC1 was tghe first DC of the forest/domain. Therefore, it
probably still holds all 5 Operation Master roles, so runing any thing that
changes AD on it is your best bet.
Microsoft states that it is common for Exchange's virtual servers to not
come up after a reboot. And that you should always check their associated
services. Being a Lotus Domino man myself, I find this shocking. Although in
practice, I've never encountered this happening. So what services are not
starting. If System Attendant is one of them, not good; if its IMAP4, no big
deal. Also, you can always set the recovery mode on the service to restart
for up to three consecutive failures.
Service dependencies can cause a problem for any heavily loaded server.
Services don't wait for ever for their dependencies to come up, they time
out. Therefore, its common for a service to start find manually after
logging on, while it timed out during a reboot.
I think that your network has just gotten to the size that interdependencies
between the services are starting to show up. This is normal, and you need
to simply adjust to that fact. Most of my customers have been given specific
reboot sequences to follow, so that all services load start up automatically
on all their servers. You simply need to start up DC2 first.
BTW: If you look in DC2's System and FRS event logs, you'll probably find a
few errors there as well.
"Bob" <86c6c2e6-2146512712@xxxxxxxxxxxxxx> wrote in message
news:8DFD1849-8F8C-47B1-BC65-0CB9F9AA474C@xxxxxxxxxxxxxxxx
I'm running 2K3 Server R2.
I had two DC's running just fine in that if either one was shutdown, users
could log on and do their work just fine.
The original DC1 was the first and therefore had AD,DNS and the GC. It
also
has Exchange 2003.
The second DC2 was added as an additional DC and it had only AD. I later
added DNS, but never GC or Exchange. Other than Exchange not working when
DC1 was down, things seemed to work well (even though the GC was down with
DC1). Go figure?
Anyway, I added a third DC3 as an additional DC, but this one is Longhorn
beta 2.
Longhorn defaulted to adding DNS and GC, so I let it do that. (I ran
adprep
/forestprep and domainprep on DC1 & DC2 beforehand using the Longhorn
DVD).
Before this, I backed up everything (hope I don't need it though).
I find things to run well except when I shutdown everything and only bring
up DC1.
Exchange no longer starts 3 of its 5 needed services. Once up, I can start
them manually however.
The Exchange error suggested a problem with the GC, so I looked in dnsmgmt
Forward Lookup Zone\msdcs.FQDN\gc and found DC3 (longhorn) was the only
gc.
I then used AD Sites & Services to un-check the Global Catalog entry for
DC3
and that did add DC1 back into the gc DNS. I believe DC1 is the only gc
at
this point as it is the only one with a check mark next to Global Catalog
on
the NTDS Settings.
I still have the same problem however, in that DC2 must be up before DC1.
Otherwise, Exchange fails to start 3 of its 5 needed services.
I don't think I really have an Exchange problem, but rather a GC problem.
Would removing longhorn as a DC be the solution or are their other things
I
can do to resolve this?
btw: The Exchange error is: Event 1005 on MSExchangeSA and KB Article
252137
led me to the gc.
http://support.microsoft.com/kb/252137/EN-US/
Thanks!
--
Bob
.
- Follow-Ups:
- Re: Global Catalog problems?
- From: Harvey Colwell
- Re: Global Catalog problems?
- Prev by Date: Re: Our Own DNS vs. GoDaddy's
- Next by Date: Re: Our Own DNS vs. GoDaddy's
- Previous by thread: RE: Global Catalog problems?
- Next by thread: Re: Global Catalog problems?
- Index(es):
Relevant Pages
|
