We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now


Sezing FSMO Roles

Medium Priority
Last Modified: 2012-05-11
May i know what is the difference between Transfering and Seizing Roles.
Why exactly we seize roles.What are the reasons for Roles Seizing.

Also can i know why GCS and Infrastructure master should not be in the same server in a multi domain Forest.
Watch Question

Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Moving the FSMO roles while both the original FSMO role holder and the future FSMO role holder are online and operational is called Transferring,
However, 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.

Because infrastructure master deals with the phantom records to update the global group membership info and Global Catalog also do almost the same but it does not use the phanto records, but both of them works for the same so if you place the infracture master role with global catalog it will automatcally stop working and only global catalog server works. Due to this only we should not place Infrastructure master role with GC.


If the Dc holding the role is down can we seize the role from other DC.


I have a DC which is offline and having 3 domainwide roles in it.
Can any one help me hoe to seize these three role.

Azeem PatelSystem Administartor

Read both articles

Seizing FSMO Role : http://www.petri.co.il/seizing_fsmo_roles.htm

Transferring FSMO Role : http://www.petri.co.il/transferring_fsmo_roles.htm
See if the DC holding  the role wents down for permanent then you should seize the roles but after seizing roles never bring that dc up in the network because this will bring a conflict of roles in domain and will break all your AD infrastructure.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.