locked
LegacyExchangeDN and special characters RRS feed

  • Question

  • After crossforest migration of two test users from 2003(and 2007) something weird happends.

    User 1: A user with special language characters in name or last name

    User 2: A user with NO special language characters in name or last name (ab...yz)

    Via ADMT the AD object is migrateted and after that a preparescript is executed. To the end the new-moverquest is executed with correct syntax.

    It works fine, User 1 and 2 can log in but....

    When User 1 click on send in Outlook/webapp it says: "You do not have permission to send mail" - User 2 can send mails

    when User 2 send a mail to User 1 and User 2, the user 2 mail is received, but the user 1 mail return with an error:

    Delivery to the following persons or groups failed
    "namewithspeciallanguagecharacters"
    The specified email address was not found. Check the address and try sending the message again. Contact helpdesk if the problem persists.

    Connect server: xxxxxxx.xxx.com
    IMCEAEX-_O=xxx_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=J+3Frgen+20+3Fsterg+3Frd@xxxxx.xxx
    #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

    The difference between user 1 and 2 is LegacyExchangeDN where User 1 has a LegacyExchangeDN with name+last name with special language characters and user 2 has the name+lastname without special language characters.

    It will work if I change the  User 1 LegacyExchangeDN from /o=xxxxxx/....../cn=Name Lastname TO /o=xxxxxx/....../cn=mailnickname but is this the correct way to do it and are there disadvantages of this solution

     

    Tuesday, April 27, 2010 8:38 PM

Answers

  • you will have to make the new DN matching the old DNS so users can reply to the old emails, I believe that the special charachter is not working becasue the language is not installed on Exchange and DC's try to install the language on the Exchange and DC and try again
    Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
    • Proposed as answer by Xiu Zhang Friday, April 30, 2010 8:41 AM
    • Marked as answer by Xiu Zhang Thursday, May 6, 2010 2:49 AM
    Wednesday, April 28, 2010 7:45 PM

All replies

  • you will have to make the new DN matching the old DNS so users can reply to the old emails, I believe that the special charachter is not working becasue the language is not installed on Exchange and DC's try to install the language on the Exchange and DC and try again
    Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
    • Proposed as answer by Xiu Zhang Friday, April 30, 2010 8:41 AM
    • Marked as answer by Xiu Zhang Thursday, May 6, 2010 2:49 AM
    Wednesday, April 28, 2010 7:45 PM
  • Hi,

    Special characters could not be recognized.

    Regards,

    Xiu

    Friday, April 30, 2010 8:41 AM
  • I can see the old legacyExchangeDN is equal to mailalias (mailnickname) which does not contain Special characters (typical it is initials).

    When migrate to Exchange 2010 it change the legacyExchangeDN if it contains Special character, so it contain Full Name and last name. 

    My solution is to change legacyExchangeDN to mailalias ( /o=xxxxxx/....../cn=Name Lastname TO /o=xxxxxx/....../cn=mailnickname)

     

     

     

    Monday, May 3, 2010 9:11 AM
  • Hi,

    Have you tried to install the related language pack on Exchange Servers and Domain Contollers?

    Regards,

    Xiu

    Wednesday, May 5, 2010 2:36 AM
  • Hi

    What is the use of LegacyExchangeDN in exchange 2010? Any help on this is appreciated

    Regards

    Prashant Chamme

    Friday, July 23, 2010 9:38 AM