Solved

migration between exchange 2007 and 2013 not working

Posted on 2015-01-07
9
13 Views
Last Modified: 2016-06-22
Hi, I have an exchange 2007 that I need to migrate to Exchange 2013.
I have approx. 20 mailboxs, with which I transferred 12 the other day with no problem. I am now trying to move the other 8. The migration sits there, saying it is syncing. It has been left for 24 hours and still sits there, saying syncing, the individual user status shows 0 moved on all users.

I have stopped the sync and made another with only a few mailboxs and that does the same.

I get no errors or logs to give me any idea on what is happening.

Can you help ?
0
Comment
Question by:total123
  • 4
  • 3
9 Comments
 
LVL 4

Accepted Solution

by:
Manoj Bojewar earned 500 total points
Comment Utility
Hi,

Restart Mailbox migration service on Exchange 2013. This will fix this issue.

Thanks,
Manoj
0
 

Author Comment

by:total123
Comment Utility
its starting to move now, thank you.
0
 
LVL 20

Expert Comment

by:SatyaPathak
Comment Utility
also i suggest you to check application log of Exchange 2013
0
 
LVL 4

Expert Comment

by:Manoj Bojewar
Comment Utility
Welcome. Please accept and close this question.
0
Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

 

Author Comment

by:total123
Comment Utility
I have tried the above solutons, as the mailbox started to move, it also failed.
I have tried the "get-moverequest -MoveStatus Inprogress | Get-moverequeststatistics" cmdlet to see what its doing.
I have all 5 users (moving over 5 at a time) with the status as "NetworkFailure"
Is there a way to resume this?
0
 
LVL 4

Expert Comment

by:Manoj Bojewar
Comment Utility
stop the failed mailbox migration. i resume it again.
0
 
LVL 4

Assisted Solution

by:Manoj Bojewar
Manoj Bojewar earned 500 total points
Comment Utility
use this command to stop failed migration.

get-moverequest -movestatus Failed | remove-moverequest
0
 

Author Comment

by:total123
Comment Utility
That seems to have got it going now
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
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.

763 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

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now