[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.3

Restoring FSMO roles RID and PDC Windows 2000 Domain

Asked by Chadwhite in Windows 2000 Server, Disaster Recovery

Tags: Windows Server 2000

We have a Windows 2000 domain and one of two the DC's experienced multiple hardware failures. The failed DC was the GC, PDC, and RID Master. I have referenced MS KB 255504. Currently the 2nd and only operational DC is unable to pull RID pools and is referencing the bad DC when DCDIAG is viewed.  We have reinstalled the OS and repaired all hardware on the bad DC, but I want to verify the steps for getting the two DC's and AD operational again.

1)Seize the RID & PDC emulator role from the non-existant DC to the operational DC.
2)Run the ntdsutil /metaData cleanup command to remove old DC info from AD
2)Promote the re-installed server to DC.
3)Re-destribute the roles to the newly promoted DC.

Questions I have:
1)MS says not to put GC and Infrastructure Master roles on same DC because no AD object information will be updated. Do I transfer GC to the only operational DC before I run ntdsutil /metadata cleanup?Is this ok during the brief interim of the switch over?

2)Do I have to run the ntdsutil /metadata cleanup command if I am using the same HOST name on the DC I am promoting back into the domain? (Completely new install of OS, new main board, not a restored image)

I'm looking for the easiest way to get my original configuration back online and the recommended solution for bringing it backup without leaving trash or old bad links or references in AD.

Synopsis-
(DC1) Not Running -  (Roles) RID, PDC, Global Catalog
(DC2) Still Running -  (Roles) Shema, Domain Naming, Infrastructure

(DC1x) Reinstalled OS, New Board (Roles) to be renamed to (DC1) and promoted with DCpromo

Thanks!
 
Loading Advertisement...
 
[+][-]03/27/09 08:36 AM, ID: 24002087Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: Windows 2000 Server, Disaster Recovery
Tags: Windows Server 2000
Sign Up Now!
Solution Provided By: leew
Participating Experts: 1
Solution Grade: A
 
 
Loading Advertisement...
20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625