WIndows 2008 FSMO ROles

Posted on 2014-08-30
Medium Priority
Last Modified: 2014-09-17

My Present Environment:
Server1 : Windows 2008R2, DC, DNS, DHCP
Server2 : Windows 2012R2, DC, DNS, holds all 5 FSMO roles

Server2 has definitely failed. All 5 FSMO Roles where on server2
How do I restore all FSMO roles to server1 since I have no more access to server2

Thank you
Question by:gadsad
LVL 60

Expert Comment

by:Cliff Galiher
ID: 40294541
You can "seize" the roles onto a different server. The difference between seizing and transferring is that the server that held the roles need not be present to seize roles. As an aside, you will also want to remove the computer account for the failed DC, clean up metadata using ntdsutil, and clean up DNS.

TechNet has guidance on all of these, and as an authoritative source, I recommend searching there. I have observed a recent rise in fake links and links to blog post with blatantly bad information, often intentional to compromise the machine. So I strongly encourage going to TechNet and searching directly instead of relying on any links here.
LVL 28

Accepted Solution

MAS earned 2000 total points
ID: 40294542
You will have to seize the roles on server1 and it will take sometime to publish itslef as the new FSMO holder.

Delete the failed DC components from domain controller (metadata cleanup)
Finally install an additional DC after this server become error free to make you safe and to recover from such situations in future

Author Closing Comment

ID: 40327905

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
Suggested Courses

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question