Hey All

\Exchange 2013\Scripts\Prepare-MoveRequest.ps1 : Error looking up source MBX email@domain.local in source
rest.
 line:1 char:1
.\Prepare-MoveRequest.ps1 -Identity email@domain.local -RemoteForestDomainC ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Prepare-MoveRequest.ps1



I am running this:  

.\Prepare-MoveRequest.ps1 -Identity email@domain.local -RemoteForestDomainController server.domain.local -RemoteForestCredential $remotecredential  -LocalForestDomainController dc01.dc.horseshoelane.
cal -LocalForestCredential $localcredential

I am at wits end with this one... any help would be appriciated..

------++++++---

New information as of 29/06/2015

Server does not appear to query the AD servers within the domain.

when trying to move a user that does not exist the same error comes up.

Standard AD queries work correctly on the exchange server, so get-aduser blah brings back information of users.

• Edited by mcassar Monday, June 29, 2015 1:47 AM

Hi Mcassar,

Before moving mailbox, you should synchronize user data between different AD forests first.

I recommend you refer to the following article

Prepare mailboxes for cross-forest move requests

To move a mailbox from an Exchange 2013 forest to another Exchange 2013 forest, the Exchange 2013 target forest must contain a valid mail-enabled user with a specified set of Active Directory attributes. If there is at least one Exchange 2013 Client Access server deployed in the forest, the forest is considered an Exchange 2013 forest.

To prepare for the mailbox move, you must create mail-enabled users with the required attributes in the target forest.

Best regards,

Hey there Niko,

Thanks for your reply, We are having issues running the prepare-moverequest script which is mentioned within the article.. as we are attempting to move a single user across, we have also tried to use the ADMT tool to migrate the information of one single user (a test user) I can confirm that the trust is working between both domains and that all the necessary ports are opened between the servers and the domain controllers.

I was under the impression that the prepare-moverequest script would create a new user with all the necessary details for the transfer, is this correct?