Transferring Global Catolog

  • Thread starter Thread starter Abby
  • Start date Start date
A

Abby

I am having problems with adding a the Global Catalog to a
second Domain Controller.
At present when I try to add it I get the following log in
Event Viewer
"Promotion of this server to a Global Catalog has been
delayed because partition occupancy requirements have not
been met".

In a subsequent entry it mentions that by amending the key
below you can force its promotion.:

HKEY_LOCAL_MACHINE \ SYSTEM \ Current Control Set \
Services \ NTDS \ Parameters \ Global Catalog Delay
Advertisement (sec)

Unfortunately I am unable to find this key in either of
the 2 Domain Controllers. Does this indicate a more
fundamental problem, or should I simply add the value
manually?

Any help would be much appreciated.

Regards
 
I am having problems with adding a the Global Catalog to a
second Domain Controller.
At present when I try to add it I get the following log in
Event Viewer
"Promotion of this server to a Global Catalog has been
delayed because partition occupancy requirements have not
been met".

In a subsequent entry it mentions that by amending the key
below you can force its promotion.:

HKEY_LOCAL_MACHINE \ SYSTEM \ Current Control Set \
Services \ NTDS \ Parameters \ Global Catalog Delay
Advertisement (sec)

Unfortunately I am unable to find this key in either of
the 2 Domain Controllers. Does this indicate a more
fundamental problem, or should I simply add the value
manually?

Any help would be much appreciated.

Regards
Click to expand...


REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters]
"Global Catalog Delay Advertisement (sec)"=dword:00000000




Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 
You should not have to add that value, if it doesn't do it automatically it
means it isn't ready to be a GC and you are forcing it by setting that value.
That can mean that there isn't all the info that should be there and could cause
tremendous issues with various apps.

You need to find out if replication is working ok and if it isn't, fix it.

joe
 
Thank you for your response.

I have verified that replication is working using for
example AD replication Monitor.
One thing I did notice, on neither this domain controller
nor the original Global Catgory Server (and previously the
only Domain Controller) were these registry keys to be
found.
As I inherited the original server I can not determine
whether or not there was a mistake in configuration to
begin with.

Any pointers on how I might resolve this?

Much appreciated.

Regards
 
That entry shouldn't exist on DCs. If they do it means someone did it and that
means they had issues with the GC promotion and instead of fixing the issue,
they forced the status of the GC. If a DC is properly promoed to GC you will
find a registry entry in the same place specified but called

Global Catalog Promotion Complete

It should have a value of 1.
 
Thank you very much for all your assistance.

Once again you are spot on, I turned on some of the
diagnostics keys in the registry and found a KCC error.

Its referring to a domain that was removed previously
using the Metadata cleanup tool.

The ID is 1559 NTDS replication.

"A request has been made to promote this DSA to a Global
Catalog (GC). A precondition to becoming a GC is that this
server host a read-only copy of all partitions in the
enterprise. This server should hold a copy of partition
DC=testdom,DC=com but it does not. This system will not be
promoted to a GC until this condition is met.

This may be because the KCC has not run, or that it is
unable to add a replica of the partition because all of
its sources are down. Please check the event log for KCC
errors.

The KCC will retry adding the replica. "

Are you aware of any other tools that I can use to delete
this entry from the current Global catalog server or any
other way to resolve this problem?

Many Thanks
 
Sounds like you still have references in AD to that additional domain. Did you
follow the domain cleanup processes specified in the KB article to remove a domain?
 
Hi Joe,

Thank you so much for your assistance

I re-ran the metadata cleanup, and this time it has fixed
and replicated the correct settings.
I think the issues with replication where preventing me
from deleting the entries from the redundant nomain
entirely (one server would simply update the entry on the
other one) hence journal wrap issues etc.

Thank you again for all your help, you cracked it mate.

Regards
 
Back
Top