• Contact
  • Homelab
Dimitris Tonias
  • Management
  • Monitoring
  • Cloud
  • Virtualization
  • Networking
  • Productivity
No Result
View All Result
  • Management
  • Monitoring
  • Cloud
  • Virtualization
  • Networking
  • Productivity
No Result
View All Result
Dimitris Tonias
No Result
View All Result

Transfer FSMO roles to another Domain Controller

Dimitris Tonias by Dimitris Tonias
January 21, 2018 - Updated on April 21, 2024
in Management
Reading Time: 4 mins read
A A
23
Share on FacebookShare on Twitter

In today’s article, we will see how to transfer one or more FSMO roles from one Domain Controller to another. This can be done in a variety of ways, but we will focus more on using the graphical user interface (GUI), PowerShell and NTDSUtil.

To proceed with the transfer of FSMO roles, we consider that DCs that already have a role are active in our infrastructure. Otherwise, if a DC holding a FSMO role is no longer online and operational, then we use the seize method instead of simple transfer.

Before you move a role, you need to know where the FSMO roles are in the Domain Controllers.

Transfer FSMO roles using the GUI

To transfer domain-specific FSMO roles, ie RID Master, Infrastructure Master and PDC Emulator, follow the steps below.

Open the Active Directory Users and Computers console, right-click the domain and then in Operations Masters. Here, each tab displays the three FSMO roles.

Transfer FSMO roles to another Domain Controller

To transfer one of the three FSMO roles to another DC, click Change and confirm your action.

Transfer FSMO roles to another Domain Controller

To transfer the forest-specific FSMO Domain Naming Master role, follow these steps.

Open the Active Directory Domain and Trusts console, right-click the icon and then Operations Masters. If you are not already connected to the DC you are about to transfer the role, then you can do so by clicking Change Active Directory Domain Controller in the same menu.

Transfer FSMO roles to another Domain Controller

In the same way, you will see who is the current role holder and by clicking the Change button you can transfer the role to another DC.

Transfer FSMO roles to another Domain Controller

To transfer the forest-specific FSMO Schema Master role, follow the steps below.

First, in a command-line window with administrator rights, type the following command to register the AD Schema snap-in.

regsvr32 schmmgmt.dll

regsvr32 schmmgmt.dll

Transfer FSMO roles to another Domain Controller

Then, open an MMC console (for example, pressing mmc on the Search or Run), and from the File – Add / Remove Snap-in menu, add the Active Directory Schema console.

Transfer FSMO roles to another Domain Controller

Here, right click on the icon and then in Operations Masters. You will need to be connected to the corresponding DC you are going to transfer the role you can do through the Change Active Directory Domain Controller option in the menu.

Transfer FSMO roles to another Domain Controller

As before, by clicking the Change button you can move the Schema Master role to another DC.

Transfer FSMO roles to another Domain Controller

Transfer FSMO roles using PowerShell

Transferring FSMO roles through PowerShell is a much easier and faster process without unnecessary clicks.

You can transfer one or more FSMO roles to a DC using the following command. For example, to transfer the PDC Emulator.

Move-ADDirectoryServerOperationMasterRole -Identity <TargerDC> -OperationMasterRole pdcemulator

Move-ADDirectoryServerOperationMasterRole -Identity <TargerDC> -OperationMasterRole pdcemulator

On the -OperationMasterRole switch you can declare one or more FSMO roles separated by a comma (,). So you can transfer all 5 roles with just one command.

For example.

-OperationMasterRole pdcemulator, ridmaster, infrastructuremaster, schemamaster, domainnamingmaster

-OperationMasterRole pdcemulator, ridmaster, infrastructuremaster, schemamaster, domainnamingmaster

After pressing Enter you will be prompted to confirm the transfer action.

Transfer FSMO roles to another Domain Controller

Finally, you can confirm that the roles were transferred using the corresponding PowerShell commands.

Transfer FSMO roles using the NTDSUtil tool

First, open the command prompt with administrative privileges.

Type ntdsutil and press Enter.
Type roles and press Enter.
Type connections and press Enter.
Type connect to server DC01 and press Enter, where DC01 is the server computer name that will transfer the FSMO roles to.
Type quit and press Enter.

Next, we will transfer FSMO roles one by one with the corresponding command, as the case may be. After each Enter appears a confirmation window. Just click Yes to continue.

For Schema Master, type transfer schema master and press Enter.
For RID Master, type transfer rid master and press Enter.
For Domain Naming Master, type transfer naming master and press Enter.
For PDC Emulator, type transfer pdc and press Enter.
For Infrastructure Master, type transfer infrastructure master and press Enter.

Transfer FSMO roles to another Domain Controller

After transferring the roles you want, press quit to exit the NTDSUtil environment.

Tags: Domain ControllerFSMONTDSUtilPowerShellWindows Server 2016
ShareTweetPin
Previous Post

Determine which DCs hold the FSMO roles

Next Post

Seize FSMO roles on a Domain Controller

Related Posts

Approve updates in WSUS 2016
Management

Approve updates in WSUS 2016

Configure Group Policy to deploy updates using WSUS 2016
Management

Configure Group Policy to deploy updates using WSUS 2016

Configure computer groups in WSUS 2016
Management

Configure computer groups in WSUS 2016

The initial configuration of WSUS 2016
Management

The initial configuration of WSUS 2016

Install WSUS in Windows Server 2016
Management

Install WSUS in Windows Server 2016

Error opening Report Viewer on WSUS 2016
Management

