Chaging the Inter-Site Topology Generator
Hi All,
Just looking for some advice.
I'm doing some AD prep before an uplift and I've come across an Inter-Site failure in dcdiag for one of our AD sites.
The failure is due to a deleted former RODC, and you can see this referenced in the 0ADEL CN. You can also see this in the ISTG Server and Site listing, which is "Invalid".
This was obviously not demoted properly and thus the reference for this site has stayed.
However, I am confused as to why this has not automatically switched to a working DC within the Site, of which there are two.
The only way I am aware of for fixing this, is to change the attribute 'interSiteTopologyGenerator' to the NTDS CN of a working DC within the site. Is that correct?
I was also wondering if emptying the attribute value and forcing a "Check Replication Topology" would also resolve the problem, by embedding a working NTDS value itself.
An help/input appreciated.
Domain/Forest level is 2016.