The secret about a successful export-to-pst and import-from-pst migration is called Add Custom Address, type X500

项目
10/25/2011

The last few months, I have had the below question pop up regularly…

Question:

is it possible to export the content of my On Premises mailboxes to PSTs, and then import them into my brand new Exchange Online environment?

Answer:

Yes, you definitely export your mailbox content to a PST, and import that PST back into your new mailbox

But, the problem that usually pops up is, that when replying to a mail that has been imported back into the new mailbox from the PST, and it’s a reply to a another mailbox homed in the same mail environment, a user gets the following NDR:

Delivery has failed to these recipients or groups, The e-mail address you entered couldn’t be found…. as seen below:

Solution?

One way of solving this, is when you reply to a mail imported from your PST, and destined for anyone in the same Exchange environment, to just remove the name, and search for it again in the Global Address List, that will work

But: is that user friendly?

Definitely not, so, time to investigate, and come up for a better way to solve this!

Setting the scene

I currently have an Exchange 2010 Sp1 On Premises deployed, with two mailbox-enabled users:

Both mailbox-enabled users have sent a few mails between one-another:

Now, I want to export the content of these two mailboxes to a PST, that I want to import into a brand new Exchange Online environment. First I will delegate myself (being the administrator) the abililty to export mailboxes to a PST using the Exchange Management Shell cmdlet New-MailboxExportRequest, by running the following line in the EMS: New-ManagementRoleAssignment –role “Mailbox Import Export” –user “MsBelgium\Administrator”

Followed by the export itself:, issuing New-MailboxExportRequest:

And double-check to make sure it’s finished, using Get-MailboxExportRequest:

Next up: Create two mailbox-enabled users in my Office 365 environment, and hand out the same e-mail addresses to both users:

Everything is looking as it should, being, ok Smile

Time to open up Robin’s mailbox using Outlook Anywhere, and import the previously exported PST file:

Everything seems to be in order, but now, Robin wants to reply to a mail received from his colleague Rita, now watch the MailTip provided by Outlook 20101

But let’s just ignore the warning provided by the MailTip, and press Send…. and let’s have a look at the NDR we are getting immediately:

and the below info, Diagnostic information for administrators:

Interesting, searching the web, got me more information about this issue, for example at the following links:

So, how to solve this?

Simple: Use the Exchange Management Shell, or the Exchange Management Console to add the X500 address to the mailbox-enabled users

After clicking OK, and checking with the Shell we can see the X500 address has been successfully added:

When replying to the same message, we don’t get the MailTip anymore Smile

And the message arrives, without any problem:

Exchange simply rocks!

Ilse

Comments

Anonymous
November 02, 2011
I had the same issue with several users after migrating from Exchange 2003 to Exchange 2010 SP1. Thanks, great article!
Anonymous
January 10, 2014
Pingback from Migrating Exchange 2003 straight to Exchange 2013 | CodeTwo Squad Blog
Anonymous
January 10, 2014
Pingback from Migrating Exchange 2003 straight to Exchange 2013 | CodeTwo Squad Blog
Anonymous
January 10, 2014
Pingback from Migrating Exchange 2003 straight to Exchange 2013 | CodeTwo Squad Blog
Anonymous
January 10, 2014
Pingback from Migrating Exchange 2003 straight to Exchange 2013 | CodeTwo Squad Blog
Anonymous
January 10, 2014
Pingback from Migrating Exchange 2003 straight to Exchange 2013 | CodeTwo Squad Blog
Anonymous
June 07, 2014
I had the same issue after exporting Exchange 2010 SP1 mailboxes to PST, then importing them to new Exchange 2013 SP1 in a new Active Directory forest.

Didn't think I would find a solution for that. I instructed the users to remove the mail address and select it again from the address book, as you mentioned in the first solution.

Having read this article, I'm going to try your second solution, since it would be more convenient to the end users.

Thanks in advance!
Anonymous
June 24, 2014
Excellent article - works for me. Many thanks
Anonymous
August 05, 2014
Would this apply to a migration from 2003 to 2013 exporting the .PST and then importing
Anonymous
December 03, 2015
The comment has been removed
Anonymous
February 13, 2016
GREAT POST.

But THIS doesnt work in OFFICE365 so WHY would M$ consultants send me HERE???

通过