Custom Mapping: Setting legacyExchangeDN on synced AD contacts

Typically, the the use of a destination Domain Admin login ID returns the valid legacyexchangedn root value. However, we have seen instances of an error even when using Domain Admin.

The error looks like this:

Error Summary : 8/1/2011 12:38:24 PM
LegacyExchangeDN Failure | 1
Fatal Error | 1

This error indicates the auto detection of destination legacyexchangedn was not successful. In order to proceed, you must manually identify the destination legacyexchangedn root value. Then, insert the value using the override parameter ‘exch-legdn’ in config.txt.

Note: If appropriate, there is a way to disable the auto detection of the destination legacyexchangedn root value. See the Method #3 below.

There are two ways to find the value for the destination legacyexchangedn root:

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 find the legacyExchangeDN attribute value of a contact that was manually created on the Destination. (You can see this in the contact’s attribute properties via Users & Computers).

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.

Using the exch-legdn override in config.txt

Once you know 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:

exch-legdn=/o=org/ou=YourAdministrativeOU

Once exch-legdn is set, leave the default legacyexchangedn mapping unchanged. It will now work as designed.

Default mapping:

legacyexchangedn=~legacyexchangedn~/cn=Recipients/cn=~smtpname~.~smtphost~

Method #3 - Disable legdn detection

There are circumstances where detecting the destination legacyexchangedn root value is unnecessary. In this case, you can add an override to the connection config to disable this function.

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

exch-legdn=disable

• Click Save.
• Click Save to save the connection.
• Run a Simulation to confirm results before running a Sync.