Solved

DC deleted manually - oopps.  How do I clean all the metadata and what do I do to make it now officially gone

Posted on 2006-10-24
6
151 Views
Last Modified: 2010-04-13
I created a secondary dc that wouldn't boot at all.  I couldn't demote it either.  The DC was useless but still appears in my DC list on active directory.
How do I kill it now that the server has been reformatted?  I just want the DC data in AD gone for good.  I do have my primary FSMO DC still online and valid.  HELP HELP
0
Comment
Question by:chitchcock
  • 3
  • 3
6 Comments
 
LVL 25

Accepted Solution

by:
mikeleebrla earned 500 total points
ID: 17798639
the link below is straight from MS and tells you exacly how to do it:

http://support.microsoft.com/kb/216498
0
 

Author Comment

by:chitchcock
ID: 17798755
I believe the article Microsoft kb refers to a domain with a dc you still have active.  My DC has been formatted so I cannot connect to it
0
 
LVL 25

Expert Comment

by:mikeleebrla
ID: 17798918
in your original question you said you the 'bad' DC is still showing up in active directory.  How are you going into active directory on a domain that isn't 'active' as you state in your last post.

if you have ANY good DC up and running in your domain, then you need to do the steps in the link above.  those steps will purge ANY reference to the bad DC from your working active directory DCs.

0
Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

 

Author Comment

by:chitchcock
ID: 17799009
The bad DC is still showing up in the DC list in AD.  I can see it in the good primary DC#2 AD list as I stated.  I didn't state the domain wasn't active only a dc within a domain was formatted and gone.  This doesn't negate the fact that AD still lists a now defunct and gone DC in its DC list.  I still have a Good DC but the steps indicated by the kb article ask you to use ntdutil  in procedure#2 to connect to the DC which is impossible.

I will go over the steps again but it didn't let me do it the first time I tried
0
 

Author Comment

by:chitchcock
ID: 17799195
My mistake, I was attempting to connect to the failed DC not a current active one in NTDSUTIL.  IT WORKED and thanks for your help
0
 
LVL 25

Expert Comment

by:mikeleebrla
ID: 17799311
glad you got it fixed
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

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

Suggested Solutions

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…
The question appears often enough, how do I transfer my data from my old server to the new server while preserving file shares, share permissions, and NTFS permisions.  Here are my tips for handling such a transfer.
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

832 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