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
Solved

Best method to replace 2008 R2 server DC in Active Directory

Posted on 2010-08-31
3
806 Views
Last Modified: 2012-06-27
I have (2) Windows 2000 servers and am trying to retire Server 1.  Created a Windows 2008 R2 Core host and a Windows 2008 R2 guest called Server 3.  Upgraded the AD and made Server 3 a DC with all of the FSMO roles.  Applied Windows updates to Server 3 and it will not come back up.  Had not setup backup or taken a snapshot yet. Tried a Startrep that is stuck.  So I need to remove Server 3 from the AD and rebuild or replace it.  I could build a Server 4 in a virtual environment.  I have researched 2 possible approaches.  1). Sieze the roles and move them to Server 1.  Remove Server 3.  Clean up the metadata.  Rebuild Server 3 with the same name and repromote to a DC. or 2) Create Server 4 and promote it to DC.  Sieze and move the roles to Server 4.  Then remove Server 3 and clean up metadata.  

Has anyone done this?  Which would be the better way to handle the situation?  What gotshas are likely?
0
Comment
Question by:Bonnie_T
3 Comments
 
LVL 59

Accepted Solution

by:
Darius Ghassem earned 250 total points
ID: 33569488
You need to go with the first scenario since promoting a DC when your FSMO roles are down and a DC is down means that you would not be able to move forward properly.

So, here is what you need to do.

1. Seize roles
2. Run metadata cleanup
3. Delete DNS records from failed DC.

You can then start the rebuild process with the same name.

You can try booting the server in directory service mode and run dcpromo /forceremoval which will remove the AD services off the failed dc.
0
 
LVL 57

Assisted Solution

by:Mike Kline
Mike Kline earned 250 total points
ID: 33569508
When you say it will not come back up, what do  you mean?  Just want to make sure it will really not come back up because once you seize the roles  you don't want to bring the orginal FSMO role back.
Go with your first choice
1.  Seize the roles off
2.  Run a metadata cleanup
3.  wipe/rebuild server 3 (doesn't have to be the same name but it can be)
4.  Promote again
 
Thanks
Mike
0
 

Author Closing Comment

by:Bonnie_T
ID: 33569537
Thank you both so much.  I split the points because I will use both of your answers.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
This article describes my battle tested process for setting up delegation. I use this process anywhere that I need to setup delegation. In the article I will show how it applies to Active Directory
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

808 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