[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Windows 2003 Domain Controller Lost

Posted on 2009-04-28
7
Medium Priority
?
386 Views
Last Modified: 2012-05-06
I lost a windows 2003 domain controller in a branch office to a leaky roof.  Needless to say the system shorted out and died.  There was a total of 4 DC is my network, 2 in the main hq and 1 in each branch.  The one branch is now dead.  I know I am suppose to seize the roles that may or may not be on that lost dc, but is this dangerous if they are already not on the lost DC?  What steps should I take to carefully remove the lost DC from my enviroment before I rebuild a new system?
0
Comment
Question by:ohmErnie
  • 4
  • 3
7 Comments
 
LVL 57

Accepted Solution

by:
Mike Kline earned 2000 total points
ID: 24252978
Damn that sucks, I've dealt with one flood in my career..not fun.
Yes if the server held FSMO roles you need to seize them.  I'm guessing in a branch office it didn't but if it did then seize them
http://support.microsoft.com/kb/216498
 
Then you can run a metadata cleanup for that DC (because it wasn't gracefully demoted)
http://support.microsoft.com/kb/216498
 
Thanks
Mike
0
 
LVL 1

Author Comment

by:ohmErnie
ID: 24253019
I am not sure if the server held FSMO roles.  How do I know?
0
 
LVL 57

Expert Comment

by:Mike Kline
ID: 24253041
on one of your DCs that is up run
netdom query fsmo
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
LVL 1

Author Comment

by:ohmErnie
ID: 24253072
ok great...its looks like the 5 roles are on my DC in the HQ.
0
 
LVL 57

Expert Comment

by:Mike Kline
ID: 24253092
very good news, don't have to worry about seizing them :)
http://www.petri.co.il/delete_failed_dcs_from_ad.htm
That is another entry that is the same as the Microsoft one for metadata cleanup but Daniel has the screenshots included.
Thanks
Mike
0
 
LVL 1

Author Comment

by:ohmErnie
ID: 24263439
There is now a chance this system may power up to properly demote it.  If that is the case...will bring this system up 4 days later cause an issue to active directory?  im sure the system was not properly shut down.  Also, what are the steps to demote properly?
0
 
LVL 57

Expert Comment

by:Mike Kline
ID: 24263569
Have you already done the metadata cleanup on it?
To demote gracefully you just run dcpromo again  http://support.microsoft.com/kb/238369
If you haven't demoted it or run a metadata cleanup then being down for 4 days is fine.  You shouldn't have any issues if a box is down for 4 days.
Thanks
 
Mike
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

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

A hard and fast method for reducing Active Directory Administrators members.
High user turnover can cause old/redundant user data to consume valuable space. UserResourceCleanup was developed to address this by automatically deleting user folders when the user account is deleted.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

834 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