• State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 20 subscribers
  • Views 23441 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LegacyExchangeDN and X500 - adding random numbers to LegacyExchangeDN attribute - random x500 addresses on resource mailboxes

slav
over 5 years ago

I have a problem with some resource mailboxes I want to migrate. The issue is once those mailboxes got migrated and a full syn runs, qmm changes legacyexchangedn values adding random digits to the and of the value. 

for example: X500:/o=MY Org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=somemailnickname35131471,

Then, the uttered value does not match the primary X500 address and the legacyexchangedn value got changed again. At the end, proxyAddresses attribute contains 400 different/random x500 addresses.

I thought the issue is related to the fact the mailnicknames contain hyphens (some-mail-nickname). I changed them by removing the hyphens but that didn't fixed the problem. 

Anyone knows how to fix this ?

Also, I would like to know how to prevent qmm from changing legacyexchangedn values. Since there is no such option in qmm settings there must be a way to do that change in the registry or lds database.

Important note: Source exchange is 2013 and Target is 2010 SP3

 Also I noticed that mailnickname doesn't get synced and has no value in the target domain. (resource mailboxes only)

Regards,

Slav

Parents
  • 0 over 5 years ago

    Slav,

    The X:500 is for reply ability for existing emails.  Is this causing you an issue?

  • 0 over 5 years ago in reply to Enrico Mancini

    Sort of. LegacyDN doen't match  any X500 addresses in proxyaddresses attribute. 

    For example the LEDN is X500:/o=MY Org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=somemailnickname35131471

    But the X500 is X500:/o=MY Org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=somemailnickname35131472

    LEDN technically should be copied to proxyaddresses attribute as a x500 address.

    I'm also trying to figure out why there is no value under mailnickname in the Target AD.

    User and group objects have been successfully staged/migrated in the Target AD and I hadn't have that issue before.

  • 0 over 5 years ago in reply to slav

    The source LegacyExchangeDN should match a target proxyaddresses value.  What the value is in the target for the LegacyExchnageDn only needs to be forest unique. It does not need to match anything 

  • 0 over 5 years ago in reply to Jeff Shahan

    having the same value in the LegacyExchnageDN and proxyaddresses would create a duplication of addressing 

  • 0 over 5 years ago in reply to Jeff Shahan

    I know it should but it doesn't. After qmm figures out the values don't match, it generates another value which again doesn't match. That happens over and over again. Once, I have over 600 entries (of x500 addresses) under proxyaddress attribute

  • 0 over 5 years ago in reply to slav

    "User and group objects have been successfully staged/migrated in the Target AD and I hadn't have that issue before."

    Did you use QMM to perform the staging?

    Did you enable the Exchange options in the QMM DSA? - I could be wrong but I don't believe mailnickname will be brought over as part of the default "AD only" attribute set.

  • 0 over 5 years ago in reply to JohnnyQuest

    You are correct. MailNickname is only handled by the MBReDir and the Exchange tab has to be enabled for that. 

  • 0 over 5 years ago in reply to JohnnyQuest

    I used Qmm to stage the accounts.

    Also Exchange options have been enabled in the DSA. I want to point again, the problem happens only if an account has special characters in the values of affected attributes.

Reply
  • 0 over 5 years ago in reply to JohnnyQuest

    I used Qmm to stage the accounts.

    Also Exchange options have been enabled in the DSA. I want to point again, the problem happens only if an account has special characters in the values of affected attributes.

Children