• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2510
  • Last Modified:

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?
0
kopite47
Asked:
kopite47
  • 2
  • 2
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
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
 
kopite47Author Commented:
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
 
kopite47Author Commented:
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
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
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

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now