Transferring FSMO roles back to original Domain Controller

I have a primary domain controller DC01 that stopped booting. While it was down I transferred all the FSMO roles and Catalog Server to DC02. I found out that something in DC01's chassis was wrong and I got it fixed and now I can boot DC01 back up. Can I transfer all the FSMO roles from DC02 back to DC01?

Seize domain naming master
Seize infrastructure master
Seize PDC
Seize RID master
Seize schema master
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DonNetwork AdministratorCommented:
You sure can, I have just recently gone thru the same scenario
Glen KnightCommented:
Did you seize the roles from the other DC?
If so then the DC you seized the roles from should not be reintroduced in to the network.

You should only seize roles as a last resort if the server is never going to come back on to the network
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

Please make sure that your Infrastructure Master role is not on a server that is a Global Catalog at the same time. If you need to you can move the GC to another server within the site.
Glen KnightCommented:
@gktech that is only an issue in a Multi Domain environment, if it's a single domain there is no issue with this and infact I would suggest that all the DC's in a single domain environment should be Global Catalogue servers.
If you seized the roles in the first place (which I imagine you did, as you said you did it whilst DC01 was down), you should NOT just bring DC01 back up now that it's fixed. Due to the seizing as opposed to a graceful transfer of roles, it will still think it's the role holder, so you'll end up with 2 DCs thinking they hold all the FSMO roles, which is not good!!!

My advice would be to completely reformat DC01, reinstall the OS etc, then join it to the domain again, and then repromote it to DC status.

Before you rejoin it, you should probably run a metadata cleanup to remove all the records the domain has for this server (

Finally, once DC01 has been repromoted, you can gracefully transfer the roles back on to it from DC02 - You should NOT use seize when you do this part - Use Transfer instead.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Glen KnightCommented:
If the roles were seized there is NO other option but to format DC01 and re-install AFTER a METADATA cleanup.
morarcAuthor Commented:
Great help thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.