Transfer FSMO roles from Windows Server 2003 to Windows Server 2012

Windows Server 2012 logo

In the previous articleOpens in a new tab. we explained how to add the first Windows Server 2012 R2 domain controller in existing Windows Server 2003 environment. That procedure didn’t consider the transfer of the FSMO roles: Schema master, Domain naming master, RID master, PDC emulator and Infrastructure master. For the meaning of each one of these roles, check this knowledge base articleOpens in a new tab.. I believe that most system administrators are already familiar with these things.

Before demoting the old Windows Server 2003 domain controller, it is very important to transfer these FSMO roles to the new domain controller running on Windows Server 2012. You must not demote a Windows Server 2003 DC who holds a FSMO roles until you transfer all of them to the new DC.

Transfer FSMO roles using GUI

Here is a very good guide regarding the transferring FSMO rolesOpens in a new tab., provided by Canadian IT Pro community. It is well written and strict to the point. It worked well in my case without any problems. I just skipped the last part “Removing the Windows Server 2003 from the Global Catalog Server” because I still want both of them to run in parallel and make sure that everything run smoothly.

Important notice: make sure you perform all the procedures by using an account that is member of Enterprise Admins group. Also, you should run Command Prompt as Administrator (Right-click Command prompt, and then click Run as administrator). This is very important, especially when installing the Active Directory Schema Snap-InOpens in a new tab. – this is the part when you transfer the Schema Master role from the old 2003 DC to the new 2012 DC.

General recommendation before you start with transferring FSMO roles is to examine who currently holds the FSMO roles. You can achieve that by opening Command Prompt and executing this command:

netdom query fsmo

Also, executing the dcdiag command against both domain controllers is a good practice to prove that your DC’s are healthy and functioning.

After you are done with the entire procedure, start again the CMD and execute the netdom query fsmo command to make sure that new Windows Server 2012 DC is current holder of all 5 FSMO roles.

Transfer FSMO roles using the Command Line or Power Shell

Lot of SysAdmins prefer command line for doing administrative tasks, because it provides simplicity and reduces the required administrative time. You can transfer FSMO roles using the command line the same way as you do that using the GUI. The command line tool used for this purpose is called ntdsutil.

I would suggest one articleOpens in a new tab. where the process of transffering FSMO roles using the command line is well explained. Take into consideration that transferring the FSMO roles doesn’t work always, especially if your domain controller which holds any of that roles is corrupted. In that case, the last possible way to make another DC a FSMO holder is seizing FSMO rolesOpens in a new tab. (use this option cautiously).

If you prefer PowerShell, than consider this articleOpens in a new tab. or even more simpler guideOpens in a new tab..

Milan Mihajlov

Milan is a seasoned professional with a diverse background in Software Testing, IT Support and System Engineering. With a keen interest in AI, Smart Home technology, and useful software utilities, Milan brings a unique perspective to the ever-evolving world of technology. Through his expertise and passion, he aims to share insights and help readers navigate the complexities of modern tech seamlessly. Follow me for the latest trends, tips, and innovations in the digital landscape.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Recent Posts

Pin It on Pinterest