Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Exchange 2010 - 2013 migration

Posted on 2014-02-24
4
Medium Priority
?
592 Views
Last Modified: 2014-02-24
My team and I are in the middle of two active Exchange 2010 to Exchange 2013 migrations for separate customers.  Both sets have exchange 2013 installed but no configuration beyond that.   What we noticed in both situations is the the Exchange 2013 server can see the Exchange 2010 server but not the other way around.   Example of what I mean.  In the Exchange 2013 power shell you can issue the get-exchange server cmdlet and it will reply back with both the Exchange servers.  If you issue the same cmdlet on the Exchange 2010 power shell you only get a result back of the Exchange 2010.   So my question is this normal or do we have an issue.   I'm proceeding with caution, so i have not moved anything yet.

On a side note, we also have another customer running Exchange 2007 server with Exchange 2013 install in their environment, this customers migration is in a holding pattern for contract reasons, but I did the same test on their Exchange 2007 power shell and it DOES give a result back of BOTH servers.
0
Comment
Question by:snowdog_2112
[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
  • 2
4 Comments
 
LVL 3

Accepted Solution

by:
Krishna Patil earned 2000 total points
ID: 39882786
This is perfectly fine. I have working setup of exchange 2007 + 2010 + 2013 is same domain.

You will get complete list of exchange servers from exchange 2007 and exchange 2013, but not from exchange 2010.

This is because, this command when it runs from exchange 2010, has filter of
version no less than 19...

VERBOSE: [15:44:01.828 GMT] Get-ExchangeServer : Searching objects of type "Server" with filter "(VersionNumber LessThan 1941995520)", scope "SubTree" under the root "$null".
0
 

Author Comment

by:snowdog_2112
ID: 39882816
Now to take it one step further with the information you provided, we can't do a local move request from the Exchange 2010 server but can on the Exchange 2013 server.   Does this fall under the same category?
0
 
LVL 3

Expert Comment

by:Krishna Patil
ID: 39882849
Yes, this is also expected.
You can do local move request from exchange 2010 to exchange 2010's other DB/Server.
But not to exchange 2013 MBX.

And from exchange 2013, you can migrate any mailbox to any server/DB.
0
 

Author Comment

by:snowdog_2112
ID: 39883046
Thank you for the information provided.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, just open a new email message. In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

609 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