I have seen a few times where the Remote Registry service causes issues with the Mult-Master Synch. At times it is that the service is stopped and set to Triggered yet it does not start. Or at times it is even Stopped and set to disabled. Since the DRA service account will have permissions on each of the servers, if it encounters an error connecting remotely to the registry, it should check the status of the Remote Registry service and programmatically resolve the issue. I have also seen cases where there is an error stating the RPC Server is too busy to complete the operation during an MMS Synch. This too is caused by the Remote Registry service. Even though the service is already started, restarting this service on the secondary server resolves the issue and the MMS Synch is then able to complete successfully. It would be very beneficial to have DRA perform these types of resolution steps programmatically to ensure uninterrupted Multi-Master synchronizations.

Comments