Exchange 2003 to Exchange 2010 cross-forest migration.

I have been using your Invoke-MoveRequest and this works perfectly in the LAB.
When this is run in LIVE the msExchMailboxGUID is not copied correctly.
If I view the msExchMailboxGUID in ADSIEdit the attribute does match in source and target when viewed in Hex, Octal, Decimal or Binary (the only ones you can Edit in manualty) but not the default Octet String. The value is different when viewed in Octet String.

The mailbox will not migrate due to this miss match.

Any advice is much appreciated!

Regards,
Matt

Thank you.

Thanks for your feedback, I`ll have a look into it and update the post when done

I was using your script and it’s a life-saver, but I had trouble understanding one variable, and had to figure it out on my own Microsoft documentation on Technet is very detailed, but a litle confusing regarding the “targetdeliverydomain” parameter and so on…

May I suggest you rename “Domain A” or “Domain” or “Mailbox Database A” and place some more meaningfull things, like:

#Custom variables, edit this section
$TargetDatabase = “Database in target domain”
$TargetDeliveryDomain = “source.com”
$TargetForest=”source.local”
$SourceForest=”target.local”
$SourceForestGlobalCatalog = “dc-01.source.local”
$SourceForestCredential = Get-Credential -Credential “source.local\SourceForestAdministrator”

#Connect to source forest to collect users to migrate
Connect-QADService -Service $SourceForest | Out-Null
$SourceForestUsersToMigrate = Get-QADUser -SearchRoot “source.local/Department A/Users”

… so people can make a little better difference between source local and public domain, and target source and public domain.

Maybe put a small drawing with for forest A and forest B with local names and public names of domains on it.

Anyway,

great script, really a life-saver

Thanx