This is a guide for transitioning Exchange 2003 to 2010 in the same domain.
n.b (An Exchange migration is from one Active Directory forest to a different Active Directory forest.)
- Bring the Exchange organization to Exchange Native Mode.
- Upgrade all Exchange 2003 Servers to Exchange Server 2003 Service Pack 2.
- Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
- Upgrade at least one Global Catalog domain controller in each AD Site that will house Exchange Server to Windows Server 2003 SP2 or greater.
- Run ServerManagerCmd -i NET-Framework from 2008 R2 server.
- (only run if setup is not run by Schema, Enterprise and Domain Admin)Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
- Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema). ServerManagerCmd -i RSAT-ADDS
- Install Web Server role on the CAS server and any necessary prerequisites. (If additional Exchange servers are on the network)
- Set the Net.Tcp Port Sharing service to automatic
- Install the Office 2007 converter filter Pack http://go.microsoft.com/fwlink/?LinkId=123380
- Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate at the command line.)
- Install CAS server role servers and configure per 2010 design. (If required)
- Install Mailbox servers and configure Databases (DAG if needed)
- Install Hub Transport role and configure per 2010 design.
- Create public folder replicas on Exchange 2010 servers using shell. Run cd <Exchange Installation Path>\Scripts then run.\AddReplicatoPFRecursive.ps1 -TopPublicFolder \ -ServerToAdd Servername in Exchange Shell, or Exchange 2010 Public Folder tool.
- Transfer inbound and outbound mail traffic to the HT servers.
- Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
- Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
-
Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Powershell.
Indivdual users:New-MoveRequest -Identity “someuser@corp.local” -DomainController DC02 -TargetDatabase “Mailbox Database 01″
Entire mailboxes: .\MoveMailbox.ps1 -MailboxDatabase “SRV-01\First Storage Group\Mailbox Store (SRV-01)” -TargetDatabase “Mailbox Database” (note: ps1 scripts must be run from \Exchsvr\Scripts location in Management Shell)
- Run Get-MoveRequest –MoveStatus Completed | Remove-MoveRequest to remove Move requests otherwise mailboxes can’t be moved again.
-
Update Email address policy to Exchange 2010
Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} | Set-EmailAddressPolicy –IncludedRecipients AllRecipients
- Update Address Lists
Set-AddressList “All Users” -IncludedRecipients MailboxUsers
Set-AddressList “All Groups” -IncludedRecipients MailGroups
Set-AddressList “All Contacts” -IncludedRecipients MailContacts
Set-AddressList “Public Folders” -RecipientFilter { RecipientType -eq ‘PublicFolder’ }
Set-GlobalAddressList “Default Global Address List” -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq ‘user’ -or ObjectClass -eq ‘contact’ -or ObjectClass -eq ‘msExchSystemMailbox’ -or ObjectClass -eq ‘msExchDynamicDistributionList’ -or ObjectClass -eq ‘group’ -or ObjectClass -eq ‘publicFolder’))}
- Rehome Public Folder Hierarchy on new Exchange Server 2010 Admin Group.
- Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
- Delete Public and Private Information Stores from Exchange 2003 server(s).
-
Delete Routing Group Connectors to Exchange Server 2003.
Get-RoutingGroupConnector | Remove-RoutingGroupConnector
-
Delete Recipient Update Service agreements using ADSIEdit
“CN=Recipient Update Services,CN=Address Lists Container,CN=Commonname, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local”
- Uninstall all Exchange 2003 servers through add/remove programs







