Global Catalog server not recognized

[Brad Kenney]

I have an AD DC that I'm trying to move the FSMO roles
off of. I have configured another DC and things seemed to
moving along fine. When I try to move the DNMaster I get
an error that the DNMaster needs to be a GC. I have
checked the GC box in ADS&S for the new server. I have
run NTDSUtil and it states that the new server is a GC
server. I have used the AD admin tool under support tools
and ran a check against the new server. Under the section
that lists "is Global catalog ready" the value is False.
How can I make the server ready when every other tool is
listing the server as a GC?

Thanks in advance

 

[Matjaz Ladava [MVP]]

Probably the utilities just check options attribute of nTDSDSA object
located at CN=NTDS
Settings,cn=ServerName,cn=SiteName,cn=Configuration,dc=domain,dc=local
This attribute sets server as GC or not. After you mark a server as GC it
takes some time for GC to build. To see if your GC is ready you need to
query
isGlobalCatalogReady in RootDSE. The following script will return this flag

Set objRootDSE= GetObject("LDAP://RootDSE")
Wscript.Echo "Is GC ready: " & objRootDSE.Get("isGlobalCatalogReady")

If your GC is not ready, then check your event log for possible errors. Run
dcdiag and netdiag to get more info.

--
Regards

Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com

 

[Brad Kenney]

I was able to find three error that keep popping up in
the event log 1559, 1578, and 1110. These errors keep
talking about partitioning. They also refer to a child
domain that no longer exists. If I can stop these errors
then I think I can get the server to promote.

 

[Guest]

I found how to remove an orphaned domain KB#230306. After
doing this the GC came online within 30 minutes.

Thanks

 

[Matjaz Ladava [MVP]]

Use http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q230306 to
remove orphaned domain from your AD. If you get error when doing metadata
cleanup, then use
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q235416 to manualy
remove domain from AD using ADSIEdit. The last Qarticle is missing one
aditional step before demoving TDO (trusted domain object), where you have
to remove server object in the Sites part of the configuration container
prior to removing TDO.

--
Regards

Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com