?
Solved

Using Active directory Recovery Mode to Fix Problems

Posted on 2006-10-24
3
Medium Priority
?
760 Views
Last Modified: 2008-02-26
My Windwos 2000 Server will not boot normally because the AD services will not start.  Guidance that I have found suggests booting into Active Directory Recovery Mode.  I have done that, but now what?  The server is a DC has has the latest service pack.  I have used a different DC on the same domain to seize FSMO roles, so my users cand still connect, but I still need to get this server booting normally with active directory services running?  Can anyone help?
0
Comment
Question by:SlyPrince
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 39

Expert Comment

by:redseatechnologies
ID: 17794099
Hi SlyPrince,

If you have seized the roles on another server, you can't bring the old server back into the domain - you will need to reinstall windows again.

How can I forcibly transfer (seize) some or all of the FSMO Roles from one DC to another?
http://www.petri.co.il/seizing_fsmo_roles.htm

Windows 2000 Active Directory FSMO roles
http://support.microsoft.com/kb/197132

Flexible Single Master Operation Transfer and Seizure Process
http://support.microsoft.com/kb/223787

Hope that helps,

-red
0
 

Author Comment

by:SlyPrince
ID: 17794204
 Thank you Red.  That is an answer I kind of expected, but hoped not to hear.  I can rebuild the server, but the Active Directory Database will think that the "old" server still exists.  Can I clean up the database and reinstall the server with the same name as before?  I want to use the same name because there are many users and shares at steak on the faulty server.  As I rebuild it, I need to avoid any conflect with old information is the AD database.
0
 
LVL 39

Accepted Solution

by:
redseatechnologies earned 2000 total points
ID: 17794296
Sorry to be the bearer of bad news :)

You can manually rip out a dead server - Daniel Petri has been good enough to detail this here -> http://www.petri.co.il/delete_failed_dcs_from_ad.htm

I would recommend you do not use the same name, but instead use a DNS alias (then your shares will still work).

That isn't to say that the old name won't work (or that using a new name and a DNS alias is perfect) but it can be a right pain to troubleshoot.

Good luck

-red
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

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

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
In today's business world, data is more important than ever for informing marketing campaigns. Accessing and using data, however, may not come naturally to some creative marketing professionals. Here are four tips for adapting to wield data for insi…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

765 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