Move-ADDirectoryServerOperationMasterRole

by Posted on

Move-ADDirectoryServerOperationMasterRole is accessible with the help of addsadministration module. To install addsadministration on your system please refer to this link.

Synopsis

Moves operation master roles to an Active Directory directory server.

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 $. 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 $.

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).

Parameters 

 -AuthType 
         Specifies the authentication method to use. Possible values for this parameter include:

    Required?                    false
    Position?                    named
    Default value                Microsoft.ActiveDirectory.Management.AuthType.Negotiate
    Accept pipeline input?       false
    Accept wildcard characters?  false

-Credential <PSCredential>
    Specifies the user account credentials to use to perform this task. The default credentials are the credentials of the currently logged on user unless the cmdlet is run from an Active Directory PowerShell provider drive. If the cmdlet is run from such a provider drive, the account associated with the drive is the default.

    Required?                    false
    Position?                    named
    Default value                
    Accept pipeline input?       false
    Accept wildcard characters?  false

-Force <SwitchParameter>
    This parameter is used for seize operations on domain controllers with the flexible single master operations (FSMO) role.

    Required?                    false
    Position?                    named
    Default value                
    Accept pipeline input?       false
    Accept wildcard characters?  false

-Identity <ADDirectoryServer>
    Specifies an Active Directory server object by providing one of the following values. The identifier in parentheses is the LDAP display name for the attribute.

    Required?                    true
    Position?                    1
    Default value                
    Accept pipeline input?       True (ByValue)
    Accept wildcard characters?  false

-OperationMasterRole <ADOperationMasterRole[]>
    Specifies one or more operation master roles to move to the specified directory server in Active Directory Domain Services. Possible values for this parameter include:

    Required?                    true
    Position?                    2
    Default value                
    Accept pipeline input?       false
    Accept wildcard characters?  false

-PassThru <SwitchParameter>
    Returns the new or modified object. By default (i.e. if -PassThru is not specified), this cmdlet does not generate any output.

    Required?                    false
    Position?                    named
    Default value                
    Accept pipeline input?       false
    Accept wildcard characters?  false

-Server <String>
    Specifies the Active Directory Domain Services instance to connect to, by providing one of the following values for a corresponding domain name or directory server. The service may be any of the following:  Active Directory Lightweight Domain Services, Active Directory Domain Services or Active Directory Snapshot instance.

    Required?                    false
    Position?                    named
    Default value                See notes
    Accept pipeline input?       false
    Accept wildcard characters?  false

-Confirm <SwitchParameter>
    Prompts you for confirmation before running the cmdlet.

    Required?                    false
    Position?                    named
    Default value                false
    Accept pipeline input?       false
    Accept wildcard characters?  false

-WhatIf <SwitchParameter>
    Shows what would happen if the cmdlet runs. The cmdlet is not run.

    Required?                    false
    Position?                    named
    Default value                false
    Accept pipeline input?       false
    Accept wildcard characters?  false

Syntax

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

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

————————– EXAMPLE 1 ————————–
C:\PS>Move-ADDirectoryServerOperationMasterRole “TOSSolution-DC1” PDCEmulator
Move the PDC Emulator role to the Domain Controller “TOSSolution-DC1”.

————————– EXAMPLE 2 ————————–
C:\PS>Move-ADDirectoryServerOperationMasterRole -Identity “TOSSolution-DC2” -OperationMasterRole PDCEmulator,SchemaMaster
Move the PDC Emulator and Schema Master roles to the Domain Controller “TOSSolution-DC2”.

————————– EXAMPLE 3 ————————–
C:\PS>Move-ADDirectoryServerOperationMasterRole TOSSolution-DC`$instance1 -OperationMasterRole schemaMaster -server TOSSolution-DC:50000
Move the schema master FSMO owner to the AD LDS instance “instance1′ on the server “TOSSolution-DC”.

————————– EXAMPLE 4 ————————–
C:\PS>Move-ADDirectoryServerOperationMasterRole -Identity TOSSolution-DC1 -OperationMasterRole RIDMaster,InfrastructureMaster,DomainNamingMaster -Force
Seizes the specified roles (RID master, infrastructure master, domain naming master).

————————– EXAMPLE 5 ————————–
PS C:>$server = Get-ADDomainController -Identity “TK5-Delhi-DC-10.TOSSolution.com”
PS C:>Move-ADDirectoryServerOperationMasterRole -Identity $server -OperationMasterRole SchemaMaster,DomainNamingMaster,PDCEmulator,RIDMaster,InfrastructureMaster
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.

You can check the Version, CommandType and Source of this cmdlet by giving below command.

Get-Command Move-ADDirectoryServerOperationMasterRole
Get-Command Move-ADDirectoryServerOperationMasterRole powershell script command cmdlet

You can also read about
. Move-ADDirectoryServer

To know more PowerShell cmdlets(Commands) on addsadministration (Active Directory) click here

Click on this Link for an Single place where you get all the PowerShell cmdlet sorted based on the modules.

You can also refer other blogs on PowerShell at link

You can also refer other blogs on Microsoft at link

And also if you required any technology you want to learn, let us know below we will publish them in our site http://tossolution.com/

Like our page in Facebook and follow us for New technical information.

References are taken from Microsoft

Published by Karthik S

Lead DevOps | Windows | AWS | Azure | Docker | Kubernetes | Jenkins

Leave a Reply

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