Link to home
Start Free TrialLog in
Avatar of kopite47
kopite47Flag for Ireland

asked on

Office365 migration error on legacyexchangedn value

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?
ASKER CERTIFIED SOLUTION
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of kopite47

ASKER

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?
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

?????
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