FSMO Crash

[snootalope]

Just curious..

I'm sure there's lots of people out there who have a somewhat small domain, maybe three or four domain contollers all within one site.

Let's assume your FSMO domain controller melts and dies, it's just a matter of transfering the roles held by the FSMO to one of the other contollers to get the domain functioning again.

What if your FSMO controller was the domain catalog holder? If it suddenly melts, does that mean one of the other controllers need to rebuild it, or does it have to be restored?

 

[WhoKilledKenny]

If the DC with the FSMO roles fails you would not be able to transfer the roles, you would have to do a more drastic process called seizing the roll. There are steps available from Microsoft on how to do this properly. Regarding the Global Catalog, this is not a FSMO role. But do apply this rule: Create at least two GC's per site in your domain. Another thing to follow: If you have a multi-domain forest, do not run the Infrastructure Master FSMO on a DC that is a GC.

 

[Andreh]

Snootalope,

You need to 'Seize' the 'FSMO' roles if the DC with them dies. You can only 'TRANSFER' the FSMO roles when the DC holding the FSMO roles is available. You use a util called NTDSUTIL to do this:

http://www.petri.co.il/seizing_fsmo_roles.htm

Good luck.





"Assumption is the mother of all f#%kups!