SBS2008 / Exchange 2007 to Server 2012 / Exchange 2013 mailbox migration fails

Okay we're upgrading a clients server from Small Business Server 2008 running Exchange 2007 to Windows 2012 / Full Exchange 2013.

The 2012 has been joined up to the domain as a BDC (for now, yes I know its not recommended when running exchange) and Exchange 2013 is setup and running.  We've been using the following as a guide:

Everything seems to be fine, right up to the point of migrating a test mailbox from 2007 > 2012, it just fails with the following error:

Error: MigrationTransientException: MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎

Quick google suggests that the two servers cannot communicate because the 2012 cannot resolve the 2007 in DNS and NETBOIS.  I've checked and ping works lovely between them using the FQDN and just the NETBIOS name.

I've turned off the firewall on the 2008 server but beyond this I'm a bit stuck.  Ive been trying the mailbox move in EAC on the 2012 server - with both the destination DB name entered and without - still fails.

Is this a SBS anomilly?  The co-existance is only short term until we migrate all the mailboxes to prevent downtime.

For what its worth, the 2007 Exchange was migrated from an SBS2003 server some years back and there may be some traces of that original schema in the setup.

Help me?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Randy DownsOWNERCommented:
This could be part of your problem. Since it's SBS it will want to control Exchange.

The components that come with SBS such as Exchange, SQL, and ISA can only be installed on the server that is running SBS.
Jock_ScotlandAuthor Commented:

That stands for software bunndled with SBS, this new server were migrating to is not running SBS nor any components of it.  But I hear you.

Right now I discovered (quite) a few updates for the SBS box which were applying now.  I'm hoping that this helps in some way but it does seem like a comms issue.  

Incidentally I can telnet the SBS Exchange 2007 from the 2012 and get an open port - this is via both NETBIOS and DNS names.

The SBS Exchange is HUGE (for SBS anyway) and it may be crashing out somehow when we try to migrate mailboxes.
Jock_ScotlandAuthor Commented:
I had a better look at the 2008 server and realised that quite a few updates were missing, including a few Exchange update rollups.  Theyre now installed and the issue has changed a litte now, but in essence the problem is the same.

Running the following command from powershell:

New-MoveRequest -Identity '' -TargetDatabase "EXCH2013"

Gives me this error:

Mailbox database '68b59c00-2ef3-4c5c-93cf-2899f45befae' is offline.
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=EXCHSVR2013,RequestId=f85006e2-d247-4ed3-bf69-602710d0cbfc,TimeStamp=03/08/2015 20:
   00:11] [FailureCategory=Cmdlet-RemoteTransientException] CAACA33,Microsoft.Exchange.Management.RecipientTasks.NewM
    + PSComputerName        : exchsvr2013.server.local

...and I still cant migrate mailboxes.  

Ive also tried from the ECP - no errors, just doesnt do it!

Can anyone help?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Randy DownsOWNERCommented:
Maybe something in here will help. They are moving without Public folders.

Use this process if you wish to entirely remove the public folders from an Exchange 2007/2010 Organisation instead of performing a migration. This is a one way process. Data will be lost if you proceed.
Jakob DigranesSenior ConsultantCommented:
are all databases running on EXCHANGE2013? have you created a mailbox in EXCH2013 just to check?

(Sorry for asking somewhat lame questions - but in a migration scenario gone slightly wrong, one might look past the obvious)
Jock_ScotlandAuthor Commented:

Thanks for this, yeah we have a mailbox up and running in the Exchange2013 server - all seems well this side!
Jakob DigranesSenior ConsultantCommented:
do you see anything in event viewer during failed move?
you try to move from 2013 server?
Jock_ScotlandAuthor Commented:
Sorry - I need to clear this one up.  We're actually trying to migate from Exchange 2007 (running on SBS2008) into full Exchange 2013.  

Ive checked the log files in Event Viewer and the only thing which sticks out is a recurring  error as follows:

Event 1018, MSExchangeTransportDelivery

