“Failed to set basic mailbox information, will retry in 60 seconds” in move-mailbox cross-org

Posted on by

When running Move-Mailbox in a cross-org scenario you get “Failed to set basic mailbox information, will retry in 60 seconds” 

The cause seems to be that the Mailbox Server and Move-Mailbox cmdlets are using different DCs. So making sure that both use the same DC will fix this error

Using a specific DC (on destination forest), with -DomainConrtoller & -GlobalCatalog switches

get-mailbox -DomainController ‘dcA.src.local’ -Credential $s -database ‘Server1\DatabaseA’ | move-mailbox -TargetDatabase ‘Server2\Database1’ -Identity ‘testMailbox1’ -SourceForestGlobalCatalog ‘dcA.src.local’ -GlobalCatalog ‘dc1.dest.local’ -DomainController ‘dc1.dest.local’ -NTAccountOU ‘OU=UsersOU, DC=dest, DC=local’ -MaxThreads 8 -SourceMailboxCleanupOptions DeleteSourceNTAccount -SourceForestCredential $s -TargetForestCredential $t -ReportFile “C:\Logs\migrationReport.xml”

Excluding specific DCs for Mailbox server role to use with -StaticExcludedDomainController

Set-ExchangeServer -identity Server2.dest.local -StaticExcludedDomainControllers:dc2.dest.local,dc3.dest.local.

Assuming that on destination forest exist 3 dcs: dc1, dc2, and dc3.

Another workarround is leave only one DC up and running, so replication will not be involved.

References:

http://support.microsoft.com/?scid=kb;en-us;298879&x=2&y=9

http://msexchangeteam.com/archive/2006/11/02/430289.aspx

1 thought on ““Failed to set basic mailbox information, will retry in 60 seconds” in move-mailbox cross-org”

  1. Thanks for this information.

    I’ve just started with my company wide AD & Exchange migration – for some reason I got the same error when I migrated my first mailbox over to the new exchange 2007 server (from a exchange 2007 server). But I had another problem where my first mailbox was created as a “linked mailbox”.

    I just removed the mailbox and moved the mailbox over again and it worked perfectly – just took awhile to update the alias & smtp address.

    My problem was due to a sluggish Exchange server – the Server was setup months ago and just sat there never been used…but after I’ve done the second mailbox-move it kicked itself into gear and now its working fine.

    Nice blog!
    Have a nice day….

    Reply ↓

Leave a comment