Microsoft KB Archive/321469

= Scripting operations master role transfers =

Article ID: 321469

Article Last Modified on 3/2/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server

-



This article was previously published under Q321469



SUMMARY
The Microsoft Windows 2000 Resource Kit describes how to script operations master role transfers (also known as flexible single master operations transfers or FSMO transfers). This article contains additional information that was not included in the Resource Kit.



MORE INFORMATION
In Active Directory directory service, operations master role transfers are exposed as a Lightweight Directory Access Protocol (LDAP) update operation to a RootDSE operational attribute of the domain controller that is taking the role. The following table shows which RootDSE operational attribute corresponds to each role:

For example, by running the following Visual Basic Script program and by using the CScript command on a domain controller, you can transfer the domain naming master role to that domain controller: Set dse = GetObject(&quot;LDAP://localhost/RootDSE&quot;) dse.Put &quot;becomeDomainMaster&quot;, 1 dse.SetInfo This example works correctly for all operations master roles except for the PDC emulator role. To use the becomePdc attribute, you must provide the domain security identifier (SID) (in binary format) to the becomePdc attribute to trigger the operations master role transfer between two domain controllers of the same domain.

The following is an example of how to use the becomePdc attribute:

Set dse = GetObject(&quot;LDAP://localhost/RootDSE&quot;) set myDomain = GetObject(&quot;LDAP://&quot; & dse.get(&quot;defaultNamingContext&quot;)) myDomainSid = myDomain.objectSid dse.Put &quot;becomePdc&quot;,myDomainSid dse.SetInfo

Additional query words: adsi script becomePDC

Keywords: kbhowto kbinfo KB321469

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.