Dear Customer,
Thank you for your post.
According to my research, seizing an operations master role means forcing a transfer of an operations master role from a domain controller that has failed to a functioning domain controller. Seizing an operations master role is a drastic step that you should consider only if the current operations master will never be available again. If the cause of the failure is a networking problem or a software or hardware failure that you can resolve in a timely manner, wait for the operations master role holder to become available again.
You should seize a role only if you confirm the problematic Domain Controller will be permanently offline. Otherwise, if the pervious operations master comes on online after you have performed the role seizure, there will be role conflicts.
You may refer to the following article to transfer the roles:
HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
http://support.microsoft.com/?id=255690
Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain Controller
http://support.microsoft.com/?id=255504
If you come across any problem, please let me know in detail.
Hope this helps!
Sincerely,
Tom Zhang
Tom Zhang – MSFT
