we had a RODC which was crashed. its not even booting up and its totally dead.
How can i remove it from the PDC since on the AD replication status tool shows errors.
Server 2012 R2
Technology Tips and News
we had a RODC which was crashed. its not even booting up and its totally dead.
How can i remove it from the PDC since on the AD replication status tool shows errors.
Server 2012 R2
Hi
You will do metadata cleanup fro completetly remove RODC from domain
check these links
https://support.microsoft.com/en-us/kb/216498
https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx?f=255&mspperror=-2147217396
http://blogs.msmvps.com/jeffloucks/2009/12/12/branch-office-removing-an-rodc/
Hi
You will do metadata cleanup fro completetly remove RODC from domain
check these links
https://support.microsoft.com/en-us/kb/216498
https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx?f=255&mspperror=-2147217396
http://blogs.msmvps.com/jeffloucks/2009/12/12/branch-office-removing-an-rodc/
hi thank you for the solutions.
but mine is a server 2012 R2.
Hi
Same on server 2012,metadata cleanup,etc..
Hi,
you can 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 the Windows 2008 DC or 2012 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 Crashed DC name and then script will remove automatically. Once this is done you have to remove Crashed 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
Regards,
Eth
Hi,
you can 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 the Windows 2008 DC or 2012 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 Crashed DC name and then script will remove automatically. Once this is done you have to remove Crashed 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
Regards,
Eth