We help IT Professionals succeed at work.

Fix replication errors with an inexistant DC

ndidomenico
ndidomenico asked
on
I have a SBS2003 server which is having replication errors with another DC (Win2008) that was removed ungracefully from the domain (no dcpromo, was simply unplugged). What is the proper way to cleanup remains of this old DC that is not there anymore so that the SBS server does not try to replicate with it anymore.

SBS2003 is the only DC on the domain. It still holds all 5 fsmo roles, is the GC server. The tombstone lifetime of 60 days has been passed - the old DC was removed about 3 months ago.

Thanks.
Comment
Watch Question

Larry LarmeuPrincipal Consultant
Commented:
Active Directory Sites & Services,  Double click your Site name, double click Servers, double click your DC (the current one), double click NTDS settings, then you should see an entry for replication with the old, non-existing DC.  Right click and delete that entry.  That will stop it from trying to replicate.

Author

Commented:
Will that take care of deleting the old DC entry that is now under Servers ?

Note: because of these sync errors, I am getting recently errors in the event log, id 2092, saying that the FSMO role can not be validated and that operations may be impacted. I realized that today I cannot create new user accounts, probably because of this. Any chances this will fix this issue, or there are additionnal steps to do to re-validate the fsmo role on the sbs dc ?

Thanks.
 
Larry LarmeuPrincipal Consultant

Commented:
You can delete that entry, as well.

Are you sure you have all the FSMO roles?

How to seize FSMO roles:

http://support.microsoft.com/kb/255504

Author

Commented:
Also, just to confirm your previous instructions, I should end up with a NTDS Settings window which should be empty ? (there are no other DC on the domain except the sbs server).

Author

Commented:
When I do a netdom /query fsmo, it lists all 5 roles linked to my sbs2003 server.
Distinguished Expert 2018
Commented:
This is what you need:

http://technet.microsoft.com/en-us/library/cc736378%28WS.10%29.aspx

You'll basically be sending in a janitor to clean up the stale server entries.

Author

Commented:
Do I do both the Ntds deletion first proposed AND the metadata cleanup suggested in your last post ?
Distinguished Expert 2018

Commented:
If you to the metadata cleanup, it will clean up the NTDS section as part of a larger sweep, so you only need to do the one.

Author

Commented:
Metadata cleanup did the job, thanks cgaliher. ADSS would have done a part of the job too (llarmeu), but not as complete as the Metadata cleanup.