Solved

Moving Mailboxes from Exchange 2007 to Exchange 2013

Posted on 2016-07-26
3
32 Views
Last Modified: 2016-08-16
Hi Experts,

I have 2 Exchange servers in the same domain, one is Exchange 2007 and the other one is Exchange 2013.

In Exchange 2013, I initiate a mailbox move from the 2007 server but it has been stuck with the status "Syncing" for over 48 hours.

So in the Exchange powershell, i ran the following command
Capture.PNG
Here is the result
Capture1.PNG
Can anybody shed more light on this error and what i can do to resolve it?
0
Comment
Question by:jnsimex
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 16

Expert Comment

by:FOX
ID: 41730047
Heavy load on the server it seems.  Suspend the move and start off hours.

ref link:http://blog.manton.im/2015/04/exchange-2013-job-is-waiting-for.html

suspend the move ref link:  http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2010/ManagementAdministration/SuspendMailboxMoves.html
ref link:http://blog.manton.im/2015/04/exchange-2013-job-is-waiting-for.html

**Always initiate the powershell command  from the new server **
0
 

Accepted Solution

by:
jnsimex earned 0 total points
ID: 41753142
So I tried doing the mailbox move during off hours and again, the move did not complete successfully so I bit the bullet and got MS involved.

They solved it by changing the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchange ResourceHealth\MRS from 0 to 1 and restarting the Mailbox Replication service.
0
 

Author Closing Comment

by:jnsimex
ID: 41757593
The issue was solved by Microsoft Support.
0

Featured Post

What Is Transaction Monitoring and who needs it?

Synthetic Transaction Monitoring that you need for the day to day, which ensures your business website keeps running optimally, and that there is no downtime to impact your customer experience.

Question has a verified solution.

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

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This article outlines some of the reasons why an email message gets flagged as spam on a recipient's end.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
how to add IIS SMTP to handle application/Scanner relays into office 365.

688 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