Forcibly
transfer (seize) some or all of the FSMO Roles from one DC to another
when the original FSMO role holder went offline or became non
operational for a long period of time, the administrator might consider moving
the FSMO role from the original, non-operational holder, to a different DC. The
process of moving the FSMO role from a non-operational role holder to a
different DC is called Seizing, and is described in this article.
To check the
PC1 weather it is primary or additional domain controller
Runàcmd-
> net accounts
It can be
seen clearly in above diagram that PC1 in no more Primary DC it is now Backup
domain controller
Then write
the command “ netdom query fsmo” to heck where the roles resides.
So all the
roles have been transferred to PC2..
Now perform
check on PC2 which is acting as Backup/ Additional DC
Runà Cmd
C: >
Net accounts
By running
net account command on PC2 it can be seen clearly that PC2 is Primary DC
Because all
roles has been transfer to PC2 from PC1
Now run the
command “netdom query fsmo”
It is obvious from picture above all roles are resides in pc2. Thus PC2 is Primary DC
Procedure
to Seize roles:
There are
Five Roles to be seized
RID Master
PDC Emulator
Infrastructure
master
Domain Naming
Mater
Schema Mater
Runàcmd (on PC1)
(Command
Line)
>Ntdsutil
>Roles
>Connections
>Connect to
server pc1.abc.com
>Q
>Seize naming
master
Click Yes
Seize RID
Master
Click Yes
Seize PDC
>Seize PDC
>Seize PDC
Click YES
Seize infrastructure master
>Seize infrastructure master
>Seize infrastructure master
Click Yes
Seize schema
master
>Seize schema master
>Seize schema master
Click yes
All five
roles have been seized on PC1
It means all
roles have been transferred back from PC2
Verification:-
On PC1
Runàcmd
then run the following commands
> net accounts
>netdom query fsmo
PC1 again
become Primary and all roles reside back on PC1
On PC2
PC2 become backup domain controller and all roles are shifted back to PC1