Syncing source objejectsid to destination msexchmasteraccountsid

Created: 2018-06-20 11:56:50
Modified: 2018-06-20 11:56:50
Tags: Active Directory Custom Mapping UnitySync

A UnitySync connection can set msexchmasteraccountsid of a destination object.

We recommend you use a test connection to sync a single object before applying this change to your production sync.

1) If you do not already have one, create a custom object map file. 2) Insert this line at the bottom of the map file: ^msexchmasteraccountsid^=^objectsid;binary^

3) If you do not already have one, create a custom sourcedef file.

The default sourcedef file for an ActiveDir to ActiveDir configured connection includes both objectsid and objectsid;binary. This works fine with a Windows 2008 (or earlier) Source directory. However, once upgraded to Windows 2012 or higher, the sourcedef must be customized to remove objectsid leaving only objectsid;binary.

4) In the custom sourcedef file, look for the line that starts attribs=. This should be one long line, each attribute separated by a comma.

a) Scroll to the right…you should see both objectsid and objectsid;binary.
b) Remove objectsid from the list (including the following comma) c) Leave objectsid;binary.
c) Click Save to preserve your custom sourcedef.
d) Click Save on the tab to confirm selection of the custom sourcedef.

5) To confirm your results:

  • Run a new Discovery and a Simulation at Log File level 3-Detailed.
  • The Source Entry should now show objectsid;binary.
  • The Dest Entry should now show msexchmasteraccountsid being set to a base64 coded value.
  • If satisfied, run Sync and msexchmasteraccountsid should be populated on the destination.

If you run into trouble or have any questions, please contact

Share this article:

  1. Directify - Self Service

  2. Mimic - Replication

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