Cross-forest Mailbox Moves using the Exchange Management Console
Another great feature in the Exchange 2010 Management Console is that you now can do cross-forest mailbox moves using the new “New Move Request” wizard. To launch this wizard right-click a User Mailbox in the EMC, then select New Move Request in the context menu as shown in the figure below.
This brings up the wizard shown next. Here you can specify to which Exchange organization you want to move a mailbox.
Note
Before you can perform a cross-forest move, you must add the Exchange org in the target forest to the EMC. In addition, you must have the AD account of the source user mailbox migrated/replicated to the target forest using ILM or a similar tool. Yes doesn’t work like the Move-Mailbox cmdlet did in Exchange 2007, where the AD object would be created if it didn’t already exist.
- Henrik Walther
balasubramaniam.p Says:
April 20th, 2009 at 4:53 am
Dear Henrik
very good feature.Try to bring this option in exchange server 2007.
balasubramaniam.p Says:
April 20th, 2009 at 5:00 am
Dear Henrik
if we want to do the cross forest migration from 2003 to 2007.we have to use the powershell,it is very tought to do it.
Try to bring this option in exchange server 2007 console.it will be very to useful to
exchange administrator.
Brinkmann Says:
November 29th, 2009 at 3:18 am
Hi,
I have a problem with that feature.
When I try to move a mailbox to the another forest get an error:
“The operation couldn’t be performed because object ‘xxxxxxxxxxxxx…’ couldn’t be found on the target DC”
That object are a GUID wich I can’t find realy in the tartget and in the source forest.
Have you any idea, please
thanks
Brinkmann
Henrik Walther Says:
November 29th, 2009 at 5:32 am
Brinkmann,
Remember the target account requirements has changed in Exchange 2010:
1. msExchMalboxGUID needs to be migrated from source domain
2. Migrated user (in target domain) needs to be mailEnabled, with same email address as in source domain
3. Mailbox in source domain is deleted during migration process, and converted to mailEnabled user
4. New user has same msExchMalboxGUID (migrated) after mailbox in new domain is created
Henrik