On Tue, Apr 14, 2015 at 10:49 AM, Micheal Espinola Jr < [email protected]> wrote:
> From my side, it looked as if result #5 in that search query should have > been a link to an associated petri.com article. > At the moment, result #5 from your original search link is a link to the Petri forum post I made this morning. :-) And no Petri results in the first 3 pages of search results from https://www.google.com/search?q=Replication+errors+after+DC+demotion > Perhaps this is a better search for you: > > > https://www.google.com/search?q=windows+cleanup+a+removed+server+from+active+directory > > > This search should have quite a few Microsoft articles for cleanup > procedures. Even in a seemingly graceful demotion, things might not be so > graceful behind the scenes, and you are left with extinct/widowed server > metadata that requires cleanup. > Yes, most of those cleanup articles say to use ntdsutil, and remove the old DC. Problem is, the old DC doesn't show up in ntdsutil. When I tell it to do metadata cleanup, use the connections menu, to list all servers in site, the old DC isn't listed there to be cleaned up. And in ADSIEdit: 1. CN=Topology,CN=Domain System Volume,CN=DFSR-Globalsettings,CN=System,DC=Your Domain,DC=Domain Suffix 2. Delete the *msDFSR-Member* CN object that has the old computer name. There is no msDFSR-Member with the old DC name, only the one current DC. I'd remove the old server as a DC if I could. But it seems to have been removed, as ntdsutil doesn't show it at all.
