This Post is moved to itbigbang.com. Please click here to visit the GUI Script.
Please feel free to post your queries here.
Regret the Inconvenience. Thank you.
March 23, 2010
19 Comments »
RSS feed for comments on this post.
This Post is moved to itbigbang.com. Please click here to visit the GUI Script.
Please feel free to post your queries here.
Regret the Inconvenience. Thank you.
RSS feed for comments on this post.
Msexchangehelp 
what about the legacyexchangedn ? replying to emails needs this ? Thanks
Comment by Andrew — April 1, 2010 @ 10:04 am
I don’t find the move2exchange.ps1 download
What can i find it?
thanks
Comment by salva — April 7, 2010 @ 11:07 am
i get this error when running th script(i see that at the background powershell window) and nothing works(after prompt twice)
Exception setting “SelectedIndex”: “InvalidArgument=Value of ‘0’ is not valid for ‘SelectedIndex’.
Parameter name: SelectedIndex”
At C:\1\MovetoE14.Ps1:30 char:11
+ $SrcTrust. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
The Credential parameter must be used with the DomainName or Forest parameters.
+ CategoryInfo : InvalidArgument: (Microsoft.Excha…omainController:GetDomainController) [], ArgumentExc
eption
+ FullyQualifiedErrorId : 79FCEE63
Exception setting "SelectedIndex": "InvalidArgument=Value of '0' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex"
At C:\1\MovetoE14.Ps1:39 char:8
+ $SrcDC. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
The Credential parameter must be used with the DomainName or Forest parameters.
+ CategoryInfo : InvalidArgument: (Microsoft.Excha…omainController:GetDomainController) [], ArgumentExc
eption
+ FullyQualifiedErrorId : 79FCEE63
Exception setting "SelectedIndex": "InvalidArgument=Value of '0' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex"
At C:\1\MovetoE14.Ps1:48 char:8
+ $SrcGC. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
0
1
2
0
Failed to reconnect to Active Directory server DCR2.newdomain.corp. Make sure the server is available, and that you hav
e used the correct credentials.
+ CategoryInfo : NotSpecified: (:) [Get-User], ADTransientException
+ FullyQualifiedErrorId : 4C3E810B,Microsoft.Exchange.Management.RecipientTasks.GetUser
0
0
0
0
1
2
0
0
Comment by turbo — April 10, 2010 @ 8:17 pm
I have the same error. Have you found a solution for it?
Comment by Michael — July 25, 2010 @ 5:57 pm
This is awesome! Great job!!!
Comment by Geoff — May 18, 2010 @ 8:08 pm
This is by far one of the best script i have ever seen for moving mailbox cross forest using PS. Is there a script like this to move mailbox between Exchange 2007 cross forest to Exchange 2010? I can not seem to find any tool like this.
Comment by Davis Truong — May 21, 2010 @ 7:04 am
Hi I am trying to run this script however um getting errors on run and not filling in any of the fields in the gui box.
the script does not recognize parameters such as get-trust etc
Comment by Brian — May 26, 2010 @ 5:48 am
I got the same problem as Turbo…
Exception setting “SelectedIndex”: “InvalidArgument=Value of ‘0’ is not valid
or ‘SelectedIndex’.
Parameter name: SelectedIndex”
At C:\PrepareMoveRequest\movetoE14.ps1:30 char:11
+ $SrcTrust. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
The Credential parameter must be used with the DomainName or Forest parameters
+ CategoryInfo : InvalidArgument: (Microsoft.Excha…omainControl
ler:GetDomainController) [], ArgumentException
+ FullyQualifiedErrorId : 73D3EE63
Exception setting "SelectedIndex": "InvalidArgument=Value of '0' is not valid
or 'SelectedIndex'.
Parameter name: SelectedIndex"
At C:\PrepareMoveRequest\movetoE14.ps1:39 char:8
+ $SrcDC. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
The Credential parameter must be used with the DomainName or Forest parameters
+ CategoryInfo : InvalidArgument: (Microsoft.Excha…omainControl
ler:GetDomainController) [], ArgumentException
+ FullyQualifiedErrorId : 73D3EE63
Exception setting "SelectedIndex": "InvalidArgument=Value of '0' is not valid
or 'SelectedIndex'.
Parameter name: SelectedIndex"
At C:\PrepareMoveRequest\movetoE14.ps1:48 char:8
+ $SrcGC. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
Comment by Markus — July 30, 2010 @ 2:25 pm
I got the same problem…
Exception setting “SelectedIndex”: “InvalidArgument=Value of ‘0’ is not valid
or ‘SelectedIndex’.
Parameter name: SelectedIndex”
At C:\PrepareMoveRequest\movetoE14.ps1:30 char:11
+ $SrcTrust. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
The Credential parameter must be used with the DomainName or Forest parameters
+ CategoryInfo : InvalidArgument: (Microsoft.Excha…omainControl
ler:GetDomainController) [], ArgumentException
+ FullyQualifiedErrorId : 73D3EE63
Exception setting "SelectedIndex": "InvalidArgument=Value of '0' is not valid
or 'SelectedIndex'.
Parameter name: SelectedIndex"
At C:\PrepareMoveRequest\movetoE14.ps1:39 char:8
+ $SrcDC. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
The Credential parameter must be used with the DomainName or Forest parameters
+ CategoryInfo : InvalidArgument: (Microsoft.Excha…omainControl
ler:GetDomainController) [], ArgumentException
+ FullyQualifiedErrorId : 73D3EE63
Exception setting "SelectedIndex": "InvalidArgument=Value of '0' is not valid
or 'SelectedIndex'.
Parameter name: SelectedIndex"
At C:\PrepareMoveRequest\movetoE14.ps1:48 char:8
+ $SrcGC. <<<< SelectedIndex = 0
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
Comment by Markus — July 30, 2010 @ 2:26 pm
I’m getting the same problem too, it’s as if it can’t see the source domain even though the ADMT works fine.
Comment by Mark — July 30, 2010 @ 4:34 pm
Fixed it! You can try this however I cannot guarantee success. I’m also having a few other issues but this may work for you, it did for me in the lab environment.
First I downloaded powergui. This isn’t necessary, any text editor would do, however powergui has some intellisense to the the scripting.
Find the line:
Get-Trust | ForEach-Object{$SrcTrust.Items.Add($_.Name)}
Change it to:
Get-Trust -DomainName $env:userdomain.”local” | ForEach-Object{$SrcTrust.Items.Add($_.Name)}
Now you may or may not need the “.local” it all depends on your domain suffix. You may even try it without the “.local”. Adding this allowed the program to find the GC and the DC properly and list the mailboxes.
However the next two, Organization units and exchange server, do not show up. (you may also get some syntax errors here and there as well before the gui pops up.) I simply typed in the exchange server and let the OU go. It listed all my mailboxes/users in a flat list regardless of ou.
I picked two mailboxes, picked my OU and exchange store (target info always worked fine) and clicked “Move Mailboxes”. Everything went just fine.
Hope that helps.
As far as the errors for exchange server name and OU, it appears it doesn’t keep the credentials and the cmdlets don’t have the ability to assign credentials as far as I can tell. Perhaps someone has a fix?
Comment by Mark — July 30, 2010 @ 9:06 pm
Yes, But is the source mailbox automatically deleted as part of this process. I ran into an issue today where a colleague ran this script and had permission issues on the target account. It was unable to complete the move-mailbox request AND it deleted the source mailbox. He had to restore the mailbox from backup. Is there a way to remove this portion from the script?
Comment by Lou — August 12, 2010 @ 7:33 pm
I would really recko to use a 3rd party tool like http://www.priasoft.com/products-exchange-migration-mailbox.aspx that supports 5.5, 2000, 2003, and 2007 direct to Exchange 2000, 2003, 2007, and 2010 and deals with all this and moves way faster than the native tools. + you get support!! 🙂
Comment by CJ — August 3, 2010 @ 9:52 pm
I am having the same error, tried the suggested fix but no luck! Has anyone else have any other input?
also, what’s the purpose to download the “Prepare-MoveRequest.Ps1” is it’s not listed as been used here? Or is it use by the GUI tool?
Thanks
Comment by David — August 22, 2010 @ 12:59 am
Hi, first of all thanks for this great tutorial.
I have a problem whith my environment, I just have migrated users in cross forest from server 2003 and exchange 2003 to server 2008 r2 and exchange 2010, but my target forest has two child domains:
Parent domain:
Contoso.com
Child domain:
Branch1.contoso.com
Branch2.contoso.com
Exchange 2010 is member of contoso.com and the users are in child domain.
The user’s migration was fine, but when I try to migrate the mailbox’s I got an error.
When I run enable-mailuser it shows that the user didn´t find it in the domain controller of the parent domain.
The question is: is it possible to add a parameter at the script in order to find the user in the child domain controller?
Is it not possible, how can I do the mailbox migration of users?
Comment by Juan Roja — September 16, 2010 @ 2:27 pm
It doesn’t appear that the MovetoE14.Ps1 script is available at the link provided. Where can we get it?
Comment by Ly — October 14, 2010 @ 7:04 pm
Where is the script?
Comment by Joe — July 26, 2012 @ 5:10 pm
Joe Please find it here
http://www.itbigbang.com/gui-interface-for-exchange-2003-to-exchange-2010-cross-forest-move-mailbox-using-powershell/
Sorry for inconvenience.
Comment by Sathish Kumar Elango — November 22, 2012 @ 4:39 am
Hi all please find the scripts below
http://www.itbigbang.com/gui-interface-for-exchange-2003-to-exchange-2010-cross-forest-move-mailbox-using-powershell/
Comment by Sathish Kumar Elango — November 22, 2012 @ 4:36 am