HiI have an additional domain controller in windows server 2003, i want to make it as a primary domain controller now as PDC is creating some problem ,Can any one help me , how to change operation master FSMO role (below) in this additional domain controller in command prompt1.Schema Operations Master2.Relative ID Master 3.Domain-Naming Master 4.PDC Operations Master 5.Infrastructure Master

HI, Transferring FSMO Roles C:\WINDOWS>ntdsutil ntdsutil: Type roles, and then press ENTER. ntdsutil: roles fsmo maintenance: To see a list of available commands at any of the prompts in the Ntdsutil tool, type ?, and then press ENTER. Type connections, and then press ENTER. fsmo maintenance: connections server connections: Type connect to server <servername>, where <servername> is the name of the server you want to use, and then press ENTER. server connections: connect to server server100 Binding to server100 ... Connected to server100 using credentials of locally logged on user. server connections: At the server connections: prompt, type q, and then press ENTER again. server connections: q fsmo maintenance: Type transfer <role>. where <role> is the role you want to transfer. For example, to transfer the RID Master role, you would type transfer rid master: Options are: Transfer domain naming master Transfer infrastructure master Transfer PDC Transfer RID master Transfer schema master 1. You will receive a warning window asking if you want to perform the transfer. Click on Yes. 2. After you transfer the roles, type q and press ENTER until you quit Ntdsutil.exe. 3. Restart the server and make sure you update your backup. Thanks Alagar

Here is the official document from the Microsoft which will guide you sete by ste tranfering the fsmo roles using command prompt.http://support.microsoft.com/kb/255504In addtion to the above link see all the http://www.petri.co.il/transferring_fsmo_roles.htmhttp://technetfaqs.wordpress.com

Hi,Follow these steps on the server you want to transfer a FSMO. Start - Run:ntdsutil roles connections connect to server servidor.domínio.local (Server that assumed the functions) quit seize PDC seize RID master seize infrastructure master seize schema master seize domain naming master Now just configure the new server as a Global Catalog and ready.Se til, classifique. Matheus M. Bertuco MCT, MCSA, MCTS, MCP.

Hello Matheus,please keep in mind that SEIZE is not TRANSFER and should only be used if the original DC, which has held the FSMO roles, is broken and never comes back to the domain.Then also a metadata cleanup has to be done to remove the orphaned machine complete from the AD database, additional DNS and also AD sites and services must be cleared from the old machine.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.