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