none
WARNING: Not advertising as a global catalog.

    Question

  • Hi Team, 

    We have 1 PDC server and 3 member DC (All are Windows server 2008)  , all DC replication are happening between each other.

    When i check repadmin /showrepl on one DC, it showing following error, but user's authentication, DC replication is happening  from this DC. 

    DSA Options: IS_GC
        WARNING:  Not advertising as a global catalog.



    Thanks, Manish


    • Edited by Manish KS Wednesday, January 18, 2017 10:09 AM
    Wednesday, January 18, 2017 10:07 AM

Answers

  • Dear All,

    Thanks for reply.

    We had some orphan domains, i deleted these domain's partitions through NTDSUTIL.

    Now this server is showing Global Catalog server.


    Thanks, Manish

    • Marked as answer by Manish KS Wednesday, July 19, 2017 8:04 AM
    Wednesday, July 19, 2017 8:03 AM

All replies

  • You can safely ignore this message if all you have is a single Active Directory domain, which is what you have based on your problem description.  Only in a multi-domain AD domain model would you need to worry about which DC is, and which is not, advertising as a global catalog.  In a single AD domain such as yours, you can make that one DC which is throwing the error into a global catalog, you will not incur any extra overhead, and it will resolve the problem.  How to promote a domain controller to a global catalog server
     

    Best Regards, Todd Heron | Active Directory Consultant

    • Proposed as answer by AshPoxon Wednesday, January 18, 2017 12:17 PM
    Wednesday, January 18, 2017 10:19 AM
  • Hi Todd,

    Thanks for reply.

    Already marked on Global catalog. Earlier this server  was a Global catalog, From 2-3 months we are facing this error.


    Thanks, Manish

    Thursday, January 19, 2017 7:24 AM
  • Hi Manish,
    You could firstly check if that DC is GC or not, the suggested method is use the /GC parameter in nltest.exe and observe that GC is listed in the Flags: nltest /dsgetdc:contoso /force /gc.
    If not, as Todd suggested, you could promote the DC as GC.
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, January 19, 2017 7:31 AM
    Moderator
  • Hi Wendy,

    Thanks for reply.

    Kindly find below details for reference.

    C:\Users\Administrator."doamin name">nltest /dsgetdc:"doamin name" /server:ADC-HO
               DC: \\ADC-HO
          Address: \\192.168.1.20
         Dom Guid: 9520cab8-9937-4068-9e64-2096284dba86
         Dom Name: "doamin name"
      Forest Name: "doamin name"
     Dc Site Name: HO
    Our Site Name: HO
            Flags: DS LDAP KDC TIMESERV WRITABLE DNS_FOREST CLOSE_SITE FULL_SECRET
    The command completed successfully

    C:\Users\Administrator."doamin name">


    Thanks, Manish

    Thursday, January 19, 2017 7:51 AM
  • Wether the server is GC or not is governed by 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")

    As you said it was earlier GC now it is not may be this value is still not properly updated and still showing old value, check that one.

    Thursday, January 19, 2017 11:17 AM
  • Dear All,

    Thanks for reply.

    We had some orphan domains, i deleted these domain's partitions through NTDSUTIL.

    Now this server is showing Global Catalog server.


    Thanks, Manish

    • Marked as answer by Manish KS Wednesday, July 19, 2017 8:04 AM
    Wednesday, July 19, 2017 8:03 AM