Error opening Report Viewer on WSUS 2016

Comments 23

  1. JosephM3 says:
    7 years ago

    there seems to stuff be missing from one of your examples. -OperationMasterRole pdcemulator, ridmaster, infrastructuremaster, schemamaster, domainnamingmaster is NOT a complete command. I tried adding Move but it still does not work.

    Reply
    • Dimitris Tonias says:
      7 years ago

      I just tested this PowerShell oneliner on my lab and it transfer the FSMO roles between my two DCs. Are you sure you typed the command correctly?

      Reply
  2. Blaine says:
    7 years ago

    Nicely written. Thank you!

    Reply
  3. joseph says:
    6 years ago

    hey i know its a old thread but if u can please reply, after tranferring the fsmo roles i still want to keep the old server around as a backup domain controller, can i just let it run? or i need to demote it?
    and does dns need to point to the fsmo role server?

    Reply
    • Dimitris Tonias says:
      6 years ago

      The most common practice is to use two DCs instead of one, so you can have both running. Are the DCs hold the DNS role as well? That depends on your environment actually. However, in a two servers scenario that are both DNS servers, we configure DNS settings to point to both the other DC and the DC itself.

      Reply
  4. Mike says:
    6 years ago

    Thank you so much! I did not realize how easy it was. 🙂

    Reply
  5. Ben says:
    6 years ago

    Good afternoon,

    What is the best practice for completing a transfer of the FSMO roles? Should I wait until after hours or is this change instant?

    Reply
  6. Rahul says:
    6 years ago

    they will change instantly.

    Reply
  7. Oliver says:
    6 years ago

    Thanks 🙂

    Reply
  8. Lance Woods says:
    6 years ago

    Excellent article! Thanks you!

    Reply
    • Shivendra says:
      4 years ago

      Thanks it help me alot.
      In just one go I complete the transfer succesfully

      Reply
  9. Catalin Mezdrea says:
    6 years ago

    Useful, thank you.

    Reply
  10. Gary L says:
    6 years ago

    Well written article and easy to follow steps. I used the GUI method and was able to easily move the roles on a DC that I was demoting.

    Reply
  11. Jeeva says:
    5 years ago

    the content section you mentioned as “Type connect to server DC01 and press Enter” but in the snippet you are connecting to server DC02 (connect to server DC02).

    Do i need to connect to DC02 if i need to transfer the roles from DC01 to DC02 ? if yes, then why its mentioned initially to connect to DC01. i am bit confused. can you please clarify this.

    Reply
    • caleb says:
      5 years ago

      You need connect to the new server that the roles will be MOVING TO. Hope this helps.

      Reply
  12. Martin Rosenbaum says:
    5 years ago

    Is it possible to migrate AD DC from Server 2003 to Server 2019 Essentials?

    Reply
  13. Robert Mitchell says:
    4 years ago

    Excellent article, very helpful. For anyone who says there is no PDC/BDC any longer, clearly not true, however Microsoft has separated the functions and made it considerably more complicated than it was 12 years back. Not sure if that is progress…but this article helped me get my 2019 setup as PDC, etc. and get rid of my 2012 machines finally.

    Reply
  14. Steven G says:
    4 years ago

    Finally a straight answer. Thank you

    Reply
  15. Vlastimir says:
    4 years ago

    Ela, file. Efcharisto 🙂
    Greetings from Serbia 365

    Reply
  16. deftoner says:
    3 years ago

    Thanks for the article, helped a lot!!!

    Reply
  17. Thorsten says:
    3 years ago

    Did “Move” means, the old DC is no longer the Master? can I continue use the old DC after moving?
    I only want to prepare the new DC, and keep the old one alive until the new Server goes online

    Reply
  18. Mark J says:
    2 years ago

    How can i transfer the Forrest wide FSMO roles (Schema master and Domain Naming master) from existing server 2012R2 Essentials to new server 2022 Standard (not essentials)? it seems that the Essentials server does not let go. should I seize on the new server instead? FYI, i transferred the 3 domain specific roles successfully.

    Reply
  19. kushal kumar says:
    2 years ago

    I successfully transferred FSMO role from DC (2012 R2) to ADC (2019 R2).
    but when i run DCDIAG i am getting this error “The server holding PDC role is down”

    In netdom query fsmo showing all 5 roles.

    Reply

Leave a Reply Cancel reply

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

No Result
View All Result
Zabbix server: More than 75% used in the trends cache
Monitoring

Zabbix server: More than 75% used in the trends cache

In Zabbix, "trends" are a type of data storage representing aggregated historical data. Zabbix monitors and collects a vast amount...

Read moreDetails
Check word count on Google Docs

Check word count on Google Docs

Zabbix server: More than 75% used in the configuration cache

Zabbix server: More than 75% used in the configuration cache

Approve updates in WSUS 2016

Approve updates in WSUS 2016

Configure Group Policy to deploy updates using WSUS 2016

Configure Group Policy to deploy updates using WSUS 2016

Configure computer groups in WSUS 2016

Configure computer groups in WSUS 2016

The initial configuration of WSUS 2016

The initial configuration of WSUS 2016

Get more stuff

Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.

we respect your privacy and take protecting it seriously

  • Contact
  • Homelab

© 2024 Dimitris Tonias

No Result
View All Result
  • About
  • Contact
  • Free Tools
  • Home
  • Homelab

© 2024 Dimitris Tonias

This website uses cookies. By continuing to use this website you are giving consent to cookies being used.