The account 'NT AUTHORITY\SYSTEM' provided valid credentials, but it does not have submit permissions on SMTP Receive connector 'Default Mailbox Delivery EXCH2013'; failing authentication.

Interestingly, there is no recieve connector called 'Defaul Mailbox Delivery EXCH2013' on the server - and a quick google suggests that there may me more than one connector listening on port 25.  That doesnt seem to be the case with this server though.  No idea where its getting this recieve connector from??
Randy DownsOWNERCommented:
This help?

Using ADSIEdit.msc wo check the Receive Connector permission:

1.Open AdsiEdit.msc.
2.Expand Configuration.
3.Expand CN=Services.
4.Expand CN=Microsoft Exchange.
5.Expand CN=<Organization name>.
6.Expand CN=Exchange Administrative Group (FYDIBOHF23SPDLT).
7.Expand CN=<Server Name>.
8.Expand CN=Protocols.
9.Expand CN=SMTP Receive Connectors.

Is the default one available there?
Jock_ScotlandAuthor Commented:
No, because this lists the Recieve connectors I can see in EAC - not the one which is shown in the error message in the post above.

This doesnt exist!

Default Mailbox Delivery EXCH2013

Even if I check using the Exchange Shell.
Randy DownsOWNERCommented:
Any idea where the non-existent came from ?  You could try creating it maybe.
Jock_ScotlandAuthor Commented:
I thought of that, then saw a post where somebody had done this and it didnt get rid of the problem....
Randy DownsOWNERCommented:
You could try exporting Exchange 2007 mailbox to pst & importing to 2013 Exchange. The post was for SBS 2003 but the principle should work. He had issues with offline Address book so you might want to remove that.

So I went to one user's PC and exported everything to a PST, I then deleted the mailbox from Exch2003, purged it and created a new mailbox on the Exch2010 server and imported the pst.
Jock_ScotlandAuthor Commented:
Thanks Randy, this was always option 2 however......

One of the mailboxes is 160Gb and its export is taking DAYS not hours (dieing 2007 server) - plus im not confident that we have everything exported.

Is there any way that we could create new mailboxes in Exchange 2013 but leave the 2007 ones dormant and export mail over time?
Randy DownsOWNERCommented:
Is the mailbox really that big? Maybe repair and/or export from client.

Maybe you could make the old Exchange 2007 mailboxes inactive & assign the users new mailboxes on Exchange 2013.

I would try it with a test account to make certain that it doesn't cause delivery issues.
Jock_ScotlandAuthor Commented:
Yep, its really that big and causing trouble.  Outlook just cant handle it and crashes so the End user is accessing via an iPad and ActiveSync.

I'm not sure how I would make a mailbox inactive without deleting it?
Randy DownsOWNERCommented:
Try this. Note the warnings.

The option that most people should be using in Exchange 2007 is to disable a mailbox. This is equivalent to the “Remove Exchange Attributes” option in Exchange 2003. This action does not remove the recipient object from Active Directory; it only removes the Exchange attributes from the object and marks its mailbox for deletion.

In either scenario, mailboxes marked for deletion are protected by the mailbox retention settings on the mailbox database (30 days by default). Once the retention period is met, the mailbox is permanently deleted from the database.

For additional information on managing user mailboxes in Exchange 2007 please see:
Jock_ScotlandAuthor Commented:

I dont like the potential risk of this so what we're going to do is a full information store backup using BackupAssist from the old server, then a restore to the new server.

On completion I'll post the process and result.

Randy DownsOWNERCommented:
Sounds like a good plan. Good luck.
Jock_ScotlandAuthor Commented:
Okay, an update.

We ended up setting up an who,e new domain with the Exchange2012 server integrated onto it.  After that we exported the old mailboxes to .PST files using BackupAssist from the IS backup.

There's not too many mailboxes so we imported the mail using the users Outlook client.

Result? Clean setup, now working properly.

Never again.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Randy DownsOWNERCommented:
I did suggest exporting to pst. Don't I get partial credit at least?
Jock_ScotlandAuthor Commented:
This is the only solution which worked
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.