I was checking on the replication status for a domain controller when I noticed that long ago decommissioned domain controllers show up in the list. What is the best way to remove these references?

repadmin /showvector /latency DC=domain,DC=com

same case is open below please do not create duplicate request. Kindly close this one as this already running below.

https://social.technet.microsoft.com/Forums/en-US/a3eb7cd0-877c-4e65-bffc-75d0fbfbeb56/old-domain-controllers-in-replication-list?forum=winserverDS

I was checking on the replication status for a domain controller when I noticed that long ago decommissioned domain controllers show up in the list. What is the best way to remove these references?

repadmin /showvector /latency DC=domain,DC=com

• Merged by Ethan HuaMicrosoft contingent staff, Moderator 1 hour 29 minutes ago duplicate

Did you have to demote them via a metadata cleanup?

In AD sites and services, Is there a server object for this server? If so, go to where the server object is, does it still have an NTDS object associated with it?

Is the name (invalid by now) in the name server list on the DNS server?

The link below guides you through a metadata cleanup.

https://technet.microsoft.com/en-us/library/cc816907%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

hi,

Can you provide the output of following command. then follow the steps given below.

Repadmin /replsum /errorsonly

Yes you can remove the Decommission DC from AD. First run the following command see is there any FSMO roles resides on that DC. If yes kindly Transfer or Seized the role.

Net dom Query Fsmo

Once you have done the above steps then download the script from below link for metadata clean-up.

https://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3

Copy the code in notepad and save as metadatacleanup.vbs and then open the command prompt run as administrator on one of DC and go to the path where you have copied the script and then run the command cscript metadatacleanup.vbs

It will ask for Domain controller name which you want to remove just type Decommission DC name and then script will remove automatically. Once this is done you have to remove Decommission DC from DNS manually as given below.

Manual Steps

Dnsmgmt.msc [Dns Management]
 A.Expand the forward lookup zones\_msdcs folder
 i. Make sure only the actual domain controllers are listed, delete wrong Alias recordsremove wrong name server records
 ii. Select the container [forward lookup zones\_msdcs.domain.com\dc\_sites_\sitename\_tcp] > delete incorrect _ldap and _kerberos records are listed.
 iii. Select the container [forward lookup zones\_msdcs.domain.com\dc\_tcp] and delete incorrect _ldap and _kerberos records
 iv. Expand the [forward lookup zones\_msdcs.domain.com\domains\guid\_tcp] and delete incorrect _ldap entries
 v. Select [forward lookup zones\_msdcs.domain.com\gc] delete incorrect HostA records
 vi. Expand the [forward lookup zones\_msdcs.domain.com\gc\_sites\sitename\_tcp] delete incorrect _ldap entries
 vii.Select the [forward lookup zones\_msdcs.domain.com\gc\_tcp] delete incorrect _ldap entries
 viii. Select the [forward lookup zones\_msdcs.domain.com\pdc\_tcp] delete incorrect _ldap entries
 
 B.Expand the forward lookup zones\domain.com folder
 i.Delete Host(A) records of dcs which are non-existant.
 ii.Correct the NameServer (NS) records
 iii. Follow steps similar to A ii >> A viii
 
Dssite.msc [Sites and Services]
 A.Expand the [Sites\Sitename\Servers] delete incorrect servers
 B.Delete incorrect subnet configurations [Sites\Subnets]
 C.Delete incorrect site links [Sites\IP]
 
  Make sure the domain controllers are pointing to the correct dns servers in tcp\ip settings.
  Force replication repadmin /syncall

hi,

Can you provide the output of following command. then follow the steps given below.

Repadmin /replsum /errorsonly

Yes you can remove the Decommission DC from AD. First run the following command see is there any FSMO roles resides on that DC. If yes kindly Transfer or Seized the role.

Net dom Query Fsmo

Once you have done the above steps then download the script from below link for metadata clean-up.

https://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3

Copy the code in notepad and save as metadatacleanup.vbs and then open the command prompt run as administrator on one of DC and go to the path where you have copied the script and then run the command cscript metadatacleanup.vbs

It will ask for Domain controller name which you want to remove just type Decommission DC name and then script will remove automatically. Once this is done you have to remove Decommission DC from DNS manually as given below.

Manual Steps

Dnsmgmt.msc [Dns Management]
 A.Expand the forward lookup zones\_msdcs folder
 i. Make sure only the actual domain controllers are listed, delete wrong Alias recordsremove wrong name server records
 ii. Select the container [forward lookup zones\_msdcs.domain.com\dc\_sites_\sitename\_tcp] > delete incorrect _ldap and _kerberos records are listed.
 iii. Select the container [forward lookup zones\_msdcs.domain.com\dc\_tcp] and delete incorrect _ldap and _kerberos records
 iv. Expand the [forward lookup zones\_msdcs.domain.com\domains\guid\_tcp] and delete incorrect _ldap entries
 v. Select [forward lookup zones\_msdcs.domain.com\gc] delete incorrect HostA records
 vi. Expand the [forward lookup zones\_msdcs.domain.com\gc\_sites\sitename\_tcp] delete incorrect _ldap entries
 vii.Select the [forward lookup zones\_msdcs.domain.com\gc\_tcp] delete incorrect _ldap entries
 viii. Select the [forward lookup zones\_msdcs.domain.com\pdc\_tcp] delete incorrect _ldap entries
 
 B.Expand the forward lookup zones\domain.com folder
 i.Delete Host(A) records of dcs which are non-existant.
 ii.Correct the NameServer (NS) records
 iii. Follow steps similar to A ii >> A viii
 
Dssite.msc [Sites and Services]
 A.Expand the [Sites\Sitename\Servers] delete incorrect servers
 B.Delete incorrect subnet configurations [Sites\Subnets]
 C.Delete incorrect site links [Sites\IP]
 
  Make sure the domain controllers are pointing to the correct dns servers in tcp\ip settings.
  Force replication repadmin /syncall

• Proposed as answer by Ethan HuaMicrosoft contingent staff, Moderator 1 hour 18 minutes ago

same case is open below please do not create duplicate request. Kindly close this one as this already running below.

https://social.technet.microsoft.com/Forums/en-US/a3eb7cd0-877c-4e65-bffc-75d0fbfbeb56/old-domain-controllers-in-replication-list?forum=winserverDS

• Proposed as answer by Mr XMVP Saturday, August 22, 2015 9:01 PM

Simply proceed as the following:

• Run dsa.msc and remove the computer objects of the old DCs
• Run dssite.msc and remove the NTDS settings of the old DCs and there references there

You can simply clean this by doing a metadata clean up.
 
As already suggested by others, this can be done by using GUI tools, command line or a script. For more information about how to clean up server metadate, please take a look at this TechNet article:
 
https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx
 
Hope this helps.
 

Regards,

Eth