Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Seizing FSMO Roles if the PDC is not availble

Active Directory, Domain, DNS, WINS, DHCP, SBS, New Releases.

Seizing FSMO Roles if the PDC is not availble

Postby blin » Mon Feb 15, 2016 4:01 pm

Q: Our PDC is crashed and not available. How can I make the BDC to be PDC?

A: You can use Seizing FSMO Roles.

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.

Notes•Under typical conditions, all five roles must be assigned to “live” domain controllers in the forest. If a domain controller that owns a FSMO role is taken out of service before its roles are transferred, you must seize all roles to an appropriate and healthy domain controller. We recommend that you only seize all roles when the other domain controller is not returning to the domain. If it is possible, fix the broken domain controller that is assigned the FSMO roles. You should determine which roles are to be on which remaining domain controllers so that all five roles are assigned to a single domain controller. For more information about FSMO role placement, click the following article number to view the article in the Microsoft Knowledge Base:
223346 FSMO placement and optimization on Windows 2000 domain controllers

•If the domain controller that formerly held any FSMO role is not present in the domain and if it has had its roles seized by using the steps in this article, remove it from the Active Directory by following the procedure that is outlined in the following Microsoft Knowledge Base article:
216498 How to remove data in active directory after an unsuccessful domain controller demotion

•Removing domain controller metadata with the Windows 2000 version or the Windows Server 2003 build 3790 version of the ntdsutil /metadata cleanup command does not relocate FSMO roles that are assigned to live domain controllers. The Windows Server 2003 Service Pack 1 (SP1) version of the Ntdsutil utility automates this task and removes additional elements of domain controller metadata.
•Some customers prefer not to restore system state backups of FSMO role-holders in case the role has been reassigned since the backup was made.
•Do not put the Infrastructure master role on the same domain controller as the global catalog server. If the Infrastructure master runs on a global catalog server it stops updating object information because it does not contain any references to objects that it does not hold. This is because a global catalog server holds a partial replica of every object in the forest.

To test whether a domain controller is also a global catalog server: 1.Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Sites and Services.
2.Double-click Sites in the left pane, and then locate the appropriate site or click Default-first-site-name if no other sites are available.
3.Open the Servers folder, and then click the domain controller.
4.In the domain controller's folder, double-click NTDS Settings.
5.On the Action menu, click Properties.
6.On the General tab, view the Global Catalog check box to see if it is selected.
For more information about FSMO roles, click the following article numbers to view the articles in the Microsoft Knowledge Base:
197132 Windows 2000 Active Directory FSMO roles

223787 Flexible Single Master Operation transfer and seizure process
How to Configure and Troubleshoot Cisco

Tablet and Smartphone Setup Guide
Site Admin
Posts: 3649
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Return to Windows

Your Ad Here

Who is online

Users browsing this forum: No registered users and 5 guests