I'm running a test lab on testing a cross-forest migration between Exchange 2007 and 2013. I have been unsuccessful in finding guides on a successful cross-forest migration between the versions I am working with. 

Environments: Exchange 2007 SP3 RU11 -Windows 2003 x64 Exchange 2013 CU2 -Windows 2008R2

I am currently stuck at the point of migrating mailboxes between the two forests. 

When trying to create a migration endpoint via the ECP Admin site, I get this message:

When I do a Test-MigrationServerAvailability in the shell I get a similar message:

Since my test lab is an isolated environment not publish to the net, I am unable to run the Analyzer. 

However, I did try to recreate the steps in a production environment and got the same results. I ran the analyzer on the Autodiscover and RPC test with success.

I installed Outlook on the Exchange 2013 server and created a profile for a mailbox from the Exchange 2007 server to see if the Autodiscover service is working by doing a Test Email AutoConfiguration and it was successful.

I have access to an Office365 environment where I can see if I can create an migration endpoint. I noticed Exchange Online had more options for migration endpoint and was successfully create an endpoint with the OutlookAnywhere option. 

However, in my test environment the option was not there and for the commands Test-MigrationServerAvailability and New-MigrationEndpoint does not have the -ExchangeOutlookAnywhere or -RPCProxyServer flags. 

Do you think it could be something I overlooked during my configuration or is there a limitation with Exchange 2013 on creating endpoints compared to Exchange online?

• Edited by nigzero 18 hours 10 minutes ago

Hi,

I think we can refer to OliverMoazzezis suggestion in the following thread:

http://social.technet.microsoft.com/Forums/exchange/en-US/35828bef-3eaa-4540-b2ef-0dc1da0d77ca/cross-forest-migration-from-exchange-2007-to-exchange-2013

Thanks,