Solved

First Windows 2003 DC failed

Posted on 2010-09-23
7
238 Views
Last Modified: 2012-05-10
The first DC, Windows 2003, used to build the forest and domain failed and is unrecoverable.  We tried to slave the drive but our efforts was unsuccessful. All of our other DCs are running Windows 2008 R2 and our forest and domain functional levels are Windows 2003.  All AD Roles are on the Windows 2008 R2 DC.  Can I stand the replacement DC as a Windows 2008 r2 DC?  Do you foresee any problems?
0
Comment
Question by:romious4
  • 4
  • 2
7 Comments
 
LVL 57

Accepted Solution

by:
Mike Kline earned 250 total points
Comment Utility
You said the first, did you have other DCs in that domain (hopefully yes).  Not sure if those other DCs you mentioned are in the same domain or a different domain.

If you had FSMO roles on that box you will have to seize them http://www.petri.co.il/seizing_fsmo_roles.htm

Run a metadata cleanup on the box  http://www.petri.co.il/delete_failed_dcs_from_ad.htm

Thanks

Mike
0
 

Author Comment

by:romious4
Comment Utility
This is not the only dc in the domain. It is the last 2003 dc in the forest. We did not do a migration to 2008.  We initially added the 2008 r2 dcs to the domain. We plan to stand its replacement up as a 2008 r2 box with same name and IP.
0
 
LVL 57

Expert Comment

by:Mike Kline
Comment Utility
That will work, just make sure to clean out that old DC first if you want to give it the same name and IP.
0
Are your corporate email signatures appalling?

Is it scary how unprofessional your email signatures look? Do users create their own terrible designs and give themselves stupid job titles? You can make this a lot easier for yourself by choosing an email signature management solution from Exclaimer today.

 

Author Comment

by:romious4
Comment Utility
The other two domain conntrollers are erroring out stating the 'DNS server is not configured'.
0
 

Author Comment

by:romious4
Comment Utility
The remaining domain controllers upon clicking the DNS icon displays the following message.

The server xxx-xxxx could not be contacted.
 The error was:
The server is unavailable.

Guys, the DC that went down was the PDC in dns.

0
 
LVL 38

Expert Comment

by:ChiefIT
Comment Utility
That's DNS metadata that you need to rid yourself of. The petri article that mkline provided tells you how to remove FRS, AD and DNS metadata from the remaining DCs.
0
 

Author Closing Comment

by:romious4
Comment Utility
mkline71 solved the problem.
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

Resolve DNS query failed errors for Exchange
In this article, we will see the basic design consideration while designing a Multi-tenant web application in a simple manner. Though, many frameworks are available in the market to develop a multi - tenant application, but do they provide data, cod…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
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…

743 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

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now