Category:Exchange 200x
Last Updated:2010-02-09
Yes. SimpleSync can sync to/from Exchange 2007 and Exchange 2010.
As of v5.0, all of the below requirements are met automatically. The recommended customizations are only required in pre v5 Simplesync installations. Whenever possible, it is highly recommended you upgrade to SimpleSync v5 rather than run v4 with the below customizations.
SimpleSync does not rely on the RUS. SimpleSync writes to AD, creating/updating your user or contact objects. Default mappings include proxyaddresses (smtp/x400) required to create mail enabled objects. Default mappings also sync all other required attributes. You may use custom map files to create/modify attribute mappings as desired. Many SimpleSync users have already migrated and are syncing successfully to Exchange 2007.
As of Ex2007, the following elements were found to be required by Microsoft.
If you are running pre v5 SimpleSync, the following customizations have been found to be required for most implementations when syncing to Exchange 2007 or 2010. These are customizations you can make to the attribute mapping, so the sync can automatically set mailnickname, ShowInAddressbook and LegacyExchangeDN automatically at sync time.
Note 1:
If you are running v4.7 or prior release, see the Syncs to Exchange 2007 set invalid value for mailnickname article for details on the custom mailnickname mapping that is required to sync to Ex2007. As of v4.8, the default mappings have been adjusted to support the new mailnickname requirement (the @ character is not allowed).
Note 2:
If your synced objects do not show up in the GAL, it may be necessary to use a custom mapping to set the a custom ShowInAddressBook on your synced contacts.
Note 3:
If your synced objects show up in the GAL, but delivery to the recipient fails, it may be necessary to set a custom legacyexchangedn on your synced contacts.
Note 4:
4a) After applying the steps to customize legacyexchangeDN as outlined in Note 3, you will run each Ex2007 connection. This allows the sync to set legdn and custom x500 addresses to avoid NDRs that may have begun after an earlier upgrade/sync. Verify mail delivery is successfully working.
4b) To complete this process, you should now return to each connection and add legacyexchanedn to the connection's no-mod-attrib list.
This is done so that future syncs will never modify legacyexchangedn, thus avoiding the potential for NDRs due to modified legdn.
Edit the config.txt for this connection. Insert the below line in it's entirety. (one long line including comma separated attribute list).
No-Mod-Attribs=legacyexchangedn,grouptype,objectclass,instancetype,
samaccountname,userprincipalname,name,cn,msExchHomeServerName,homeMTA,
homeMDB,msexchmasteraccountsid;binary,msexchuseraccountcontrol,useraccountcontrol,
pwdlastset
Save the config.txt.
Future runs of this connection will never modify the legacyexchangedn attribute.
As of SimpleSync v5.0.15, legdn is included in the default no-mod-attribs list.