| In this phase, existing mail accounts and messages | | | | or modify existing migration scripts. All scripts for |
| are migrated from the existing messaging | | | | managing batch processes must be completed and |
| environment to the Microsoft Exchange 2003 | | | | tested prior to |
| environment. Your migration strategy must be | | | | ------------------Choosing Full or Limited Migration |
| executed in a manner that is transparent and that | | | | Accounts to migrate can be defined based on |
| has the minimum possible impact on your current | | | | business rules (for example, all mail accounts in good |
| e-mail users.To accomplish these goals, an effective | | | | standing or priority accounts requiring early access to |
| migration strategy and appropriate migration tools | | | | features not offered in the exiting mail system).If |
| must be designed and implemented. They must | | | | you are not going to migrate the entire population at |
| address all aspects of system migration, including | | | | one time, there are certain considerations you need |
| networking, external interfaces, account | | | | to plan for. For limited migration, you must configure |
| synchronization, management systems, and parallel | | | | the Microsoft Exchange 2003 system for POP proxy |
| operations.This chapter contains the following | | | | in order to retrieve mail from the legacy system for |
| sections:Developing a Migration StrategyPreparing the | | | | unmigrated accounts and mailboxes. The architecture |
| Migration PlanUsing Migration UtilitiesTips for a | | | | must also account for SMTP relay during Proxy mode |
| Successful MigrationRefer to the Microsoft Exchange | | | | in order to deliver appropriate mail to the legacy |
| 2003 Migration Guide for complete information on | | | | system as well as to Microsoft Exchange 2003.The |
| migration.Developing a Migration Strategy | | | | method of migrating account data must be identified |
| The typical site where Microsoft Exchange 2003 is | | | | and tested. Before the limited account migration can |
| installed has an existing mail system that provides | | | | occur, a back-out plan, migration quality assurance, |
| messaging services to its users. Migration is the act | | | | and certification of migration must be resolved and |
| of moving or copying the data for all users from the | | | | validated by testing.In many instances, new |
| legacy (existing) system to the Microsoft Exchange | | | | subscribers to mail service at the customer site are |
| 2003 system. Migration is performed so that all | | | | added to the Microsoft Exchange 2003 system |
| customers can be serviced by the Microsoft | | | | before migrated accounts from the legacy system. |
| Exchange 2003 system, not simply those new | | | | The benefits of handling new registrations in |
| subscribers following the installation of Microsoft | | | | Microsoft Exchange 2003 are that you may be able |
| Exchange 2003.Migration is the most complex facet | | | | to:Offer differentiated service immediately.Introduce |
| of any deployment project. Even though this | | | | Microsoft Exchange 2003 at a measured pace.Ensure |
| document provides a framework to follow for | | | | that no more users are added to an obsolete |
| migration, no two migrations are exactly alike, due to | | | | system.Resuming Service |
| the differences in each site's legacy mail system and | | | | Once migration is completed, accounts are |
| its integrated systems and procedures. A successful | | | | automatically switched from Proxy mode to active |
| migration depends upon accurately identifying all | | | | status. Users regain access to their mailboxes and all |
| unique aspects of the system that are to be | | | | messages that were deferred during migration are |
| duplicated in Microsoft Exchange and then duplicating | | | | delivered to their intended recipients. In addition, you |
| these conditions through development and testing | | | | must move operations entirely to the Microsoft |
| prior to the actual physical migration.The principal | | | | Exchange 2003 system and deactivate the legacy |
| issues of concern in any migration to a new mail | | | | system.A burn-in period should be identified, over |
| service are data integrity and transparent cutover to | | | | which the Microsoft Exchange 2003 system must be |
| production. Data integrity guarantees that all mail | | | | closely monitored for error conditions.Using Migration |
| accounts, stored messages, and associated personal | | | | Utilities |
| information and preferences (for example, address | | | | There are multiple methods for the combined |
| books, passwords, and so forth) are accurately | | | | migration of accounts and mailboxes. One method is |
| retained in the new mail system. Transparent cutover | | | | to transfer all accounts in a single migration. Then, |
| to production means that the transition is handled | | | | mailboxes can be transferred in batches. Another |
| quickly, cleanly, and with no disruption to the | | | | method is to transfer a batch of accounts, then |
| end-user experience.In typical migrations, the total | | | | transfer a batch of corresponding mailboxes, and so |
| amount of time required for a successful transition is | | | | on.Utilities that support the chosen strategy must |
| a function of system complexity. Both the total | | | | then be developed and tested. These tests should |
| number of mail accounts and the total number of | | | | include timing of the execution of these utilities.This |
| stored messages are significant factors. In addition, | | | | phase involves the building of the migration utilities |
| migration time can be affected by system and | | | | themselves and must include the design, |
| site-specific issues.Any migration strategy must | | | | development, and testing of the migration utilities |
| address:Migrating accountsMigrating mailboxesMigrating | | | | that are to be used to migrate the mail from the |
| Accounts | | | | existing system to the newly implemented Microsoft |
| This migration involves all of the information that | | | | Exchange 2003 system. New tools have to be built |
| uniquely identifies and describes a user, including | | | | very often because of the different source mail |
| class-of-service data that defines the service for | | | | systems that can be in existence.Microsoft Exchange |
| which users are subscribed. Account data must be | | | | 2003 offers automated migration tools designed to |
| placed in the Microsoft Exchange 2003 system | | | | streamline the process of moving your service, |
| before message data. The first task is therefore to | | | | including built-in tools for services using Sendmail and |
| collect and transfer account data from the legacy | | | | Software.com's Post.Office. These flexible, modular, |
| system and then transfer it to the Microsoft | | | | and customizable tools are Perl scripts that handle the |
| Exchange 2003 system.If your legacy system has | | | | export of directory, mailbox, and user information |
| domains and organizational units, you must prepare to | | | | from these other systems to files in Microsoft |
| migrate these also.Migrating Mailboxes | | | | Exchange 2003-readable format (based on LDIF), |
| This migration involves message data--the actual | | | | which are then imported into Microsoft Exchange |
| messages to be migrated that belong to the user. | | | | 2003. These tools enable you to migrate all accounts |
| The mailbox is simply a collection of the messages | | | | at once or as incremental blocks of users. When |
| belonging to a particular account.Preparing the | | | | migrating from a different mail system such as |
| Migration Plan | | | | Netscape Messaging Server or SIMS, Microsoft |
| Migration involves significant planning, more so than | | | | Exchange 2003's proxy features and robust export |
| any other deployment task. This planning is necessary | | | | command set provide a solid foundation for rapid |
| because the activity is exposed to existing users and | | | | development of custom export scripts.Tips for a |
| will, in most cases, be the initial experience that users | | | | Successful Migration |
| have of the new system. It is very important to plan | | | | With the completion of the migration tests, the only |
| for every eventuality in order to avoid problems | | | | anticipated impact will be caused by the difference in |
| during the migration.Refer to Appendix A for | | | | functionality between mail systems. Once the |
| information on how to obtain a sample migration | | | | migration of accounts has started, the target |
| plan.Migration is 95 percent planning and 5 percent | | | | production environment becomes the production |
| execution. A multitude of factors that must be | | | | environment.The migration procedure involves these |
| considered in order for a migration to succeed.The | | | | discrete steps:Setting up Microsoft Exchange 2003 in |
| Migration Plan provides a detailed, step-by-step | | | | Proxy modeChanging the MX recordIdentifying |
| procedure for migrating accounts and mailboxes to | | | | accounts to be migratedExtracting account |
| Microsoft Exchange 2003. The deployment team | | | | informationCreating accounts in Microsoft Exchange |
| should make several dry runs of this plan, with each | | | | 2003Migrating messagesSetting Up Microsoft |
| dry run resulting in a subsequent refinement of the | | | | Exchange 2003 in Proxy Mode |
| plan.Any migration plan should address these | | | | Microsoft Exchange must be configured for Proxy |
| considerations:Ensuring systems readinessCoordinating | | | | mode prior to activating the system. The proxy |
| with other groups and identifying | | | | configuration permits the relay of message and |
| dependenciesVerifying software installation and | | | | service requests to the legacy system until the full |
| configurationSetting up the test systemProviding | | | | migration has been achieved.In Proxy mode, all |
| provisioning connectivityTesting the migrationChoosing | | | | incoming mail is directed to Microsoft Exchange 2003. |
| full or limited migrationResuming serviceEnsuring | | | | If the mail is for a user that does not have an |
| Systems Readiness | | | | Microsoft Exchange account, the mail is relayed to |
| All systems to be tested must be ready and | | | | the legacy system for delivery. If a user attempts to |
| operational before testing begins. In addition | | | | retrieve mail, but the user's mailbox is not yet located |
| networks must be implemented as defined in the | | | | on the Microsoft Exchange 2003 system, the POP |
| architecture design (see Chapter 2).For each original | | | | server will connect to the legacy system and will |
| e-mail system, separate IP settings (each with unique | | | | retrieve the mail from the legacy mailbox |
| "A" records in the DNS) must be established for the | | | | location.Changing the MX Record |
| following:Host Address This is the permanent IP | | | | In order for mail to reach the Microsoft Exchange |
| assignment for the host. | | | | 2003 system (instead of the legacy system), you |
| Service Address This is the address that is used by | | | | must change the MX record in the DNS for the mail |
| all e-mail clients for a service. The Service Address | | | | domain of the site, so that traffic is directed to |
| will be re-assigned to Microsoft Exchange at the time | | | | Microsoft Exchange 2003.With all of the mail directed |
| of account migration. | | | | to Microsoft Exchange, you can begin to burn-in the |
| Service Proxy Address There must be a Service | | | | system with live loads and become accustomed to |
| Proxy Address for each Service Address. The IP | | | | operations administration even if there is no account |
| number used for any Service Proxy Address will | | | | data in the system. However, as soon as the system |
| match its respective Service Address. The Service | | | | is activated, accounts are provisioned directly into |
| Proxy Address will be used for proxy targeting | | | | Microsoft Exchange |
| where proxy is used on the Microsoft Exchange | | | | ------------Note: This step can take a few hours to be |
| system. These can be de-assigned after all migrations | | | | propagated over the |
| are complete and when it is determined that a revert | | | | -----------------Identifying Accounts to Be Migrated |
| procedure is not required.Coordinating with Other | | | | The first step in migration is to determine which |
| Groups and Identifying Dependencies | | | | existing mail accounts will move to the Microsoft |
| Since any migration touches upon many aspects of | | | | Exchange 2003 system. Accounts to migrate can be |
| a company's operations, make sure you coordinate | | | | defined based on business rules (for example, all mail |
| the migration with all affected groups and identify | | | | accounts in good standing, or priority accounts |
| dependencies--that is, determining the order in which | | | | requiring early access to features not offered in the |
| systems should be migrated.Verifying Software | | | | existing mail system).Extracting Account Information |
| Installation and Configuration | | | | After defining the accounts to migrate, the next |
| In addition to installing Microsoft Exchange 2003 (see | | | | step is to extract account information from the |
| Chapter 3) and verifying that all components | | | | existing mail system. Using the target account list, |
| inter-operate, you must set correct Microsoft | | | | account information is exported into a file in LDAP |
| Exchange environment settings for the root user. | | | | Data Interchange Format (LDIF). The standard LDIF |
| These include the correct $PATH, | | | | format permits the importing of account information |
| $LD_LIBARARY_PATH, and $Microsoft Exchange | | | | from any existing mail system to an Microsoft |
| settings in order to access the Microsoft Exchange | | | | Exchange system. The scripts used here can be |
| migration tools.Setting Up the Test System | | | | customized to handle any situation.Creating Accounts |
| To validate a migration plan, the test system should | | | | in Microsoft Exchange 2003 |
| have the capacity of production systems, including | | | | Next, accounts are created in the Microsoft |
| the proper storage volume configuration and failover | | | | Exchange directory based on the account information |
| configuration (service continuity). The test system | | | | described in the LDIF file. As accounts are created, |
| must have Internet connectivity, as Proxy mode | | | | they are placed in Proxy mode, causing mail delivery |
| operations cannot be tested without this.Aside from | | | | to and access from unmigrated accounts to be |
| equipment that mimics the production system, test | | | | passed directly through to the old mail system, thus |
| driver machines must also be available to power the | | | | ensuring continuous service to end users. During this |
| migration and capacity tests. The test drivers must | | | | phase, if a user logs in and supplies an unknown |
| be configured with migration utilities as well as with | | | | username, the Microsoft Exchange POP server |
| mail clients or other test utilities for accessing and | | | | connects to the current e-mail system.Migrating |
| sending mail.At least one test host is required for | | | | Messages |
| migration testing; this host acts as a surrogate for | | | | The last phase of migration involves moving mail |
| the actual online e-mail hosts and holds all mailbox | | | | messages from the existing mail system to the |
| data required for testing.Providing Provisioning | | | | Microsoft Exchange system. Message migration may |
| Connectivity | | | | occur either as separate files or as a single, |
| The provisioning interface must be validated before | | | | concatenated file. However, some customization is |
| migration can occur. C API procedures should be | | | | typically required, since the way a message is stored |
| tested to ensure that modifications performed on | | | | in the Message Store Server (MSS) can differ from |
| the ISD are successful and are propagated to the | | | | the standard mail format. This phase requires new |
| provisioning database. The Perl API set for batch | | | | accounts to run in Maintenance mode, during which |
| account migration also must be tested. Last, | | | | time these mailboxes are unavailable. For this reason, |
| administrative routines in the provisioning system or | | | | message migration is typically performed in small |
| ISD must be validated.This testing is performed in a | | | | increments during off-peak hours.Exchange Migration |
| dual provisioning environment. The purpose of dual | | | | plan for moving forward:Perform Due Diligence on |
| provisioning is to ensure the ability to revert to the | | | | your network via Remote Terminal Service ( Next |
| legacy mail system in the event that the new mail | | | | Week) |
| system in not successful.For provisioning, automatic | | | | Identify existing components - users, groups, login |
| mailbox creation must be tested. Zero-length | | | | variables |
| mailboxes are typically not migrated; rather, they are | | | | Document proposed AD structure |
| turned on in Microsoft Exchange 2003. The first time | | | | Project kickoff meeting (Friday) |
| mail is received or checked, the mailbox can be | | | | Install Windows Server 2003 (Friday Night) |
| created. A large test database (representing the | | | | Install Active Directory (Friday Night) |
| volume of anticipated accounts) must be | | | | Configure, Patch and Connect (Friday Night) |
| test-migrated to ensure that the procedure works | | | | Review Event Log, resolve any errors (Friday Night) |
| and that the destination ISD database can handle it.If | | | | Connect AD environment to existing Windows 2000 |
| possible, you should identify a group of "friendly" | | | | (Friday Night) |
| users willing to assist in identifying any problems or | | | | Identify existing printers (Saturday) |
| errorsTesting the Migration | | | | Identify existing components in Exchange (Saturday) |
| Before the migration can occur, comprehensive | | | | |
| testing on the production system must be completed. | | | | Build Exchange, configure, patch(Saturday) |
| Migration test activities are "non-intrusive" to the | | | | Install and configure virus software,Spam solution |
| existing mail system and are conducted from a | | | | and Fax Software(Saturday) |
| separate system using actual user account | | | | Configure OWA in DMZ(Saturday) |
| information and a test copy of the production user | | | | Verify Installation (Saturday) |
| data.The procedures for extracting account data | | | | Perform Mailbox Move (Saturday) |
| from the legacy system must be tested. The | | | | Install Outlook 2003 on all desktops. (Saturday - |
| method and utilities to load these accounts into the | | | | Sunday) |
| ISD must be validated through testing. Each class of | | | | Review Event Log, resolve any errors (Sunday) |
| service must be included, as well as each combination | | | | Setup Test workstation/perform testing (Sunday) |
| of account attributes, such as forwarding, aliases, and | | | | On-Site to handle any issues with the migration |
| vacation replies.In addition, the process of moving | | | | (Monday)The above steps are only an estimate of |
| mailboxes to the Microsoft Exchange 2003 system | | | | work needed to be perform a successful migration. |
| must be tested. This process includes the method of | | | | After we perform the Due Diligence Intercore will |
| suspending the account, the physical transfer of | | | | have a more definite outline in MS Project to fully |
| messages and attachments, and the return of the | | | | detail the breadth of work needed to perform the |
| account to active status.You should make any | | | | migration . This Due Diligence will identify issues that |
| possible configuration changes to prevent network or | | | | we can resolve before the migration is |
| system loading. In addition, you must establish any | | | | performed.InterCore Technologies, LLC opened it's |
| special network, host, or storage accommodations | | | | doors in May of 1996. Our mission: To Provide a high |
| that may be required for testing. A special network | | | | level of computer consulting services using the most |
| configuration may be required to prevent traffic | | | | experienced engineers at fair prices. We believe in |
| complications introduced by migration testing. Another | | | | using a Business Value approach to every aspect of |
| solution may involve localization of the original mailbox | | | | computer consulting. This provides our clients with |
| storage to the Microsoft Exchange 2003 | | | | the most cost effective solutions. We help our clients |
| ----------------Note: Depending on the particulars of a | | | | get more with their current technology investment. |
| given migration, you may need to create new scripts | | | | |