There are many steps to get groups and contacts over, here's some scripts and commands to get the basic attributes over
Contacts:
Export from source forest:
ldifde -f contacts.ldf -o "whenCreated, whenChanged, uSNCreated,uSNChanged, proxyAddresses, replicatedObjectVersion, objectGUID, showInAddressBook, dSCorePropagationData, replicationSignature, msExchALObjectVersion, msExchADCGlobalNames,
dLMemDefault, msExchPoliciesIncluded, memberOf" -r "(objectClass=contact)"
Import into target forest:
ldifde -k -i -f contacts.ldf -j C:\ -c "DC=oldforest,DC=local" "DC=newforest,DC=local"
Get-Recipient | Update-Recipient
-This command will use EAPs to then setup the e-mail addresses on the newly imported contacts
But this won't include group membership or e-mail addresses.
Groups:
Export groups script: http://izzy.org/scripts/Exchange/Migration/Export-GroupMembers.ps1
Import groups script: http://izzy.org/scripts/Exchange/Migration/Import-GroupMembers.ps1
Export groups SMTP addresses:
http://izzy.org/scripts/Exchange/Migration/Export-GroupsSMTP.ps1
Import group SMTP addresses: http://izzy.org/scripts/Exchange/Migration/Import-GroupsSMTP.ps1
The above scripts don't get any delivery restrictions, ownership\manager properties, permissions, and other settings.
You can export the delivery restrictions using these EMS cmdlets:
Get-DistributionGroup | Where-Object {$_.AcceptMessagesOnlyFromSendersOrMembers -ne $Null} | Select Alias, @{Name='AcceptMessagesOnlyFromSendersOrMembers';Expression={[string]::join(";", ($_.AcceptMessagesOnlyFromSendersOrMembers))}} | Export-Csv -NoType -encoding "unicode" GroupsAcceptFrom.csv
Get-DistributionGroup | Where-Object {$_.RejectMessagesFromSendersOrMembers -ne $Null} | Select Alias, @{Name='RejectMessagesFromSendersOrMembers';Expression={[string]::join(";", ($_.RejectMessagesFromSendersOrMembers))}} | Export-Csv -NoType -encoding "unicode" GroupsRejectFrom.csv
I do NOT recommend using PSTs to Export\Import your Mailbox data since this will break replies to previously received messages and meeting attendees. To prevent these issues you have to copy the LegacyExchangeDN from the source domain into an x500 address on
the new mailbox for the same user in the target domain. Exchange 2007 also support migrating the mailbox data across forest without taking the source mailbox database off-line. Using the Move Mailbox Wizard you can move one mailbox at a time or all of them
over a weekend.
Again, doing a cross forest migration is a complex process and VERY VERY error prone. So if you want to minimize downtime and issues I highly recommend getting professional assistance.
If you would like assistance with your migration please contact me to provide a statement of work and quote to assist in your migration.
Note: The scripts and code examples above are provided as-is with no support via forums or e-mail.
If this post helps to resolve your issue, please click the "Propose as Answer" If you find it helpful , mark it as helpful by clicking on "Vote as Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find
the answer faster. If you need an expert migration consultant to assist your organization feel free to contact me directly.
Jason Sherry | Blog |
Hire Me | Twitter: @JasonSherry
Microsoft Infrastructure Architect, MCSE: M, MCTIP, Microsoft Exchange MVP
