Sync Now events now name the correct Active Directory server

Triggering Sync Now
 for a customer records an event for each source that was synchronised. The Active Directory event reported success but named the AD member server
 rather than the AD server
 — the domain controller the sync had actually run against. Because it named a machine that wasn't the sync target, it looked as though the sync had only reached the member server.
The Active Directory entry now identifies the server the sync actually ran against, so the event log accurately reflects which systems were synchronised.
This was a reporting issue only — the synchronisation itself ran correctly against the intended servers; only the server named in the event was wrong.