Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

First Windows 2003 DC failed

Posted on 2010-09-23
7
Medium Priority
?
250 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 1000 total points
ID: 33748673
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
ID: 33748921
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
ID: 33749270
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
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 

Author Comment

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

Author Comment

by:romious4
ID: 33750123
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 39

Expert Comment

by:ChiefIT
ID: 33752227
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
ID: 33758008
mkline71 solved the problem.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
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 …
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…

579 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