Solved

Office365 migration error on legacyexchangedn value

Posted on 2013-01-17
4
2,277 Views
Last Modified: 2013-01-19
I am performing a cutover migration to Office365 from my Exchange 2003 server and one use has failed with the message: Failed to update one of the recipient properties. Couldn't find object "/o=First Organization/ou=first administrative group/cn=Recipients/cn=lmahony". Please make sure that it was spelled correctly or specify a different object.

The username is: aogara and not lmahony so this seems to be the issue.  I'm assuming the account was renamed at some point.

I have checked all the Exchange attributes and I have run adsiedit and checked the value for exchangelegacyDN but this is showing as: /o=First Organization/ou=first administrative group/cn=Recipients/cn=aogara which should be correct.

Is there something else I need to check, like I said all the values in ADUC look ok.

Any other suggestions?  If I remove the Exchange attributes and add them again through AD will it mess up the mailbox or is this safe to do?
0
Comment
Question by:kopite47
  • 2
  • 2
4 Comments
 
LVL 52

Accepted Solution

by:
Manpreet SIngh Khatra earned 500 total points
ID: 38788045
I guess the old account was renamed or a copy of an old account was made and a new one created

Add this as X500
/o=First Organization/ou=first administrative group/cn=Recipients/cn=lmahony

Or simply delete the Object and Mailbox after taking proper AD and Mailbox PST backup and create a new one

- Rancy
0
 

Author Comment

by:kopite47
ID: 38788117
I can't add an X500, I only have the option for X400 which is already there and looks correct.

It's Exchange 2003 (not sure if this supports X500 or not).

I'd rather not delete and re-create the account if possible, would probably be easier to do an IMAP migration of this one account but there must be an easier way though?
0
 

Author Comment

by:kopite47
ID: 38788136
Just Googled that and discovered how to add an X500 address (as a custom address).

One question, the username is actually 'aogara' so should the X500 address not be:

/o=First Organization/ou=first administrative group/cn=Recipients/cn=aogara

?????
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38789964
No the reason we dont want /cn=aogara as if thats what it needed it could have picked up from the LegacyExchangeDN and not ask the error is the data we use and create a X500 :)

- Rancy
0

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what the Office 365 disclaimer function is, why you would use it and its limited ability to create Office 365 signatures.
Find out what you should include to make the best professional email signature for your organization.
how to add IIS SMTP to handle application/Scanner relays into office 365.
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question