Seize FSMO Roles in Server 2012 R2

How to seize the FSMO Operations Master roles in Server 2012 R2 uing Powershell.
If in the event that the Domain Controller hosting any of the Operations Master Roles (FSMO) becomes corrupt or unreachable you will need to seize the roles by moving them to another active Domain Controller.
First of all I would recommend that confirm which Domain Controller host which FSMo roles which you check using the following command:
netdom query fsmo
Netdom Query FSMO**Warning** Seizing FSMO roles should be used as a last resort because once the roles have been seized from a domain controller the machine should never be allowed to connect to the network again.
Seizing FSMO roles should be used the following situations:

  1. The domain controller was not demoted gracefully and the process of transferring the roles did not occur.
  2. The domain controller has been become corrupt or unusable due to either a software or hardware failure.

If you have no choice but to manually seize the FSMO roles then you can use the following Powershell command:
Move-ADDirectoryServerOperationMasterRole -Identity “Server” -OperationMasterRole 0,1,2,3,4 -Force
Where OperationMasterRole correspond to the below tabel:

PDCEmulator
0
RIDMaster
1
InfrastructureMaster
2
SchemaMaster
3
DomainNamingMaster
4