Developing the Migration Documentation

Migration documentation is typically created during the testing or prototype phase of the project. Migration documentation, comprised of a combination of procedures and checklists, provides a roadmap of the Exchange Server 2003 migration. The documents might need updating after the initial or pilot implementation to more accurately reflect the migration process.

Server Migration Procedures

Server migration tasks should be decided on during a design and planning process. Detailed procedures associated with those tasks are then developed and confirmed during a prototype/testing phase. It is also important to validate the documents each time a server is rebuilt to ensure that critical steps are not left out. When complete, this information can save a great deal of time during the implementation.

TIP

Server migration procedures should be written in such a way so that even less- experienced resources are able to use the procedures for the actual migrations.

The procedures covered can include, but are not limited to, the following:

• Server hardware configuration details

• Service pack (SP) and hotfixes to install on each server

• Services (such as DNS and DHCP) to enable or disable (including any appropriate settings)

• Applications (for example, antivirus) to install and appropriate settings

• Security settings

• Steps required to migrate mail to the new server(s)

• Steps required to test the new configuration to ensure full functionality

• Steps required to remove old servers from production

Desktop Client Configuration Procedures

Desktop configurations might change during the migration to, the implementation of, or the configuration change of Exchange Server 2003. If the Outlook client is already in use, server configuration changes might affect only the Outlook profile. All changes and the change procedure should be documented to ensure that there is a uniform user experience after the implementation.

NOTE

The desktop configuration change process should be discussed in the design and planning phase.

Mail Migration Procedures

One of the most frequently identified messaging systems implementation goals is to migrate all the existing mail, contacts, mailing lists, calendar items, and more without losing any data. Developing complete and accurate messaging migration procedures during the testing phase helps migrate existing production messaging data and prevents data loss.

Checklists

The migration process, based on the amount of data that must be migrated , can often be a long process. It is very helpful to develop both high-level and detailed checklists to guide the migration process. High-level checklists determine the status of the migration at any given point in the process. Detailed checklists ensure that all steps are performed in a consistent manner. This is extremely important if the process is being repeated for multiple sites.

The following is an example of an Exchange Server 2003 server build checklist:

 Task:                                                                Initials Notes Verify BIOS and Firmware Revs Verify RAID Configuration Install Windows Server 2003 Enterprise Edition Configure Windows Server 2003 Enterprise Edition Install Security Patches Install Support Tools Install System Recovery Console Add Server to Domain Install Antivirus Install Exchange Server 2003 Enterprise Configure Exchange Install and Configure Backup Agent on Exchange Apply Rights For XX-Sysadmins Set up and Configure Smart UPS Sign off:                                                                Date: