General outline of our process flow when doing a replication troubleshoot, as well as the Microsoft APIs we use to get our information / take actions.
'
Replication Troubleshooting high-level outline:
- Process each DC in the scope of the troubleshooter. The following actions are taken for each DC
1) Test a Bind to the DC to ensure it is reachable from the AA server.
2) Check for replication failures in AD. We call System.DirectoryServices.ActiveDirectory.GetReplicationConnectionFailures(DC)
3) Check the Ping, open connections, Replication Partners, and IP / DNS for the DC.
Replication partners are checked using System.DirectoryServices.ActiveDirectory.GetAllReplicationNeighbors
4) Run KCC if selected.
5) Retry any failed replications from the list in step (2) if selected.
6) Send the results from all of the above back to the UI and to be stored in the results history.
