HIDDEN: Can UnitySync map LegacyExchangeDN?
Created: 2012-04-20 08:09:59Modified: 2017-06-11 08:28:31
Tags: Custom Mapping Exchange 20xx UnitySync
Syncs to Ex2007/10 will likely require a mapping to set LegacyExchangeDN .
Default mappings in UnitySync include setting of LegacyExchangeDN, ProxyAddresses (Ex2000) and OtherMailbox (Ex55). These default mappings should be sufficient to allow mail delivery to a legacy system. We recommend you test your connections using default mapping to determine if additional mappings are necessary before trying any of the map file customizations outlined below. Always test map file changes on [[841|a single test object]] before running a regular sync. Proper testing of this mapping requires mail delivery tests, including Reply-To addressing.
If you have upgraded from SimpleSync and are using custom maps created prior to version 5.1.8, you may not have the proper mapping for LegacyExchangeDN.
If you want to sync the source Exchange 5.5 x500 address to the destination Exchange 2000 legacyexchangedn attribute of synced objects, add the following mappings to [[239|a Custom Object Map File]]: :legacyexchangedn={{{~x500~}}} :proxyaddresses=X500:{{{~x500~}}}
If you want to sync the Ex2000 legacyexchangedn value to your Destination Ex55 objects, add the following mapping to a [[239|a Custom Object Map File]]: :othermailbox={{{^legacyexchangedn^}}}
If you want to sync the Ex20xx legacyexchangedn value to another destination Ex20xx directory, add the following mapping to a [[239|a Custom Object Map File]]: :legacyexchangedn={{{^legacyexchangedn^}}}