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