Syncing source legacyExchangeDN as an x500 proxyaddress on the Destination

Created: 2016-06-21 10:44:32
Modified: 2017-05-17 20:49:17
Tags: Active Directory Custom Mapping Exchange 20xx Troubleshooting

If you are performing Exchange migrations on your synced directories, you may run into reply-ability issues. In most cases, this can be resolved by syncing the source legacyExchangeDN to the Destination contact as an X500 proxyaddress.

Manually confirm the x500 address will resolve your issue.

  • On the Destination contact, manually add an x500 proxyaddress matching the source legacyExchangeDN. Verify the reply-ability is successful.

  • Further, you can test the below custom mapping on a single tests object.

  • Confirm the above tests are successful before running a production Sync with the new mapping.

Customizing your object map file to sync source legacyExchangeDN as a Destination x500 address:

1) If you do not already have one, create a custom object map file.

2) In the custom object map file:

  1. Leave the existing default proxyaddresses mapping in place: (proxyaddresses=[proxyaddresses)//\

b) Below that default mapping, insert this custom mapping:

c) Click Save on the custom map window and again at the bottom of the tab.

d) When you run this connection, you will see a Modify of all synced contacts.

All Destination contacts should now contain an x500 proxyaddress with the legacyExchangeDN value from the Source, correcting reply-ability issues.

Share this article:

  1. Directify - Self Service

  2. Mimic - Replication

  3. UnitySync - Sync
  1. emPass - Sync
  1. Profiler
  2. SimpleSync