DirWiz Logo

Article Tags

Custom Mapping: Setting legacyExchangeDN on synced AD contacts

2021-02-22 15:56:50
Active Directory Exchange 20xx UnitySync 

By default, legacyExchangeDN is set to:


The default works as long as the Destination Login ID is Domain Admin.

At sync time, using Domain Admin credentials allows you to automatically detect the Destination’s legacyExchangeDN root value. With this value, the default mapping can successfully set legacyExchangeDN on the synced contacts.

If you are using a Domain Admin account, you shouldn’t need to use the legacyExchangeDN override described below. However, if you are using a Domain Admin account and receive a LegacyExchangeDN Failure error you should apply the override detailed below.

Using a NON Domain Admin login account

If you do not use Domain Admin credentials for the destination Login ID, you will receive the error LegacyExchangeDN Failure. This occurs because the login account is unable to detect the Destination legacyExchangeDN root value without Domain Admin permissions. When this occurs, the legacyExchangeDN root must be defined using a configuration parameter override.

Method #1

To identify the appropriate override value we suggest using ADSI Edit to view the legacyExchangeDN property.

  • From the root of your domain, select:

    • CN=Configuration,
    • then CN=Services,
    • then CN=Microsoft Exchange,
    • then CN=YourExchangeOrg,
    • then CN=Administrative Groups.
  • Now look for the appropriate Administrative Group for your Exchange version:

    • for Exchange 2003
      • CN=First Administrative Group
    • for Exchange 2007
      • CN=Exchange Administrative Group (FYDIBOHF23SPDLT)
    • for Exchange 2010
      • CN=Exchange Administrative Group (FYDIBOHF23SPDLT)
  • Then click Properties.

    • Look for the Attribute ‘legacyExchangeDN’.
    • Click Edit to view the value. Click Cntl-C to copy the value.
      /o=E2k Organization/ou=First Administrative Group

IMPORTANT NOTE: This may be called something different in your organization.

Method #2

Alternatively, you may view the legacyExchangeDN value of a User account manually created on the Destination.

For example:
/o=E2k Organization/ou=First Administrative Group/cn=Recipients/cn=John.Smith

IMPORTANT NOTE: You do not need to include the ‘/cn=Recipients/cn=name’ portion of this value as it is appended by the default mapping.

Finally, once you have the proper legdn root value, add it to your configuration as follows:

  • Go to the Custom tab in UnitySync
  • Click the Raw Config button.
  • Add a line with the value in the following format:


Share this article: Twitter reddit