No announcement yet.

Windows 2000 Server with all 5 fsmo roles dead

  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows 2000 Server with all 5 fsmo roles dead

    There are 2 dcs on the network running windows 2000 server with sp4.
    I found out this morning that the one holding all the 5 fsmo roles is not working due to motherboard failure.
    For some reason, the backup of that dc is not availabe. In this scenario, how do I resove this issue; however the other dc is functioning on the network and when I used the dcdiag command and the netdom command the output confirmed that the dead dc held all the five fsmo roles.
    I have installed windows 2000 server with different hardware on another computer using the same computer name as the dead one.
    1. How do I seize all the 5 fsmo roles since the dc is dead
    2. How do I join the domain? Do I have to run dcpromo again.
    3. What about the DNS-for fault tolerance, the dead dc was running actve directory integrated.

  • #2
    Re: Windows 2000 Server with all 5 fsmo roles dead

    To seize the FSMO roles by using the Ntdsutil utility, follow these steps:

    1. Log on to a Windows 2000 Server-based or Windows Server 2003-based member computer or domain controller that is located in the forest where FSMO roles are being seized. We recommend that you log on to the domain controller that you are assigning FSMO roles to. The logged-on user should be a member of the Enterprise Administrators group to transfer schema or domain naming master roles, or a member of the Domain Administrators group of the domain where the PDC emulator, RID master and the Infrastructure master roles are being transferred.
    2. Click Start, click Run, type ntdsutil in the Open box, and then click OK.
    3. Type roles, and then press ENTER.
    4. Type connections, and then press ENTER.
    5. Type connect to server servername, and then press ENTER, where servername is the name of the domain controller that you want to assign the FSMO role to.
    6. At the server connections prompt, type q, and then press ENTER.
    7. Type seize role, where role is the role that you want to seize. For a list of roles that you can seize, type ? at the fsmo maintenance prompt, and then press ENTER, or see the list of roles at the start of this article. For example, to seize the RID master role, type seize rid master. The one exception is for the PDC emulator role, whose syntax is seize pdc, not seize pdc emulator.
    8. At the fsmo maintenance prompt, type q, and then press ENTER to gain access to the ntdsutil prompt. Type q, and then press ENTER to quit the Ntdsutil utility.

    Is the second DC not also doing DNS AD Integrated? If it is then just point all DNS on all workstations to the second DC?
    Please remember to leave positive reputation points (The Ying Yang Icon) if someone helps you.


    • #3
      Re: Windows 2000 Server with all 5 fsmo roles dead

      You should metadata cleanup before you DCPROMO a new DC with the same name as the failed DC. Better yet rename is something else.


      • #4
        Re: Windows 2000 Server with all 5 fsmo roles dead

        This is to thank members for their response.
        I succesfully seized all the five fsmo roles and removed the dead dc from the ad.
        The only problem is I was unable to delete the dead dc name from the dc container. Since I decided to name the new dc to a different name, I removed the name from the DNS entries.