I am having an issue migrating mailboxes from an Exchange 2003 server to Exchange 2010 in another forest. I've ran ADMT to start the migration, and am not ready to test the Exchange move.
The prepare-mailbox works fine. It's the move mail command that does not.
The commands I am running are:
$LocalCredentials = Get-Credential
$RemoteCredentials = Get-Credential
.\Prepare-MoveRequest.Ps1 -Identity test1 -RemoteForestDomainController dc.olddomain.com -RemoteForestCredential $RemoteCredentials -LocalForestDomainController dc.newdomain.com -LocalForestCredential $LocalCredentials -UseLocalObject -Verbose
New-MoveRequest -Identity test1 -TargetDatabase 'Mailbox Database 1' -remoteGlobalCatalog 'dc.olddomain.com' -remoteCredential $RemoteCredentials -TargetDeliveryDomain newdomain.com -RemoteLegacy -verbose
The error I get is:
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
......
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0xCA0313AC00000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 2344
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2012-12-26 19:35:36:467
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 45169 StoreEc: 0x977
Lid: 52465 StoreEc: 0x977
Lid: 60065
Lid: 33777 StoreEc: 0x977
Lid: 59805
Lid: 52209 StoreEc: 0x977
Lid: 56583
Lid: 52487 StoreEc: 0x977
Lid: 19778
Lid: 27970 StoreEc: 0x977
Lid: 17730
Lid: 25922 StoreEc: 0x977
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : BA3AEC32,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
+ PSComputerName : exchange.newdomain.com
Running in verbose mode shows that is fails when 'loading source mailbox info". I would assume it's on the Exchange 2003 server, and not the source domain controller.
Troubleshooting, I saw most people who've receiving this error were due to the FQDN or Netbios name not being resolved. I don't have this issue, as both domain names are in DNS Suffix for all NICS. I can ping vie both, no problem.
All accounts I am using are the domain Administrators accounts with proper access to exchange on both ends.
I don't see any other errors pointing to an issue.
Tom Drought