I have two AD domains with respective Exchange organizations. Source AD domain is Functional Level 2003, contains an Exchange 2003 server (running on Server 2003 R2 SP2) and Exchange 2010 SP3 Server. (running on Server 2008 R2 SP1) Target AD domain is Functional Level 2012, contains an Exchange 2013 server. (running on Server 2012) Mailboxes are currently contained in the Exchange database of the Exchange 2003 server. I am able to migrate mailboxes from 2003 to 2010 without issue using a Local Move Request. Remote Move Requests from the EMC in Exchange 2010 seem to result in any number of errors. I've attempted to use the Prepare-MoveRequest.ps1 script, but they only ever result in "Error looking up source MBX user@domain in source forest.", so I'm kind of stuck as to how to proceed. What is the recommended method, given my scenario, to migrate a user from Exchange 2003 to 2013?

Hi You won't be able to move mailboxes from 2003 to 2010, you will need to move them to 2010 first. You should do the moves from the 2013 server using the autodiscover hostname that point to your 2010 server. Steve

I'm good with moving them from 2003 to 2010, that much I can do successfully. Question is, how do I go about initiating the move from 2013? The ECP doesn't seem to allow anything except outgoing mailbox movement.

You should be able to get as far as being ready to make the move. That will fail however since Exchange 2013 needs a rollup before the move will work. That said, running Prepare-MoveRequest.ps1 should work, are you running it in the target Exchange 2013 environment? Are there any firewalls or other network restrictions between the Exchange 2013 and Exchange 2010 server? Is the trust up and verified ok? Can the target Exchange 2013 resolve the source Exchange 2010 server using DNS? Have you tried using the host file for the target Exchange 2013 server so it can resolve the source Exchange 2010 server?Martin Sundstrm | Microsoft Certified Trainer | MCITP: Enterprise Messaging Administrator 2007/2010 | http://msundis.wordpress.com

So, I was running it on the source domain, rather than the target. Running it on the target, it prepares the mailbox to move successfully. That said, there are no firewall or network restrictions in place, all servers involved exist on the same subnet. The forest trust is up and verified on both ends. Both Exchange servers can resolve the other correctly. But, it seems like all of this was a symptom of attempting to prepare for the move on the source as opposed to the target. All that aside, I'm gathering that pre-Exchange 2013 CU1, moving a mailbox from 2010 to 2013 is not actually functional yet? Even in a cross-forest scenario where co-existence is not necessary?

Yes this is correct, CU1 should be available in Q1 so within the next month. Steve

I am doing moves from 2007 to 2013 - although not yet supported I guess. I am doing it this way .\prepare-moverequest.ps1 -identity 'test1' -remoteforestdomaincontroller sourcedc1.domain1.local -remoteforestcredential $remoteuser -localforestdomaincontroller targetdc1.domain2.local -localforestcredential $localuser that enables a MEU on my target and appends a x500 (add -verbose if you'd like) then I do a new-moverequest -identity test1 -remotelegacy -targetdatabase 'mailbox db1' -remoteglobalcatalog 'sourcedc1.domain1.local' -remotecredential $remoteuser -targetdeliverydomain 'domain2.local' that starts the move. It finishes with 'completed with warnings' (warning being cant find target database, which is the target on the source). If you have large items and the source and target exchange env is configured differntly when it comes to sizeacceptance, then dont forget to set the -largeitemlimit and -acceptlargedataloss switches. Good luck

Hello, base on the following articles: Exchange 2010 <acronym title="Service Pack 3">SP</acronym>3 allows Exchange 2010 servers to coexist with Exchange 2013 <acronym title="Cumulative Update 1">CU1</acronym>, which is also scheduled to be released in Q1 2013. Customers can test and validate this update in a representative lab environment prior to rolling out in their production environments as an important coexistence preparatory step before introducing Exchange Server 2013 CU1. http://blogs.technet.com/b/exchange/archive/2013/02/12/released-exchange-server-2010-sp3.aspx you will not be able to migrate to exchange 2013 from 2010 unless you update your exchange 2013 CU1.

To be in a supported state from MS and for the move to complete successfully, you need CU1 for Exchange 2013 which should be out soon.Rajith Enchiparambil | http://www.howexchangeworks.com |