Friday afternoon disaster thoughts..

[snootalope]

Just sitting here thinking, if my main DC (FSMO) burns up, what do I do?

In our domain, I've got two DC's at our home office, one's the FSMO and the other is just a partner. Then, I've got another DC in another site just for replication.

I've been googlin for "recover FSMO", "restore FSMO", "recover domain controller", etc, and I can't find any real good info other than seizing the roles and then the original DC can never be brought back on line (same name anyways).

Is this best practice? Is there any document from M$ that lays out the best practices for recovering an FSMO machine?

What's your plan if your FSMO trips and breaks?

just thinking..

 

[pagy]

Yep that's it. You either transfer the roles if possible or seize them if the server that held them is toast.

http://support.microsoft.com/kb/255504

http://support.microsoft.com/kb/324801

Paul
MCSE 2003
MCSA 2003
MCITP Enterprise Administrator

If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams

 

[58sniper]

seizing the FSMO roles is fairly straight forward. Plenty of threads here as well about recovering them, as well as dealing with disaster recovery and failed DCs.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[gmail2]

Also, after you've seized the roles you can run NTDSUTIL to clean out the failed DC from AD. As far as I know, there's no reason why you can't use the same DC name again. Here's how you would remove a failed DC from AD:

http://technet.microsoft.com/en-us/library/cc736378.aspx

Irish Poetry - Karen O'Connor
Irish Poetry and Short Stories - Doghouse Books
Garten und Landschaftsbau