US English (US)
GB English (UK)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Create ticket
English (US)
US English (US)
GB English (UK)
  • Home

legacyExchangeDN implicit writes

Written by Neil Langston

Updated at August 9th, 2024

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Getting Started
  • FAQs
  • API Documentation
  • Integrations
  • Migration Agent
  • Directory Synchronisation
  • Remote DC agent
  • Remote Password Sync Agent
+ More

Table of Contents

Default processing

legacyExchangeDN has to be written as an x500 address in the proxyAddresses attribute in the target directory to maintain replyability and calendaring when also migrating mailbox data.

legacyExchangeDN is written implicitly by PowerSyncPro Directory Synchronisation as part of default processing when Mail-Enable is selected.

Default processing

PSP will always process the following attributes when Mail-Enable is selected.

  • mail
  • mailNickname
  • proxyAddresses
  • groupType
  • reportToOrignator

If those attributes are present on the source object, they will be written to target.  The legacyExchangeDN is written to the proxyAddresses attribute as an x500 address.

If they are not present, PSP will build them and set the appropriate target attributes i.e.  

sAMAccountName to mailNickName

NOTE:  If the mail attribute is not present on the source object, then no mail attribute will be written to the target.  This is by design.

Plus the following attributes are written for mail-enabled users if the target schema is extended for Microsoft Exchange

  • legacyExchangeDN This is created as a GUID + sAMAccountName
  • msExchRecipientDisplayType set as required for User/Group/Contact
  • msExchRecipientTypeDetails set as required for User/Group/Contact [TvB8] [CM9] 
  • showInAddressBook set per target if present in the Address Lists Container in the Configuration\Services\Microsoft Exchange\[org]

NOTE:

msExchVersion is NOT set by default.  If you have a reason to set this then please create a mapping and if necessary, use a Simple Expression to hard code a value.

msExchRemoteRecipientType is also not set by default.  If you have a need to set this to control the mailbox in Microsoft 365/EXO, then use Complex Expressions to get / set msExchRecipientDisplayType, msExchRecipientTypeDetails and msRemoteRecipientType as desired

 

Attribute Mappings

If there are attribute mappings present in the mapping’s configuration, they will always be processed.

Mappings supersede Default processing.  e.g. there is a mapping like sAMAccountName to mailNickName or a complex expression to set mail, proxyAddresses or msExch* attributes - then those mappings will take precedence.


exchangedn implicitwrite

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • No License for Domain
  • Workgroup workstation migration process
  • BPRT is the Owner Workstation in Entra
  • Microsoft errors from the field
  • Intune Enrollment has not succeeded

Subscribe to Newsletter

Drop your email in the box below to sign up. We promise to keep our updates relevant and useful – and we’ll never share your details.

PowerSyncPro is the ultimate product for easing the pain and frustration during mergers, acquisitions, divestitures, and consolidations.

Terms & Conditions

  • FAQs
  • Privacy Policy
  • Cookies
  • Anti Slavery Notice

PowerSyncPro

  • Case Studies
  • Contact sales
  • Meet the Team
  • EULA

Get Connected

Room 73, Wrest House, Wrest Park, Silsoe, Bedford, England, MK45 4HR
info@powersyncpro.com

Twitter Youtube Linkedin

Knowledge Base Software powered by Helpjuice

Expand