• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 604
  • Last Modified:

Exchange 2010 - 2013 migration

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
snowdog_2112
Asked:
snowdog_2112
  • 2
  • 2
1 Solution
 
Krishna PatilCommented:
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
 
snowdog_2112Author Commented:
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
 
Krishna PatilCommented:
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
 
snowdog_2112Author Commented:
Thank you for the information provided.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now