Chapter 2. Planning, Prototyping, Migrating, and Deploying Exchange Server 2003

IN THIS CHAPTER

• Initiation, Planning, Testing, and Implementation: The Four Phases to the Upgrade

• Initiation Phase: Defining the Scope and Goals

• Initiation Phase: Creating the Statement of Work

• Planning Phase: Discovery

• Planning Phase: Creating the Design Document

• Creating the Migration Document

• The Prototype Phase

• The Testing Phase: Validating the Plan to a Limited Number of Users

• The Implementation

• Best Practices

Messaging has evolved from an alternative to " snail mail" to an intricate communications and information storage environment. Exchange and Outlook users rely on it for formal and informal communications, keeping track of appointments, storing addresses and phone numbers , and (it's been said) receiving stock quotes, health tips, and urban myths. These tools are also available remotely in most environments, making them even more important at keeping the mobile professional productive and connected to his or her world.

It has become such a critical tool that the upgrade process should not be taken lightly. Although an upgrade from Exchange 5.5 or Exchange 2000 might at first appear to be a simple process, its success relies on your understanding of current issues with the messaging environment, defining both the objectives of the upgrade, and its potential effects on the user community. Adding more features and complexity to the messaging "ecosystem" might not result in ecstatic users, but reducing spam and the resulting impact on in-boxes might more than justify the cost of the upgrade. Reducing the number of milliseconds it takes to send an email probably won't get noticed, but being able to guarantee access to email anywhere and anytime should. An enthusiastic user community tends to generate support and momentum for projects, which extend the functionality of the messaging system.

Important decisions include whether the entire network operating system (NOS) needs to be upgraded (if Active Directory is not yet in place) or only a subset of it, and what other infrastructure components need to be changed or replaced .

The examples used in this chapter assume that the environments being migrated are primarily based on Exchange v5.5 or Exchange 2000, and except where noted that Active Directory is already in place. The same process can be applied to other messaging migration projects, such as GroupWise or Notes. The migration process is covered in detail in Chapters 14, "Migrating from NT4 to Windows Server 2003"; 15, "Migrating from Exchange v5.5 to Exchange Server 2003"; and 16, "Migrating from Exchange 2000 to Exchange Server 2003."