Exchange 2003 upgrade to Exchange 2007

Migrating Exchange 2003 to Exchange 2007 Exchange 2007 has been published for some time, and the new version adds a lot of practical new features, such as Exchange 2007 with encrypted messaging, support for push mail to mobile devices, and more. While many users are still using Exchange 2003 and want to use the new features of Exchange 2007, it is necessary to consider how to safely migrate mailbox data to Exchange2007. Here's a description of how to migrate Exchange 2003 data to Exchange 2007.

Prerequisite conditions

1.Exchange organization is set to native mode.

2.Exchange 2000 Installation Sp3,exchange 2003 installation SP2

3. Components not supported by Exchange 2007:

Novell GroupWise Connector (Exchange 2003 Service)

Microsoft Mobile Information Server (Exchange Service)

Instant Messaging Service (Exchange service)

Exchange Chat Service (Exchange service)

Exchange Conferencing Server (Exchange Service)

Key Management Service (Exchange service)

Cc:mail connector (Exchange Service)

MS Mail Connector (Exchange Service)

4. DCs with the schema master role and all GCs run in Windows 2003 SP1.

5.AD Domain elevated to maximum

6. If you are unsure of the installation conditions for Exchange 2007, you can use EXBPA detection.

Preparing for AD

1.cmd-setup.com/preparelegacyexchangepermissions

In order for the Recipient Update Service to function correctly (see Exchange 2007 Help)

2.cmd-setup.com/prepareschema

Connect to the DC schema master, import the LDAP file to update the schema

3.cmd-setup.com/preparead

Create Exchange Universal Security Groups in a domain (USGs)

Note: If you run 3 first, then 1 and 2 will run automatically

Preparing the domain and preparing all domains

1.cmd-setup.com/preparedomain

2.cmd-setup.com/preparealldomains

For Exchnage,exchange organization administrators on DCs, authorize users, and Exchange mailbox administrators set permissions. Create an Exchange System Object container (if it does not exist), within this container for the Exchnage,exchange organization Administrator, authorize the user to set permissions, and create a new domain global group under the name of the Exchange installation domain server. Add this Exchange install Domain server to Exchange USG.

Installing Exchange 2007 Software Requirements

1.Microsoft. NET Framework Version 2.0

2.Microsoft Management Console (MMC) 3.0

3.Windows PowerShell V1.0

Installing Exchange 2007 Windows Component requirements

1. Mailbox Server-enable Network COM + access;iis;www Service

Http://support.microsoft.com/kb/904639/en-us

Http://support.microsoft.com/kb/918980/en-us

2. Client Access server-www SERVICE;RPC over HTTP Proxy Windows networking Component (if you want to use Outlook Anywhere); ASP.net v2.0

3. Hub Transport server-no additional Windows components are required, be careful not to install SMTP and NNTP services

Install Exchange 2007 (omitted)

Complete deployment

Open the Exchange Management Console and click the Microsoft Exchange node to complete the deployment with detailed explanations and steps for each deployment.

End to end tasks

Ditto

Global Settings

Because global settings are stored in AD, they are automatically transferred to Exchange 2007. (Recipient policy, Internet Message format, SMTP connector, Exchange delegated permissions)

Note: When Exchange 2007 is in the original Exchange organization, any organization-level settings must be managed through the Exchange 2007 management tool.

Copy public Folder

As you know, you don't need public folders in Exchange 2007, and if you don't need the previous folder data, and the client is all Outlook 2007, you can delete the utility database.

Note: In previous versions, free/busy information was stored in public Folder, updated every 15 minutes, and in Exchange 2007, this information is stored in the user's mailbox and updated immediately. However, this feature is only available to Outlook 2007. You do not need to replicate free/busy information, and this information is replicated automatically when you deploy Exchange 2007 in an Exchange 2000/2003 environment.

We use ESM to copy public folder data for Exchange 2000/2003 to Exchange 2007.

Public Folder Properties-Replication tab-Add Exchange 2007 server

When the replication is complete, remove the Exchange 2000/2003 Server from the replication list. (determines that clients have access to public folder data, such as free/busy information, Offline address book)

To point an Internet client to a client Access server

Move Exchange 2000/2003 mailboxes to Exchange 2007

There are 2 ways to move mailboxes: The Exchange Management Console and the shell. Below, we move mailboxes through the Exchange Management Console.

Open the recipient Configuration node-mailbox, select the user's mailbox, click "Move Mailbox" in the action area, and follow the wizard step-by-step. (only 4 mailboxes can be moved at a time)

Redirect Inbound messages to Exchange 2007

Delete Exchange 2000/2003

1. Specify that RUS is an Exchange 2007 server (otherwise the installer will not allow Exchange 2000/2003 to be deleted)

2. Remove Exchange 2000/2003 through Add/Remove Programs

Note: Microsoft will release a hotfix to prevent Rus from being assigned to Exchange 2007, and it is recommended to remove RUS objects by ADSIEdit.