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