Move-ADDirectoryServerOperationMasterRole

Syntax

Move-ADDirectoryServerOperationMasterRole
    [-WhatIf]
    [-Confirm]
    [-AuthType <ADAuthType>]
    [-Credential <PSCredential>]
    [-Force]
    [-Identity] <ADDirectoryServer>
    [-OperationMasterRole] <ADOperationMasterRole[]>
    [-PassThru]
    [-Server <String>]
    [<CommonParameters>]

Description

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:

asia-w7-vm4$instance1

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 following:

asia-w7-vm4`$instance1

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

The Move-ADDirectoryServerOperationMasterRole 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-ADDirectoryServerOperationMasterRole 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).

Examples

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

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

Description

---

Move the PDC Emulator role to the Domain Controller "FABRIKAM-DC1".

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

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

Description

---

Move the PDC Emulator and Schema Master roles to the Domain Controller "FABRIKAM-DC2".

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

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

Description

---

Move the schema master FSMO owner to the AD LDS instance "instance1' on the server "Fabrikam-DC".

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

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

Description

---

Seizes the specified roles (RID master, infrastructure master, 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

Description

---

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.

Parameters

-AuthType

-Confirm

-Credential

-Force

-Identity

-OperationMasterRole

-PassThru

-Server

-WhatIf

Inputs

ADDirectoryServer

A directory server object is received by the Identity parameter.

Outputs

None or Microsoft.ActiveDirectory.Management.ADDirectoryServer

Returns the modified directory server object when the PassThru parameter is specified. By default, this cmdlet does not generate any output.

Notes

• This cmdlet does not work with an Active Directory Snapshot.

  This cmdlet does not work with a read-only domain controller.

Related Links

• Move-ADDirectoryServer