Re: AD 2003R2 AD Site and Services (Replication Partnership) Question

Home Forums Microsoft Networking and Management Services Active Directory AD 2003R2 AD Site and Services (Replication Partnership) Question Re: AD 2003R2 AD Site and Services (Replication Partnership) Question

#382389

Re: AD 2003R2 AD Site and Services (Replication Partnership) Question

In order to make sure you can demote the DC without leaving metadata trash behind you can do the following tests:

1) repadmin /istg and see if it automatically detects the bridgeheads for all your sites (as long as it does it means KCC will automatically recalculate the topology and the demotion will go fine)
2) look in sites & services in the NTDS Settings containers and see how your connections look like: are they automatically generated ? if yes, your demotion will go fine (manual ones can create problems and are also not recommended)
3) the day after you demote the DC you can run on any DC in the domain: repadmin /kcc *
this will trigger KCC to recalculate the topology simultaneously on all DCs (you can then check if there are still connections to the demoted DC where they used to be)
4) you can run a repadmin /replsum and then check to see if:
a) the demoted DC still appears in the list after the demotion
b) funny entries with GUIDs instead of DC names appear (these appear due to such “dead” connections remaining after a demotion

as long as replication is working fine during the demotion you shouldn’t have any probs.

gl