Exchange 2010 to Exchange 2013 Mailbox Move
Hi All,
I have in the last couple of weeks started upgrading our exchange 2010 environment to exchange 2013. Upgraded the domain first from 2008r2 to 2012.
Then installed my first exchange 2013 server and configured.
Managed to get all the linkages working through the exchange 2013 frontend back to the exchange 2010 servers.
Owa, ActiveSync and other services are working correctly.
Mail flows from one system back to the other and the reverse.
Created a new account on 2013 and this is also working successfully.
Exchange 2013 CU2
Exchange 2010 SP3
Let it bed in for a few days and then started to work on migrating the mailboxes.
This is where I come across errors.
If I use the EAC, I get the error saying that "The mailbox of user that is located on a server that is running version 14 can't be opened on a server that is running version 15"
If I run the New-MoveRequest command from the EMS, the command runs successfully, but then, doesn't actually complete. The Get-MoveRequestStatistics always shows queued and no 0%
The event log shows it starting but not finishing. I even waited a few days to see
I have tried different mailboxes. Also confirmed that the Schema has been updated correctly. Tried researching and confirming setting but I seem to have them correct.
Any assistance in nutting this out is appreciated.
Thanks
Cameron
I have in the last couple of weeks started upgrading our exchange 2010 environment to exchange 2013. Upgraded the domain first from 2008r2 to 2012.
Then installed my first exchange 2013 server and configured.
Managed to get all the linkages working through the exchange 2013 frontend back to the exchange 2010 servers.
Owa, ActiveSync and other services are working correctly.
Mail flows from one system back to the other and the reverse.
Created a new account on 2013 and this is also working successfully.
Exchange 2013 CU2
Exchange 2010 SP3
Let it bed in for a few days and then started to work on migrating the mailboxes.
This is where I come across errors.
If I use the EAC, I get the error saying that "The mailbox of user that is located on a server that is running version 14 can't be opened on a server that is running version 15"
If I run the New-MoveRequest command from the EMS, the command runs successfully, but then, doesn't actually complete. The Get-MoveRequestStatistics always shows queued and no 0%
The event log shows it starting but not finishing. I even waited a few days to see
I have tried different mailboxes. Also confirmed that the Schema has been updated correctly. Tried researching and confirming setting but I seem to have them correct.
Any assistance in nutting this out is appreciated.
Thanks
Cameron
Shreedhar Ette
When you execute Get-ExchangeServer on Exchange 2013 Powershell. Are you able to see both server?
ASKER
Yes I do.
I see the two current servers running version 14.3 and the new one running 15.0
Any other thoughts?
I see the two current servers running version 14.3 and the new one running 15.0
Any other thoughts?
Please refer this article:
http://www.petenetlive.com/KB/Article/0000788.htm
http://www.petenetlive.com/KB/Article/0000788.htm
ASKER
Hi shreedhar,
I have gone through this document and had followed these steps originally. Along with the official MS documentation.
Unfortunately, this has not resolved the issue.
Thanks for looking and do you have anything more?
I have gone through this document and had followed these steps originally. Along with the official MS documentation.
Unfortunately, this has not resolved the issue.
Thanks for looking and do you have anything more?
Please run New-MoveRequest and -Verbose at the end.
Post the output.
Post the output.
ASKER
I have attached the screen shot.
Removed all the identifying information only.
Thanks
EMSOutputCapture.JPG
Removed all the identifying information only.
Thanks
EMSOutputCapture.JPG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Good to know that issue now resolved.
Thanks for sharing step which helped to resolve.
Thanks for sharing step which helped to resolve.
ASKER
My own comment has the correct answer. Without the checking from shreedhar, I would not have checked other things