• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 357
  • Last Modified:

Removing orphaned DC

Hello everyone,

I have a Windows 2003 Server (Ent).  We are on the process of getting additional servers.  Prior to doing that, I have an orphaned domain controller with (FSMO, GC) roles have seized and transferred to the new server.  The old server is offline.  When I check the AD Sites & Services, I still see the old DC listed as one of the replication servers.  I also know there's a tool to use (ADSIEdit) and (NTDSUtil) to clean up the metadata, but I have never done it (besides in school).  So could anyone give me some insights?

Thanks in advance.
  • 2
1 Solution
christian_dinhAuthor Commented:
Does it matter if it's not a failed DC?  Since it has been offline and everything is transferred over.  I looked at this website and his article, but just haven't proceed.

Jeremy WeisingerSenior Network Consultant / EngineerCommented:
The steps are the same if it crashed or if you just disconnected it from the network and are never going to connect it again.
No if its not there and was not removed properly from AD then treat it as a failed DC.

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now