help with removing old domain controller

Here is my situation. Replication is failing somewhere, I'm not sure where to fix it. I can run some dcdiag reports, but I'm not sure which ones to run. I can paste results here.

DC01old is a demoted Win2003 DC that is powered off and gone.
DC02old is a win2003 DC that is still active but I want to demote it

The 3 new DC's (DC01, DC02, DC03) are replicating with DC02old.
DC02old still shows DC01old in the ntds settings. This should not be there, I would assume.

I tried using ntdsutil to do some meta cleanup but it showed nothing to cleanup.

There is the option to right-click DC01old in ntds settings and Delete, but I dont want to screw anything up. For Site3/DC03 I did manually add DC01 and tried to replicate but getting the 'Naming context is in the process of being removed' error. Any ideas?? Thanks.


Sitename            From Server
Site1
DC01            DC02old

Site2
DC02            DC02old
DC02old            DC01old, DC02, DC03

Site3
DC03            DC02old
cb_itAsked:
Who is Participating?
 
Mike KlineConnect With a Mentor Commented:
Are you running 2008 on your new DCs, if so you can safely delete that old box.  That is how metadata cleanup is done in 2008 and newer

http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

Thanks

Mike
0
 
cb_itAuthor Commented:
Yes, new servers are 2008R2.

Thanks for the link, and quick reply. The article mentions right-click on NTDS settings and hit delete. My old server DC01old isnt on the left hand side as a server, it only shows up as a replication partner when I click on DC02old.

It actually shows DC01old\OADEL:0a7a378d.... blah blah.

Is this safe to delete, I would assume considering this server doesnt exist. But would this be causing my replication to fail? What about that naming context error??
0
 
Mike KlineCommented:
Yes you can delete that connection object, do you see any other places where DC01 is listed (DNS, ADUC, sites and services, etc)

Thanks

Mike
0
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

 
cb_itAuthor Commented:
Again, thanks for the quick response, Mike.

I did delete it from ADUC and from DNS, but I did double check and I see the old server in DNS with a Name Server (NS) record. The server is gone so again I would assume this can safely go?

repadmin /showreps says replication failed because of a schema mismatch.
0
 
cb_itAuthor Commented:
Anyone have any ideas to help me out, I'm pretty stuck. Replication is still failing. Tons of KCC errors everywhere.

In AD Sites and services I dont see all of domain controllers listed under each NTDS Settings. Some DC's are here, some are there, some not at all. Any help would be greatly appreciated, thanks.
0
 
Mike KlineCommented:
Yes delete the server from name servers and any other references you find.  

Did you see this KB for schema mismatch (it is a long one)   http://support.microsoft.com/kb/2734946

Thanks

Mike
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.