Microsoft KB Archive/283595

From BetaArchive Wiki

PSS ID Number: 283595

Article Last Modified on 10/29/2003



The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Advanced Server SP1



This article was previously published under Q283595


SUMMARY

This article describes how to change the role owner of the operations master after you have successfully seized it. The seizure of the operations master may become necessary when domain controllers that own one or more roles fail, or become unavailable to the network. The purpose of the article is to assist administrators that need to return a domain controller that previously owned one or more roles of the operations master to the same network without causing a conflict with any new role holder of the operations master.

You must have prior knowledge of the owner of each role to complete the following steps. To obtain a list of the current roles owners, follow the steps outlined in the following Microsoft article:

234790 How to Find FSMO Role Holders (Servers)



You must locate the object where each role is stored in Active Directory. You can use the following table for the location of each object that holds the role:

Role Object
PDC emulator DC=domain,DC=com
RID master CN=Rid Manager$,CN=System,DC=domain,DC=com
Schema master CN=Schema,CN=Configuration,DC=domain,DC=com
Infrastructure CN=Infrastructure,DC=domain,DC=com
Domain naming master CN=Partitions,CN=Configuration,DC=domain,DC=com



NOTE: PDC is the abbreviation for primary domain controller and RID is the abbreviation for relative identifier.

back to the top

Changing the Role Owner of the Operations Master After a Successful Seizure

You must install the support tools from the Windows 2000 Server CD-ROM. These tools are located under the Support folder.

  1. Start the ADSIEdit tool on the domain controller that you need to place back into the network.
  2. Locate the object (from the preceding table) that holds the role that had been previously transferred. Right-click the object, and then click Properties.
  3. On the Properties dialog box, under Select which property to view, click fSMORoleOwner.

    The fSMORoleOwner can have a value that can point to the Windows NT Directory Services (NTDS) setting of a server that had been responsible for this role. Change this setting to reference the NTDS setting of the server that currently supports this role as defined by the list of roles that had been performed previously: Old value:

    CN=NTDS Settings,CN=Incorrectserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=com

    New value:

    CN=NTDS Settings,CN=Correctserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=com

  4. On the Properties dialog box, click OK.
  5. Quit ADSIEdit.


back to the top


REFERENCES

For additional information about the roles of the operations master in general, click the article number below to view the article in the Microsoft Knowledge Base:

197132 Windows 2000 Active Directory FSMO Roles


For additional information about the transfer and seizure of operations master roles, click the article number below to view the article in the Microsoft Knowledge Base:

223787 Flexible Single Master Operation Transfer and Seizure Process



back to the top

Keywords: kbenv kbhowto kbHOWTOmaster KB283595
Technology: kbwin2000AdvServ kbwin2000AdvServSearch kbWin2000AdvServSP1 kbwin2000Search kbwin2000Serv kbwin2000ServSearch kbwin2000ServSP1 kbWinAdvServSearch