Transfer FSMO roles when the current owner is healthy and reachable. Seize a role only when the owner cannot be recovered in the required operational timeframe and the directory recovery plan permits a new owner. The two actions are not interchangeable: seizure can create serious consequences if the previous owner later returns without the required recovery or rebuild process.
This guide helps an administrator establish role ownership, select a healthy destination and verify the move. It does not replace a forest-recovery procedure or justify moving every role whenever one controller briefly goes offline. The correct decision depends on the failed role, replication health, expected recovery time and the operations the business needs.
Identify the five roles and their scope
Schema Master and Domain Naming Master are forest-wide roles. PDC Emulator, RID Master and Infrastructure Master are domain-wide roles, with a separate set in each domain. Query the relevant domain and forest explicitly in a multidomain environment rather than assuming the default management context represents everything.
Get-ADForest | Select-Object RootDomain,SchemaMaster,DomainNamingMaster
Get-ADDomain | Select-Object DNSRoot,PDCEmulator,RIDMaster,InfrastructureMaster
Get-ADDomainController -Filter * |
Select-Object HostName,Site,IsReadOnly,IsGlobalCatalog,OperationMasterRoles
Save the result, including time and the controller used for the query where relevant. An unavailable role owner does not necessarily stop every domain function immediately. Existing operations and local RID pools can continue in some circumstances, while schema changes or domain-management operations require their particular role. Assess the actual impact before escalating to seizure.
Assess the current owner and directory health
Determine whether the owner is intentionally offline, temporarily unreachable or permanently lost. Check console access, network paths, service state and the incident timeline. A workstation unable to contact one controller is not proof that the controller has failed for the entire domain.
Inspect replication and relevant directory events:
repadmin /replsummary
repadmin /showrepl
dcdiag /test:Advertising /test:Replications
Investigate lingering replication failures before selecting a new owner. A destination with stale directory data or broken inbound replication is a poor choice even if it is online. Preserve evidence of the failure and the most recent known replication state.
Confirm current AD-aware backups and the recovery decision-makers. If the directory is undergoing broader corruption or a security incident, ordinary role movement may not be the correct first action. Follow the relevant recovery or incident-response plan.
Select an appropriate destination
Choose a supported writable domain controller with healthy replication, adequate connectivity, current patching and reliable operations. Domain-scoped roles need an appropriate controller in the relevant domain. Consider site topology and the workload's availability requirements rather than choosing whichever controller appears first in a list.
Review the PDC Emulator's time-service responsibilities, particularly in the forest root domain. Identify the intended external or upstream time source and monitoring so a role move does not leave the time hierarchy incorrectly configured.
Review Infrastructure Master placement according to the forest's Global Catalog and recycling design rather than applying an old placement slogan without context. Record the intended layout and owner. A role plan should be understandable to the next administrator during an outage.
Distinguish network partition from permanent loss
A disconnected site may still contain a functioning role owner. Seizing elsewhere while the old owner continues operating can create competing assumptions across the directory. Establish whether the incident is a network partition, isolate the old owner when the recovery plan requires it and coordinate with administrators at every affected site.
Do not use seizure to compensate for an unexplained replication delay. Restoring healthy communication may permit an ordinary transfer and preserve a simpler recovery path. If permanent loss is confirmed, retain the evidence and identify the supported cleanup or rebuild work before the seizure command is approved.
Prepare permissions and a small change scope
Use the documented administrative permissions for the roles being moved. Domain and forest roles have different authority boundaries; the account needed to transfer a schema role is not automatically the same as a narrowly delegated domain operator.
Move only the roles included in the change. A planned controller retirement can justify transferring several roles, but a single failed service does not automatically justify relocating all five. Avoid scripts that silently include forest-wide roles when the request concerns one domain.
Record the source and target, reason, maintenance window, validation checks and recovery path. For a normal transfer, keep both controllers available until ownership and replication are confirmed. Do not demote the old owner immediately after the first success message.
Perform a normal transfer first
The following example transfers the PDC Emulator to a reviewed target. Resolve the target object first, which also avoids the documented issue with passing some FQDN values directly to the move cmdlet:
$target = Get-ADDomainController -Identity 'DC2025-01.example.internal'
$target | Select-Object HostName,IsReadOnly,Site
Move-ADDirectoryServerOperationMasterRole -Identity $target `
-OperationMasterRole PDCEmulator
Review the confirmation prompt and verify the target identity. The example name is illustrative. Do not add Force to a planned transfer as a generic “make it work” option. A transfer failure needs its actual cause investigated, including connectivity, permissions and directory state.
For several approved roles, specify their explicit names in the operation rather than relying on unexplained numeric identifiers. Record each result and verify the resulting owners before proceeding to the next stage of a controller replacement.
Make seizure a documented recovery decision
If the old owner cannot return within the needed timeframe, obtain the appropriate recovery authorization and isolate it so it cannot unexpectedly resume service. Confirm the chosen target has the best available healthy directory state and that the role is genuinely required.
The cmdlet's Force switch first attempts a graceful transfer and can seize the role if transfer is not possible. That fallback is consequential. A narrowly scoped illustrative seizure command is:
Move-ADDirectoryServerOperationMasterRole -Identity $target `
-OperationMasterRole PDCEmulator -Force
Use it only after the recovery decision, not as a retry habit. RID Master seizure includes allocation safeguards and can consume additional RID space; repeated unnecessary seizures are not a harmless troubleshooting technique. Other roles also have operational consequences that must be evaluated.
After seizure, do not simply reconnect the previous owner. Follow Microsoft's role-specific recovery and metadata-cleanup guidance, including rebuild or supported demotion requirements where applicable. Preserve the old system offline if it is needed for investigation.
Verify ownership and the related functions
Query domain and forest ownership again from appropriate healthy controllers. Confirm replication conveys the change and inspect relevant events. A result from one controller immediately after the operation is only part of the verification.
Get-ADDomain | Select-Object PDCEmulator,RIDMaster,InfrastructureMaster
Get-ADForest | Select-Object SchemaMaster,DomainNamingMaster
Get-ADDomainController -Identity $target.HostName |
Select-Object HostName,OperationMasterRoles
repadmin /replsummary
Validate the operations related to the moved role through ordinary approved administrative work, not a gratuitous schema or domain creation. For PDC movement, verify time configuration, domain time synchronization and relevant authentication behavior. Review monitoring so it watches the new owner.
Close retirement and rollback carefully
After a healthy transfer, roles can be transferred again through the same supported process if the previous controller remains a suitable healthy target. This is a new directory change with verification, not an invisible undo. Keep application and time-source dependencies aligned.
After seizure, returning ownership is not the whole recovery problem. The old controller's state and directory identity require the documented handling before it returns to service. For a permanently lost controller, complete approved metadata, DNS and monitoring cleanup while maintaining evidence.
Retain the decision record, commands, outputs and validation results. Microsoft's FSMO management guide and move cmdlet reference explain transfer, seizure and the Force behavior used here.
Related procedures
How to Replace an Old Domain Controller with Windows Server 2025; How to Configure the Active Directory Recycle Bin; How to Audit Active Directory Group Membership Changes.