When a one way synchronization is configured, the proxy addresses from the target are coming over to the source. Why is this happening and how is this going to affect my environment?
IMPORTANT: This behavior was changed. As of QMM 8.6 only Primary SMTP address is copied back to the source and set as Secondary SMTP address in a one way sync scenarios. If Directory Synchronization job is configured as two way, all SMTP addresses are synchronized two way.
When the source and target accounts are matched by the Directory Synchronization Agent (DSA) they are considered to be a pair. The DSA agent synchronizes proxy addresses both ways between matched pairs even in a one-way sync scenario. This behavior is by design. The two way synchronization does not have any effect on mail delivery of the source mailbox because the primary proxy addresses such as Primary SMTP, are copied across to the source mailbox as secondary addresses and the current primary addresses will stay intact.
Please note that the deletion of proxy addresses from target objects is not synchronized back to the source object in a one-way sync. In fact, any updates to the source object (or a full re-sync) will cause the deleted proxy address to re-appear on the target object.
Since version 8.2, it is possible to configure Quest Migration Manager to synchronize the primary SMTP address of the source mailbox, i.e. copy primary SMTP address across as primary, to the target mailbox. Please see solution SOL39768 for more details: SOL39768 - Source Primary SMTP address is not being set as Primary on target objects -https://support.quest.com/SUPPORT/index?page=solution&id=SOL39768
There is also a method to filter the synchronization of certain proxy addresses during synchronization, e.g. to Skip SIP proxyAddress, however this process involves the modification of ADAM entries. Please contact support to obtain this method if needed.
