--- title: "How to Seize and Transfer FSMO Roles (GUI and PowerShell)" description: "Learn how to easily transfer Active Directory FSMO roles and seize them if they’re not behaving in this detailed guide." canonical: "https://adamtheautomator.com/transfer-fsmo-roles/" --- # How to Seize and Transfer FSMO Roles (GUI and PowerShell) > Learn how to easily transfer Active Directory FSMO roles and seize them if they’re not behaving in this detailed guide. Source: https://adamtheautomator.com/transfer-fsmo-roles/ --- ATA Learning Tap to hide [ ATA Learning ](/) * [Home](/) * [Tutorials](/tutorials/) * [Instructors](/author/) * [Advertising](/advertising/) * [Recommended Resources](/resources/) * [About Adam](/about-adam/) Search for: * [](https://twitter.com/adbertram) * [](https://github.com/Adam-the-Automator) * [](https://www.linkedin.com/company/adam-the-automator-llc) * [](/feed/) ![How to Seize and Transfer FSMO Roles (GUI and PowerShell)](https://adamtheautomator.com/wp-content/uploads/2021/02/How-to-Transfer-and-Seize-FSMO-Roles-GUI-and-PowerShell.jpg) # How to Seize and Transfer FSMO Roles (GUI and PowerShell) [![](https://secure.gravatar.com/avatar/03dc51bce307848c06c945c493e95157584f949f1879c6998bceb50315eb68b6?s=192&d=mm&r=g)Emanuel Halapciuc](https://adamtheautomator.com/author/emanuel/)26 February 20215 min. read Categories: [IT Ops](/category/it-ops/) Tags:[Active Directory](/tag/active-directory/) Table of Contents * [Prerequisites](#h-prerequisites) * [Transferring FSMO Roles with the GUI](#h-transferring-fsmo-roles-with-the-gui) * [RID Master, PDCe and Infrastructure Master](#h-rid-master-pdce-and-infrastructure-master) * [Domain Naming Master](#h-domain-naming-master) * [Schema Master](#h-schema-master) * [Transferring FSMO Roles with PowerShell](#h-transferring-fsmo-roles-with-powershell) * [Viewing Current FSMO Role Holders](#h-viewing-current-fsmo-role-holders) * [Transferring the FSMO Roles](#h-transferring-the-fsmo-roles) * [Seizing FSMO Roles with the GUI](#h-seizing-fsmo-roles-with-the-gui) * [Seizing FSMO Roles with PowerShell](#h-seizing-fsmo-roles-with-powershell) * [Conclusion](#h-conclusion) There comes a time in any Active Directory (AD) administrator’s career when he or she must transfer FSMO roles (or seize them). Domain controllers (DCs) come and go and the FSMO roles hosted on those DCs must be moved around. Not a reader? Watch this related video tutorial! **_Not seeing the video? Make sure your ad blocker is disabled._** In this tutorial, you’re going to learn how to transfer and seize all of the AD FSMO roles, step by step. You’ll see how to move FSMO roles via various GUI tools and PowerShell. Let’s get started! ## Prerequisites If you’d like to follow along, please be sure you have the following: * At least two DCs – This tutorial will be using Windows Server 2019 with a forest-functional level of Windows Server 2016 although not much has changed. * A domain-joined computer with RBAC installed or you’re on a DC’s desktop directly **_Related: [How to Install and Import the Active Directory PowerShell Module](https://adamtheautomator.com/powershell-import-active-directory/)_** * Windows PowerShell v5.1 * Log on with an AD account to a computer that’s connected to the Domain. To query for the roles, no special privileges are required. Further privileges are required for transferring or seizing the roles though. ## Transferring FSMO Roles with the GUI There are two ways to transfer FSMO roles; the GUI and PowerShell. Let’s first walk through transferring FSMO roles via a few different MMC snap-ins. ### RID Master, PDCe and Infrastructure Master Let’s first knock out the domain-specific FSMO roles. 1. Open up ADUC (_dsa.msc)_, right-click on the domain and choose **Operations Masters**. Here you’ll find all of the FSMO roles unique to the domain (RID Master, PDCe and Infrastructure Master) represented via the **RID**, **PDC** and **Infrastructure** tabs. ![Domain-specific FSMO roles](https://adamtheautomator.com/wp-content/uploads/2021/02/Change_FSMO_Domain.png) Domain-specific FSMO roles 2\. Click on each tab. You’ll notice the current [FSMO role](https://adamtheautomator.com/fsmo-roles/) holder (**Operations master**) and a **Change** button. 3\. Click on the **Change** button under each tab and select the new DC to perform transfers for the RID Master, PDCe and Infrastructure Master FSMO roles. ### Domain Naming Master Next, let’s move onto the Domain Naming Master role. You can view and change this FSMO role in the Active Directory Domains and Trusts Console. 1. Open up the Active Directory Domains and Trusts Console (_domain.msc_). 2\. Right-click on the **Active Directory Domains and Trusts** parent node and click on **Operations Master**. Here you’ll see the current DC holding this role described as **Domain naming operations master**. 3\. Click on the **Change** button and choose the DC you’d like to transfer to. ![Transferring the domain naming master FSMO role](https://adamtheautomator.com/wp-content/uploads/2021/02/Change_FSMO_DomainNamingMaster.png) Transferring the domain naming master FSMO role ### Schema Master Next up and finally is the Schema Master role. To change this role, you’ll need the Active Directory Schema MMC snap-in. > _Before beginning, first ensure you’re logged in with an account that is in the Schema Administrators AD group._ 1. Open up an elevated command prompt or PowerShell console and run `regsvr32.exe "schmmgmt.dll"`. The Active Directory Schema snap-in is not available by default. This command registers the necessary DLL for schema management. 2\. Open the _mmc.exe_ utility. 3\. Click on **File** —> **Add/Remove Snap-in**. 4\. Select **Active Directory Schema** from the **Available snap-ins** and click on **Add >** and **OK**. ![Add the Active Directory Schema in the MMC console](https://adamtheautomator.com/wp-content/uploads/2021/02/Change_FSMO_1_SchemaConsole.png) Add the Active Directory Schema in the MMC console 5\. Once in the snap-in, right-click **Active Directory Schema \[\]** and choose **Operations Master** to view the current Schema Master in the pop-up window. 6\. Click on **Change** and select the new DC to transfer the Schema Master role. ![Transferring the Schema Master role](https://adamtheautomator.com/wp-content/uploads/2021/02/Change_FSMO_2_SchemaMaster.png) Transferring the Schema Master role ## Transferring FSMO Roles with PowerShell If you’re more in the mood for the command-line, PowerShell’s got your back. ### Viewing Current FSMO Role Holders Let’s first learn how to view the current FSMO role holders before transferring with PowerShell. To do that, open up an elevated Windows PowerShell console and run `Get-ADDomain` and `Get-ADForest` to find each of the current FSMO role holders as shown below. ```powershell Get-ADDomain Get-ADForest ``` ![Running Get-ADDomain](https://adamtheautomator.com/wp-content/uploads/2021/02/QueryFSMO_PowerShell_Domain.png) Running `Get-ADDomain` ![Running Get-ADForest](https://adamtheautomator.com/wp-content/uploads/2021/02/QueryFSMO_PowerShell_Forest.png) Running `Get-ADForest` ### Transferring the FSMO Roles Once you know what DCs hold the current FSMO roles, you can transfer them too. To do so in Windows PowerShell, run the `Move-ADDirectoryServerOperationMasterRole` command using the `Identity` parameter for the DC to transfer the FSMO role to (`ChildDC1` in this case) followed by the name of the FSMO role. The below example is transferring the RID Master role. ```powershell Move-ADDirectoryServerOperationMasterRole -Identity "ChildDC1" RidMaster ``` > _For the FSMO role name, you can use `PDCEmulator`, `RIDMaster`, `InfrastructureMaster`, `SchemaMaster` and `DomainNamingMaster`._ ![Transferring FSMO roles with PowerShell](https://adamtheautomator.com/wp-content/uploads/2021/02/Transfer_FSMO_Role_1.png) Transferring FSMO roles with PowerShell > _You can also transfer more than one role at once by defining each role name separated by a comma e.g. `Move-ADDirectoryServerOperationMasterRole -Identity "ChildDC1" PDCEmulator,InfrastructureMaster`._ Maybe you’re really lazy and don’t want to type out those long names. In that case, you can also just use numbers with each FSMO role corresponding to a specific number.
Role NameNumber
PDCEmulator0
RIDMaster1
InfrastructureMaster2
SchemaMaster3
DomainNamingMaster4
Using the identifiers instead of the role names, the command to transfer the PDCE role is as short as `Move-ADDirectoryServerOperationMasterRole ChildDc2 0` You are prompted about transferring the FSMO role name, just to be sure you know what you’re doing. Since this is not a frequent task, you may want to consider using the full name(s) of the role(s) you want to transfer. Especially if you’re using the command in a script someone else will use; it’s easier to understand. ![](https://adamtheautomator.com/wp-content/uploads/2021/02/Transfer_FSMO_Role_2-1024x200.png) The short, lazy way to transfer the PDCE role ## Seizing FSMO Roles with the GUI If you need to move a FSMO role from one DC to another, transferring roles is always the best option. Transferring ensures the FSMO role is completely removed from the old DC and transferred to the new DC. But things don’t always go as planned. If a DC is no longer online or has failed in some way, you can seize FSMO roles which essentially builds a new FSMO role on a new DC without removing the old one. > _Only seize a FSMO role when you’re sure you cannot bring back the current role holder back online. Once the role is seized, make sure the old FSMO role holder is never brought back._ Seizing roles with the GUI is done by removing a DC computer account within the _Active Directory Users and Computers_ (ADUC) console. To do so: 1. First, connect ADUC to the DC you’d like to transfer the FSMO role to. To that, in ADUC, right-click on the root **Active Directory Users and Computers** node and click on **Change Domain Controller**. 2\. Search for the DC you’d like to connect to and connect to it. 3\. Click on the **Domain Controllers** OU. 4\. Right-click on the DC you’d like to seize the FSMO role from and click on **Delete**. ![Right-click the offline DC account and select Delete](https://adamtheautomator.com/wp-content/uploads/2021/02/Seize_FSMO_Gui_1-1.png) Right-click the offline DC account and select _Delete_ 5\. Next, click **Yes** through the first two prompts. ![Click OK to continue with the deletion process. ](https://adamtheautomator.com/wp-content/uploads/2021/02/Seize_FSMO_Gui_2.png) Click OK to continue with the deletion process. ![Confirm that you want to delete a DC that is a GC](https://adamtheautomator.com/wp-content/uploads/2021/02/Seize_FSMO_Gui_4.png) Confirm that you want to delete a DC that is a GC 6\. Finally, you’ll get a prompt notifying you that the DC was a FSMO role holder and the role(s) will be moved to another DC. This will be the DC your ADUC Console is connected to. Click **OK** and the computer account of the offline DC will be deleted and the roles will be seized and moved to the new DC. ![You get a final prompt that the FSMO role(s) will be transferred to another DC. Click OK to seize the role(s) and to complete the deletion wizard](https://adamtheautomator.com/wp-content/uploads/2021/02/Seize_FSMO_Gui_5.png) You get a final prompt that the FSMO role(s) will be transferred to another DC. Click _OK_ to seize the role(s) and to complete the deletion wizard ## Seizing FSMO Roles with PowerShell To seize FSMO roles with PowerShell, ensure you have Windows PowerShell open and run `Move-ADDirectoryServerOperationMasterRole` providing the name of the new DC as the `Identity` parameter value along with the `Force` parameter. The example below is seizing the RID Master role and assigning it to the `NewDC3` DC. ```powershell Move-ADDirectoryServerOperationMasterRole -Identity "NewDC3" RidMaster -Force ``` > _The same FSMO role names used for transferring also apply to the `Move-ADDirectoryServerOperationMasterRole` cmdlet also._ ## Conclusion Moving FSMO roles isn’t a daily task but when you’re promoting new DCs, demoting old DCs and decommissioning servers, you’ll need to know about FSMO roles. Follow the steps in this tutorial to help you know the this task off your list! Share this article [Share on X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fadamtheautomator.com%2Ftransfer-fsmo-roles%2F&text=How%20to%20Seize%20and%20Transfer%20FSMO%20Roles%20\(GUI%20and%20PowerShell\))[Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fadamtheautomator.com%2Ftransfer-fsmo-roles%2F)[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fadamtheautomator.com%2Ftransfer-fsmo-roles%2F) ## Related Posts ![](https://adamtheautomator.com/wp-content/uploads/2026/05/featured_image-11.webp) ### [How to Troubleshoot Active Directory Replication Errors](/troubleshoot-active-directory-replication-errors/) Troubleshoot Active Directory replication errors by isolating 1311, 1722, 2087, and USN rollback issues with repadmin, dcdiag, DNS, RPC, and KCC checks. ![](https://adamtheautomator.com/wp-content/uploads/2026/05/featured_image-7.webp) ### [Migrate Group Policy to Intune Without Breaking Endpoints](/gpo-intune-migration/) Export GPOs as XML, analyze them with Group Policy Analytics, migrate supported settings to Intune Settings Catalog, and resolve hybrid device conflicts. ![](https://adamtheautomator.com/wp-content/uploads/2026/06/ditch-gpos-intune-featured.webp) ### [Ditch the GPOs: Migrate to Microsoft Intune](/ditch-gpos-migrate-microsoft-intune-2/) Use Group Policy Analytics to migrate GPOs to Intune Settings Catalog profiles, handle unsupported Group Policy Preferences, and manage hybrid AD-to-MDM transitions. ## Categories * [IT Ops](/category/it-ops/) * [Cloud](/category/cloud/) * [DevOps](/category/devops/) * [Home Ops](/category/home-ops/) * [Information Security](/category/infosec/) * [Software Development](/category/software-development/) ## Site * [Home](/) * [Tutorials](/tutorials/) * [Instructors](/author/) * [Advertising](/advertising/) * [Recommended Resources](/resources/) * [About Adam](/about-adam/) Copyright 2026© ATA Learning | [Privacy Policy](/privacy/)