Announcement

Collapse
No announcement yet.

Global Catalog issue after one server crashed

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Global Catalog issue after one server crashed

    Hello everyone
    We have 2 servers in our office, which just recently one of them crashed. We can not recover it and the problem is that the main domain is installed on it. The second one is a child. When we try to create a new user it says that there is an issue with global catalog. I have done some research and I know I need to transfer the global catalog or turn the second (child) to be the main.
    Does anyone know an article how to do that?
    Thanks in advanced

  • #2
    Re: Global Catalog issue after one server crashed

    Open up Active Directory Sites and Services.
    Click on the + next to Sites.
    Click on the + next to the Site you want.
    Click on the + next to the Servers folder.
    Click on the + next to the server.
    Right Click on the NTDS Settings and select properties.
    Put a tick in the checkbox Global Catalog.

    Voila you have now made your server a global catalog.

    Comment


    • #3
      Re: Global Catalog issue after one server crashed

      First thanks for the information, but i have already done it. i saw it in the forum.
      i still dont think it solve my problem.
      for example i am trying to open "Domain security policy" and it gives me an error that the domain is not available, like it is looking for the server that crashed.
      example 2- i am trying to install SQL server and when i enter the administrator user name and password, i am getting an error that it does not find the user account. i posted the image here too.

      Thank you in advanced
      Attached Files

      Comment


      • #4
        Re: Global Catalog issue after one server crashed

        If you have onlyn one DC then you have restore it from the backup.
        OR
        Do metadata cleanup from DSRM mode and restart the server.
        OR
        From, adsiedit.msc just try to search that which FQDN is assigned for port 3268. If it is still pointing to same old server instead of new server, then you have to manually change it. Restart the server, workstation & browser services.

        ADSIEDIT IS VERY STRONG UTILITY, DON'T TRY IF YOU DO NOT HAVE A MENTOR.

        Amit
        From,
        Amit
        [/EMAIL]

        Comment

        Working...
        X