I have to go to some company tomorrow to help with their migration from Exchange 2003 to 2010. I've done this a few times but I think that I may have some blagging to do if they choose the co-existence route.
I wrote this in preparation for my visit.
Exchange 2003 - 2010 migration
Planning and Install
1. Exchange Server 2010 Planning
a. Is Exchange 2003 running SP2. If not it must be upgraded.
b. Domain Functional level – must be 2003
c. Hardware and storage considerations
i. Run perfmon to find current IOPS requirement
d. Does the environment require roles at different sites or can all roles be on one server?
e. Exchange Server Deployment Assistant, or ExDeploy
f. DR considerations. DAGs require Windows 2008 R2 Enterprise
g. How many databases should be deployed for easy restoring?
h. Exchange Best practice analyser – run to determine existing problems
i. External access requirements:
i. Additional certificate needed. SAN certificate recommended with “mail”, “autodiscover” and “legacy”.
ii. How is OWA / ActiveSync published?
j. What version of Office is being used? Is there a requirement for public folders?
k. Archiving software – what needs to be done to move this to new server?
l. What SMTP devices (e.g. MFDs, backup alerts, etc) need to be reconfigured?
2. Windows 2008 R2 hotfixes
a. http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.141%29.aspx
3. Exchange 2010 Installation
a. Install the Windows RPC Over HTTP Proxy Component
b. Prerequisites can be installed by the Exchange 2010 installer if SP1 is bundled.
c. If external domain names are known they can be entered during installation, otherwise they should be entered in step 5
d. SP1 and SP2 and rollup hotfixes
e. Exchange best practice analyser – run again
f. Configure the Exchange 2010 certificate
i. Is there an internal CA available?
ii. Provision for a legacy URL (if option 1, below, is to be followed)
Option 1 – Co-existence
Both servers will run in tandem for the duration of the migration. More complicated route but allows external OWA for users on both servers except during the period when their mailbox is moved (move is offline).
4. Configure the client access server.
a. Enable Outlook anywhere on client access server
b. Set the Legacy URL on OWA
i. Set-OwaVirtualDirectory <CAS2010>\OWA* -Exchange2003Url https://legacy.contoso.com/exchange
1. Enable forms-based authentication on Exchange 2003
c. Change the OAB generation server to the new 2010 server and enable web based access
d. Install hotfix for ActiveSync
i. http://support.microsoft.com/?kbid=937031
5. Publish the old Exchange server via the legacy URL
a. Import the Exchange 2010 certificate into the Exchange 2003 server
i. Use this recently imported certificate in IIS on the 2003 server by replacing the old one
b. Arrange with DNS service provider to create an A record for the legacy URL, which should match the URL in 3.c.ii and 5.b. This can point to the same IP address if the publishing method allows this. E.g. ISA 2006.
c. Use firewall / ISA to publish the old Exchange server from the new external IP / legacy URL
d. Disable HTTP over RPC on any 2003 front end servers.
6. Use ISA / firewall to publish the new Exchange server from the old DNS record.
a. Users on both servers should now be able to reach their mailboxes via the old URL (and 2003 users should be able to use the legacy URL too).
Option 2 – Migration during maintenance window
The new Exchange server will be published for OWA and then all mailboxes can be moved to the new server. As soon as a user’s mailbox resides on the new server OWA will become available for him or her.
7. Use the existing external URL and publishing rule on the firewall / ISA to publish the new Exchange server.
a. The ECP sub site should also be published
b. Users on the Exchange 2003 server will now be unable to access OWA.
Migration Process
8. Once option 1 or 2 above is complete then the mailboxes can be moved using the Exchange 2010 console or shell.
a. Migration of mailboxes causes a large amount of logs and so disk space should be monitored.
9. If public folders are in use then they should be replicated to the new server.
a. .\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
Post Migration processes
10. Check public folders have finished replicating (get-publicfolderstatistics) move them to the new server:
a. .\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
b. Use Get-PublicFolder -recurse |fl name,replicas and Get-PublicFolder -recurse \non_ipm_subtree |fl name, replicas to ascertain whether migration is complete.
11. The public folder home server should be moved to the new server
12. Shared mailboxes can be converted to resource mailboxes
13. Uninstall Exchange 2003
a. If it is impossible to uninstall Exchange due to remaining replicas in the public folder database then it can removed using ADSIedit before proceeding.
14. Remove routing group connectors and the RUS using ADSIedit.
I wrote this in preparation for my visit.
Exchange 2003 - 2010 migration
Planning and Install
1. Exchange Server 2010 Planning
a. Is Exchange 2003 running SP2. If not it must be upgraded.
b. Domain Functional level – must be 2003
c. Hardware and storage considerations
i. Run perfmon to find current IOPS requirement
d. Does the environment require roles at different sites or can all roles be on one server?
e. Exchange Server Deployment Assistant, or ExDeploy
f. DR considerations. DAGs require Windows 2008 R2 Enterprise
g. How many databases should be deployed for easy restoring?
h. Exchange Best practice analyser – run to determine existing problems
i. External access requirements:
i. Additional certificate needed. SAN certificate recommended with “mail”, “autodiscover” and “legacy”.
ii. How is OWA / ActiveSync published?
j. What version of Office is being used? Is there a requirement for public folders?
k. Archiving software – what needs to be done to move this to new server?
l. What SMTP devices (e.g. MFDs, backup alerts, etc) need to be reconfigured?
2. Windows 2008 R2 hotfixes
a. http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.141%29.aspx
3. Exchange 2010 Installation
a. Install the Windows RPC Over HTTP Proxy Component
b. Prerequisites can be installed by the Exchange 2010 installer if SP1 is bundled.
c. If external domain names are known they can be entered during installation, otherwise they should be entered in step 5
d. SP1 and SP2 and rollup hotfixes
e. Exchange best practice analyser – run again
f. Configure the Exchange 2010 certificate
i. Is there an internal CA available?
ii. Provision for a legacy URL (if option 1, below, is to be followed)
Option 1 – Co-existence
Both servers will run in tandem for the duration of the migration. More complicated route but allows external OWA for users on both servers except during the period when their mailbox is moved (move is offline).
4. Configure the client access server.
a. Enable Outlook anywhere on client access server
b. Set the Legacy URL on OWA
i. Set-OwaVirtualDirectory <CAS2010>\OWA* -Exchange2003Url https://legacy.contoso.com/exchange
1. Enable forms-based authentication on Exchange 2003
c. Change the OAB generation server to the new 2010 server and enable web based access
d. Install hotfix for ActiveSync
i. http://support.microsoft.com/?kbid=937031
5. Publish the old Exchange server via the legacy URL
a. Import the Exchange 2010 certificate into the Exchange 2003 server
i. Use this recently imported certificate in IIS on the 2003 server by replacing the old one
b. Arrange with DNS service provider to create an A record for the legacy URL, which should match the URL in 3.c.ii and 5.b. This can point to the same IP address if the publishing method allows this. E.g. ISA 2006.
c. Use firewall / ISA to publish the old Exchange server from the new external IP / legacy URL
d. Disable HTTP over RPC on any 2003 front end servers.
6. Use ISA / firewall to publish the new Exchange server from the old DNS record.
a. Users on both servers should now be able to reach their mailboxes via the old URL (and 2003 users should be able to use the legacy URL too).
Option 2 – Migration during maintenance window
The new Exchange server will be published for OWA and then all mailboxes can be moved to the new server. As soon as a user’s mailbox resides on the new server OWA will become available for him or her.
7. Use the existing external URL and publishing rule on the firewall / ISA to publish the new Exchange server.
a. The ECP sub site should also be published
b. Users on the Exchange 2003 server will now be unable to access OWA.
Migration Process
8. Once option 1 or 2 above is complete then the mailboxes can be moved using the Exchange 2010 console or shell.
a. Migration of mailboxes causes a large amount of logs and so disk space should be monitored.
9. If public folders are in use then they should be replicated to the new server.
a. .\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
Post Migration processes
10. Check public folders have finished replicating (get-publicfolderstatistics) move them to the new server:
a. .\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
b. Use Get-PublicFolder -recurse |fl name,replicas and Get-PublicFolder -recurse \non_ipm_subtree |fl name, replicas to ascertain whether migration is complete.
11. The public folder home server should be moved to the new server
12. Shared mailboxes can be converted to resource mailboxes
13. Uninstall Exchange 2003
a. If it is impossible to uninstall Exchange due to remaining replicas in the public folder database then it can removed using ADSIedit before proceeding.
14. Remove routing group connectors and the RUS using ADSIedit.
Very nice post .You have planned it very clearly.It helped me a lot.Keep posting your experiences and plans.
ReplyDeleteVirtualization Technology