PowerShell Logo Small


This is the built-in help made by Microsoft for the command 'Move-ADDirectoryServerOperationMasterRole', in PowerShell version 5 - as retrieved from Windows version 'Microsoft Windows Server 2012 R2 Standard' PowerShell help files on 2016-06-23.

For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.


Moves operation master roles to an Active Directory directory server.


Move-ADDirectoryServerOperationMasterRole [-Identity] <ADDirectoryServer> [-OperationMasterRole] {PDCEmulator | RIDMaster | InfrastructureMaster | SchemaMaster |
DomainNamingMaster} [-AuthType {Negotiate | Basic}] [-Credential <PSCredential>] [-Force] [-PassThru] [-Server <String>] [-Confirm] [-WhatIf] [<CommonParameters>]

Search powershellhelp.space


The Move-ADDirectoryServerOperationMasterRole cmdlet moves one or more operation master roles to a directory server. You can move operation master roles to a directory
server in a different domain if the credentials are the same in both domains.

The Identity parameter specifies the directory server that receives the roles. You can specify a directory server object by one of the following values:

-- Name of the server object (name)
-- Distinguished Name (DN) of the NTDS Settings object
-- Distinguished Name (DN) of the server object that represents the directory server
-- GUID (objectGUID) of server object under the configuration partition
-- GUID (objectGUID) of NTDS settings object under the configuration partition

For AD LDS instances the syntax for the server object name is <computer-name>$<instance-name>. The following is an example of this syntax:


When you type this value in Windows PowerShell, you must use the backtick (`) as an escape character for the dollar sign ($). Therefore, for this example, you would type the


You can also set the parameter to a directory server object variable, such as $<localDirectoryServerObject>.

The Move-ADDirectoryServerOperationMasteRole cmdlet provides two options for moving operation master roles:

1. Role transfer, which involves transferring roles to be moved by running the cmdlet using the Identity parameter to specify the current role holder and the
OperationMasterRole parameter to specify the roles for transfer. This is the recommended option.

Operation roles include PDCEmulator, RIDMaster, InfrastructureMaster, SchemaMaster, or DomainNamingMaster. To specify more than one role, use a comma-separated list.

2. Role seizure, which involves seizing roles you previously attempted to transfer by running the cmdlet a second time using the same parameters as the transfer operation,
and adding the Force parameter. The Force parameter must be used as a switch to indicate that seizure, instead of transfer, of operation master roles is being performed.
This operation still attempts graceful transfer first, then seizes if transfer is not possible.

Unlike using Ntdsutil.exe to move operation master roles, the Move-ADDirectoryServerOperationMasteRole cmdlet can be remotely executed from any domain joined computer where
the Active Directory PowerShell administration module is installed and available for use. This can make the process of moving roles simpler and easier to centrally
administer as each of the two command operations required can be run remotely and do not have to be locally executed at each of the corresponding role holders involved in
the movement of the roles, i.e. role transfer only allowed at the old role holder, role seizure only allowed at the new role holder.



Online Version: http://go.microsoft.com/fwlink/p/?linkid=291058




-------------------------- EXAMPLE 1 --------------------------

PS C:\>Move-ADDirectoryServerOperationMasterRole -Identity "FABRIKAM-DC1" -OperationMasterRole PDCEmulator

This command moves the PDC Emulator role to the Domain Controller FABRIKAM-DC1.

-------------------------- EXAMPLE 2 --------------------------

PS C:\>Move-ADDirectoryServerOperationMasterRole -Identity "FABRIKAM-DC2" -OperationMasterRole PDCEmulator,SchemaMaster

This command moves the PDC Emulator and Schema Master roles to the Domain Controller FABRIKAM-DC2.

-------------------------- EXAMPLE 3 --------------------------

PS C:\>Move-ADDirectoryServerOperationMasterRole -Identity Fabrikam-DC`$instance1 -OperationMasterRole schemaMaster -server Fabrikam-DC:50000

This command moves the schema master FSMO owner to the AD LDS instance instance1 on the server Fabrikam-DC.

-------------------------- EXAMPLE 4 --------------------------

PS C:\>Move-ADDirectoryServerOperationMasterRole -Identity FABRIKAM-DC1 -OperationMasterRole RIDMaster,InfrastructureMaster,DomainNamingMaster -Force

This command seizes the roles RID master, infrastructure master, and domain naming master.

-------------------------- EXAMPLE 5 --------------------------

PS C:\>$server = Get-ADDomainController -Identity "TK5-CORP-DC-10.fabrikam.com"
PS C:\> Move-ADDirectoryServerOperationMasterRole -Identity $server -OperationMasterRole SchemaMaster,DomainNamingMaster,PDCEmulator,RIDMaster,InfrastructureMaster

This command transfers the flexible single master operations (FSMO) role to the specified domain controller. When using the fully qualified domain name (FQDN) to identify
the domain controller, the Get-ADDomainController cmdlet must be used first as a preliminary step. There is a known issue where the Move-ADDirectoryServerOperationMasterRole
cmdlet fails when an FQDN is specified directly as the value of the Identity parameter.