Cross Org Mailbox Moves Using EMS

I am trying to move mailboxes (Cross Org) using EMS. I use the following:

$SourceCredential= Get-Credential

$TargetCredential= Get-Credential

Move-Mailbox -TargetDatabase "<Servername>\First Storage Group\Mailbox Database" -Identity <User> -GlobalCatalog <Servername> -SourceForestGlobalCatalog <Servername> -NTAccountOU "OU=TestOU, DC=Domain,DC=local" -SourceForestCredential $SourceCredential -TargetForestCredential $TargetCredential

The first thing that happens is a timeout for 60 seconds:

"Failed to set basic mailbox information, will retry in 60 seconds."

Message is cut off and I can't read the rest of it. Then, the mailbox moves successfully.

Second, the mailbox is a linked mailbox under Recipient Type Details instead of User Mailbox.

So my question(s)... How do I get them to move without the timeout and come in as User Mailboxes NOT Linked Mailboxes?

Thanks.
LVL 1
LCNWAsked:
Who is Participating?
 
FearNoMoreConnect With a Mentor Commented:
One of the reasons this happens is becuase there is an issue with the External Master Account Sid
Do you see event 9548 on the Exchange 2003 server?
Associated External Account can  cause this issue....I gather that you have read the following article
http://telnetport25.wordpress.com/2008/06/10/linked-mailbox-conversion-after-migration-in-exchange-2007/
 
0
 
FearNoMoreCommented:
First:
Force AD replication between DC's in both the Source as well as the Target forest
Restart the IS service on both the Source as well as Target forests
Now try running the command once again
If it still fails then try running the command with the -RetryInterval switch
eg:
Move-mailbox -identity <mailbox> -TargetDatabase <mailboxDatabase> -NTAccountOU
<OU> -SourceForestGlobalCatalog <sourceGC> -SourceForestCredential $cred
-RetryInterval 00:00:01
For the second part of your question
Using ADSIedit
For the user showing as Linked modify the user account attribute
"msExchRecipientTypeDetails" from a value of 2 to a value of 1
0
 
LCNWAuthor Commented:
I have read several blogs that warn of changing that property using ADSI. Plus, that doesn't explain why it is happening. I want to know what's causing this and how to prevent it.
0
 
LCNWAuthor Commented:
I have found a workaround, though I wish I could find an answer. I move the user using ADMT 3.1, then I create a mailbox for that account. Finally, I move the original mailbox with the -AllowMerge tag. This gets rid of both problems. I hope someone out there has an answer, I would really like to get to the root of the issue. I have researched accounts that may have the Associated External Account ticked and removed that variable. Still looking...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.