Can anyone tell me how exchangeLegacyDn got in my active directory?? I did a new install into a new AD that never had exchange before We have an 08R2 domain with exchange 2010. The legacyexchangeDn's are not letting some of my users activate their BB All the legacyDn's are different for each user! /o=Exchange1/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user114a1d5b3 /o=Exchange1/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user24aacf038 The legacyExchangeDn from AD /o=Exchange1/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=TORVSRVEXCH/cn=Microsoft Private MDB Shouldnt all the legacyDn's be the same???? How can I rectify this as it is also causing some NDRs TIA Wayne

And you're not migrating any accounts? If brand new install then yes the legacyexchangedn uses same convention, would differ if you migrated accounts from different Exchange orgs. You need to add these legacyexchangedn's as an x500 email ddress into their accounts in order for older replies to work and not get the ndr. Once you have added them back then BES activation will work, but you either need to recreate their BES account or run handheldcleanup or change the mailbox agent ID in order for BES to rescan the user DN again. How to set X500 proxy addresses for Exchange Server 2003 recipients and for Exchange 2000 Server recipients http://support.microsoft.com/kb/313324James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Hi James Our legacy domain was admined by non techy type users so was so full of garbage I created a whole new domain all the users were also using an IMAP mail account before we bought exchange So are you saying that I cant set this via a policy?? nobodies LegacyExchangeDn's are the same...the are all appended with some alph-numeric digits

You're getting the NDRs because the legacyexchangedn is missing. What happened to the values? You need to know what the original values were before you can even add them. Post an NDR. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Hi James I dont know where they would come from as we never had an exchange server until this 2010 install All our users were connecting to an Mdaemon IMAP server until now The IMAP server wasnt even part of the domain So we could use both servers during the migration I added a connector on 2010 responsible for the .com address which IMAP is responsible for All the migrated users once on exchange got a .ca address as priimary and .com and an alias

Can you post one of the NDR messages?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

LegacyExchangeDN is the unique identity for all the mail-enabled objects, and won’t be changed once being created Quote: ” The legacyexchangeDn's are not letting some of my users activate their BB” How did you confirm that? Is there any related procedure that you have used to test?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi James RIM confirmed the issue is related to legacydn's When I do a mapi test on the BES it comes back with the legacydn of the user Like I keep saying...how did these values get there if there was never an exchange org in this domain?

I'm not sure how it got changed since I'm don't know the history behavior the server. Yes BES uses the DN when activating, if it doesn't find it it fails. You need to add back all the DNs. I'm not sure what the original legacyexchangedn is nor what the new one is since you're not posting the NDR. If all your old legacyexchangedns have some arbitrary random number "bsmith47dfj34r" then forget about finding an automated solution to populate it. The only times I've seen the random numbers get generated was during migrations.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Quote: “how did these values get there if there was never an exchange org in this domain?” You said “We have an 08R2 domain with exchange 2010”, the problematic users have associated mailbox, right? Could the synchronization work for newly created mailbox on the exchange 2010 server? Please make sure that ehe value of the “legacyExchangeDN” is the correct one based on the format below: /o=ExchangeOrganizationName/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=DisplayNamePlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How's the issue currently? Any further information?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi James Via MS support I had to disconnect the mailboxes and then reconnect the affected users This seemed to work!! Thanks