Chapter 5 - Upgrading Exchange Server 5.5 to Exchange 2000 Server

Chapter 5 - Upgrading Exchange Serv...

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Updated : June 14, 2001

Deployment Guide

Abstract

Microsoft® Exchange Server 5.5 Service Pack 3 can be directly upgraded to Microsoft Exchange 2000 Server. This chapter outlines the steps that you need to perform to achieve this. After completing these steps, you will have upgraded one of your mailbox servers to Exchange 2000. You will also be ready to perform any further configuration steps, such as migrating mailboxes, public folders, or connectors to this new server running Exchange 2000.

Introduction

In the Deployment Chapter 4, Installing Exchange 2000 Server, you looked at what you should do if you are just installing Microsoft® Exchange 2000 Server on a standard server running Microsoft Windows® 2000 Server. But what if you already have servers running Microsoft Exchange Server 5.5 and you want to upgrade them to Exchange 2000? This chapter walks you through the steps you should perform to complete a successful upgrade from Exchange 5.5 Service Pack 3 (SP3) to Exchange 2000.

This chapter also includes the steps necessary to ensure that you can roll back from a failed upgrade, along with a link to further information about overcoming an unsuccessful upgrade. However, if you use an account with the proper permissions and perform the preparatory steps described in this chapter, you should not have to restore a server in this manner.

Chapter Start Point

The start point to this chapter is an existing Microsoft Windows® 2000 Server organization with one or more servers running Exchange 5.5 Service Pack 3 that you intend to upgrade to Exchange 2000. Upgrading is only possible with servers that meet this specification. Previous releases of Exchange can only be migrated to Exchange 2000. Alternatively, you can upgrade Microsoft Exchange Server version 4.0 or 5.0 to Exchange 5.5, apply Service Pack 3, and then upgrade to Exchange 2000.

Chapter End Point

By the end of this chapter, you will have one or more successfully upgraded servers running Exchange 2000 in your Windows 2000 forest.

Chapter Sections

This chapter contains the following sections:

Preparing for Possible Upgrade Issues
Performing the Upgrade
Performing Post-Upgrade Procedures

Resource Requirements

Be sure that you have the resources outlined here before you upgrade Exchange 5.5 to Exchange 2000.

Personnel

For this procedure, you may need to involve the following personnel:

Architects/System Designers

Exchange Architect/Deployment Planning/Migration Planning Specialist
Consultants/System Integrators (may be covering the roles above)

Administrators

Deployment Administrator
Messaging/Exchange Administrator
Network Manager/Administrator

Miscellaneous

Technicians/Server Operators

You will need to report to:

Executive sponsor (if not your Product Manager) or
Chief Executive Officer/Managing Director (unless your Product Manager or management sponsor is doing this for you).

For a full listing and description of all the personnel that may be involved in an Exchange 2000 upgrade project, refer to Deployment Chapter 1, Overview of the Deployment Process.

Security and Account Privileges

You must use an account with all of the following permissions to upgrade a server running Exchange 5.5 to Exchange 2000:

Exchange 2000 Full Administrator permissions either at the Exchange 2000 organizational or administrative group level
Exchange Permissions Administrator rights on the site that your server running Exchange 5.5 is in
Local Administrator rights on the server

Skills

If you are performing this installation, you should have experience administering Exchange 5.5. If you do not have such experience, consider attending the Microsoft Exchange Server 5.5 Series – Accelerated Training for Administration and Implementation course. For more information, see Microsoft Training and Certification on the Internet at:

http://www.microsoft.com/traincert/syllabi/1313Bfinal.asp

Experience administrating Exchange 2000 is an added plus. However, considering the purpose of this guide, this is not a requirement.

Design Considerations

Upgrading a server running Exchange 5.5 to Exchange 2000 is one of the possible routes you can take when upgrading your Exchange 5.5 sites to Exchange 2000. After you upgrade it, you can use this system just as it is, or you can add connectors, public folders, or mailboxes from Exchange 5.5 or previous versions of Exchange.

Before you attempt to upgrade to Exchange 2000, you must prepare Windows 2000 Active Directory™ service and define the Exchange Full Administrator account. For more information about preparing Active Directory for Exchange 2000, refer to Deployment Chapter 2, "Configuring Windows 2000 Active Directory for Exchange 2000."

System Prerequisites

To upgrade to Exchange 2000, you must be running Exchange 5.5 SP3 on a Windows 2000 Server computer in an existing Windows 2000 forest. This server can be either a member server in a domain or a domain controller.

This server also must have Windows 2000 SP1 applied along with specific hotfixes. For more information about these hotfixes, refer to the following article in the Microsoft Knowledge Base:

271976: Hotfix Rollup Package Corrects Problems Described in 257357 and 271907.

available on the Internet at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;271976&sd=tech

Before you attempt the upgrade, you also must prepare your Windows 2000 forest and domain for Exchange 2000, as explained in Deployment Chapter 2, "Configuring Windows 2000 Active Directory for Exchange 2000."

Top Of Page

Process Flowchart

Top Of Page

Preparing for Possible Upgrade Issues

This section describes the actions you need to perform before upgrading your server running Exchange 5.5 to Exchange 2000. Taking these steps helps to reduce the risk associated with the upgrade procedure and helps you to rebuild your Exchange server, should you experience problems.

By this point, you should have prepared your Windows 2000 Active Directory and your current Exchange organization for Exchange 2000 as described in Chapter 2, Configuring Windows 2000 Active Directory for Exchange 2000. You should also have installed and updated Windows 2000 Server (or upgraded from Windows NT® version 4.0, then updated) on the computer on which you are installing Exchange 2000.

What You Will Need

To complete this procedure, you need the following items:

Backup software for the previous version of Exchange
Documented Exchange 5.5 backup procedure
Documented Windows 2000 backup procedure

What You Should Know

Before you proceed, you should know the following:

The account name and password that has permissions to back up the server that will be upgraded
The account name and password that has administrator rights to the site that hosts the server running Exchange 5.5
The account name and password that has Exchange administrator rights to the servers in the Exchange organization

Preliminary Steps

To prepare for the upgrade, you need to make a full backup of the Exchange system. To do this, complete the following steps (complete procedures are included later in the section):

Run the MTACHECK utility.
Run the Exchange Knowledge Consistency Checker.
Resynchronize the databases.
Back up the Exchange 5.5 directory service and information store and the rest of the system.

After you complete this preliminary work, you are ready to start the Exchange 2000 upgrade.

Running the MTACHECK Utility

Running the MTACHECK utility is required to make sure that the message transfer agent (MTA) database does not contain any inconsistencies or errors. The MTACHECK command takes the following optional switches.

mtacheck.exe /v /f mtacheck.log /rd /rp /rl 
/v Log verbose details
/f Log to a file. The filename follows this switch after a space.
/rd Remove directory replication messages
/rp Remove public folder replication messages
/rl Remove link monitor messages

Note: "mtacheck.log" is just an example of a log file name. Any filename can be used.

MTACHECK Procedure

To run MTACHECK:

Perform an online backup of your server that runs Exchange 5.5.
Confirm that the registry contains the correct path to the MTADATA directory. The key is: HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \Services\MSExchangeMTA\Parameters\MTA database path.
Stop the Exchange Server MTA.
IMPORTANT: Back up all \MTADATA\DB*.DAT files. Do not skip this step!
Confirm the backup by number of files and total size of the directory.

Note: Do not delete the DB*.DAT files from the MTADATA directory.
From the \Exchsrvr\Bin directory, run MTACHECK.EXE /? to determine what switches are available.
Run MTACHECK.EXE.

Note: Depending on processor speed, this generally takes one minute for every thousand messages.

If MTACHECK completes with any errors, such as

Database repaired, some data may have been lost.
0 queue(s) required repair out of 6 detected (0%).
1 object(s) damaged out of 34 detected (2%).

delete all the files in the \Mtadata\Mtacheck.out directory and then run the command again.

When MTACHECK completes successfully, the following message appears:
```
Database clean, no errors detected. 
```
Restart the MTA.

Note: If the "…some data may have been lost " message appears, do not panic. Objects and queues that were either damaged or corrupted were of two types: those that you do not mind losing (replication messages, link monitor messages), and those that could not have been salvaged anyway. Replication and link monitor messages are naturally regenerated, and therefore are expendable. Simply repeat the MTACHECK command until the following message appears: "Database clean, no errors detected."

You can expect the MTA to take several minutes to rebuild queues after you do an MTACHECK. After performing an MTACHECK, you should monitor the MTA to ensure that the errors you encountered prior to the check have been eliminated. You should consider an MTACHECK a solution only when it permanently eliminates the problem you are attempting to fix. If the problem recurs, follow other procedures to further troubleshoot the issue.

For more information about MTACheck, refer to the following KnowledgeBase articles available on the TechNet compact disc or online at:

http://www.microsoft.com/technet

XCON: Performing An MTACHECK [175495]
XCON: MTACheck Event IDs and Command Line Syntax [149017]
XCON: Mtacheck.log [163323]

Running the KCC

Run the Exchange Knowledge Consistency Checker (KCC) on the same server on which you just ran MTACHECK.

To run the KCC

Start Exchange 5.5 Administrator and navigate down to the server object.
Under the server, select the Directory Service object and from the File menu, select Properties.
Click Check Now.
When the KCC finishes, click OK.

Resynchronizing the Databases

Perform a Directory Service/Information Store (DS/IS) Consistency adjustment to resynchronize the two databases.

To resynchronize the databases

In Exchange 5.5 Administrator, select the server object (Organization, Site, Configuration, Servers, <servername>), click File, click Properties, and then click the Advanced tab.
Click Consistency Adjuster.
On the DS/IS Consistency Adjustment page, click All inconsistencies, and then click OK.
On the Warning page, click OK.
When the adjustment has completed, to close the dialog box and property sheet, click OK.

Creating the Backup

To create the system backup

Make an online backup of the Exchange 5.5 directory service and information store.
Create a Windows 2000 backup of the rest of the system. Include the registry and system state information in this backup. This will give you a rollback position in case you need to fully restore the server to the point before you started the installation.

Final Preparation

After completing the previous steps, you must uninstall (remove) any virus-scanning software, backup software, or other third-party products or their agents from these systems. Exchange 2000 Setup may fail if these are still operational during the upgrade.

Note: You also need to find replacements for these software applications that are compatible with Exchange 2000.

Top Of Page

Performing the Upgrade

With your preparation phase completed, you can now upgrade your first designated server running Exchange 5.5 SP3. As stated in the section of this chapter titled "System Prerequisites," you must be running Exchange 5.5 SP3 to perform this upgrade because there is no direct upgrade path from any other version of Exchange. For more information about upgrading to Exchange 5.5, refer to the links at the end of this section.

What You Will Need

Make sure you have the following items before you start this procedure:

Server running Exchange 5.5 SP3 on Windows 2000 SP1 system (Server or Advanced Server)
Exchange 2000 installation compact disc or access to Exchange 2000 installation files from a network location

What You Should Know

You should find out the following before beginning the upgrade process:

Exchange 5.5 Service Account name and password
Exchange 2000 Full Administrator account name and password or name and password of an account that has been delegated Exchange 2000 Full Administrator rights and local administrator rights on the server being upgraded

Upgrading an Exchange 5.5 SP3 Mailbox Server

To upgrade the server

Insert the Exchange 2000 Server installation compact disc into the CD-ROM drive of the server that you want to upgrade. Close the AutoRun window, and then open a command prompt.
At the command prompt, type:
```
F:\SETUP\I386\SETUP
```
(where F is your CD-ROM drive).
On the first page of the Exchange 2000 Installation Wizard, click Next. On the second page, click I agree, and then click Next. On the third page, type the product ID number from your Exchange 2000 Server installation compact disc, and then click Next.
On the Component Selection page, Upgrade is the only available option. If a feature was installed on the server running Exchange 5.5, you can upgrade that component. However, you cannot change the status of these items or add items to the list. Click Next to continue.

Figure 1: . Server Upgrade Component Selection Detail
On the Service Account page, type the Exchange 5.5 Service Account password, and then click Next.
On the Component Summary page, review the selected components, and then click Next to start the upgrade process. You will see the bars moving on the Component Progress page. There are three phases during the upgrade.

Note: During each of these upgrade phases, the installation routine performs several functions on the items being upgraded. If you want detailed information about what happens in each step, you can open the "Exchange Server Setup Progress.log" log file in the root of the system drive after the upgrade finishes.

Note: The Post-Installation process upgrades the directory schema of the Exchange 5.5 databases to Exchange 2000 format.
When the upgrade process finishes and the Installation Complete page appears, click Finish to close the wizard.

Note: The upgrade does not happen all at once. During the manual portion of the upgrade process, the database schema is modified and files are copied to the server. When this part finishes, the server becomes operational.

The database entries are actually upgraded as part of a background process that happens after the manual process completes. On a mailbox server, this background process only upgrades the primary Microsoft Outlook® messaging and collaboration client folders, which include the Inbox, Outbox, Calendar, Sent Items, and Contacts folders. This process enables the Exchange 2000 upgrade process to finish in a very short period of time.

However, if all your users access their mailboxes shortly after the manual part of the upgrade, the background store process attempts to upgrade their mailboxes (at least the folders that the users are accessing) in an on-demand fashion. This can cause your newly upgraded server running Exchange 2000 to slow down considerably. Therefore, you should upgrade your server when only a very small number of users might access it immediately after the upgrade completes, for example, early in the weekend. This enables the background process to upgrade the folders before the majority of users try to access the server.

Due to the client access issue just described, you should include a detailed schedule of when you will actually be performing your server upgrades as part of your Exchange 2000 migration plan.

Connection Agreements

After you have completed the upgrade steps, if this is the first server you have upgraded or a server that hosted Exchange 5.5 site directory replication connectors, open the Active Directory Connector snap-in and look at the new connection agreement (CA) that has been created in the Active Directory Connector (ADC). Figure 2 shows the new configuration CA.

Figure 2: . ADC Showing the Configuration CA Between Exchange 2000 SRS and Windows 2000 Active Directory

This configuration CA (ConfigCA) is the connection agreement that replicates the configuration information from Exchange 5.5 into Active Directory through the Exchange 2000 Site Replication Service (SRS). In addition, Exchange 2000 configuration information is replicated in the opposite direction, from Active Directory to Exchange 5.5. The Exchange 5.5 endpoint (for example, the server that is configured as the server from which the Exchange 5.5 directory is replicated) for the ConfigCA is the SRS on the server on which you just completed the upgrade.

The SRS exists only on the first server added to a site, the first server upgraded in a site, or on any upgraded directory replication server.

Verifying the Upgrade

To verify the success of your upgrade:

Verify that the component progress page on the Exchange Installation program did not display any errors.
View the Application Log and System Log for any error or warning messages related to any of the Exchange 2000 services.
Verify that you can mailbox-enable your user account in Active Directory. Then connect to the server with your client and access this mailbox.
Verify that you can send and receive e-mail.

Top Of Page

Performing Post-Upgrade Procedures

This section deals with the actions you need to perform after a successful upgrade to Exchange 2000. The steps in this section take you through the procedure for creating a full system backup that enables you to restore your server to the state it was in immediately following the upgrade, should any disaster strike in the future.

The post-upgrade procedures consist of the following:

Make a full Exchange 2000 backup of the system.
Follow this with a backup of the Windows 2000 system. This should exclude the Exchange databases but include registry and system state information.
Store the backup media in a safe location along with a printout of the backup status log.

This procedure gives you a rollback position in case you need to fully restore the server to the point before you started the backup. After you perform a full backup of the system, you have completed the Exchange 2000 upgrade.

What You Will Need

To complete this procedure, you need the following items:

Preferred Exchange 2000 Server backup software
Preferred Windows 2000 Server backup software
Documented Exchange 2000 backup procedure
Documented Windows 2000 backup procedure
The account name and password that has permissions to back up the upgraded server

Top Of Page

Recovering After a Failed Upgrade

Okay, so the worst has happened. Your server running Exchange 2000 has caught an advanced case of Monday morning disease and is glowering at you in mute protest, arms metaphorically folded with a look of grim implacability across its screen. The upgrade progress page looks more like the results of that terrible spelling test you did in sixth grade that you still remember with embarrassment today, the one with red crosses against every item. And to top it all, even Task Manager has stopped responding.

If you find yourself in this situation, there is good news and bad news. The good news is that the solution to this little problem is well documented. The bad news is that the procedure is not exactly straightforward. To recover after a failed upgrade, you need to perform the following procedure.

Important: This section contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

Recovery Steps

Manually remove Exchange 2000 completely from the computer. To do this, follow these steps:
1. In HKEY_LOCAL_MACHINE \CurrentControlSet \Services, remove all keys relating to Exchange 2000 services and drivers from the registry. These include:
  - DAVEX
  - ESE97
  - ESE98
  - EXIFS
  - ExIPC
  - EXOLEDB
  - IMAP4Svc
  - MSSEARCH
  - POP3Svc
  - RESvc
  - Anything that starts with LME-
  - Anything that starts with MSExchange
  - Anything that starts with SERVERNAME-LME
2. Remove the Exchange Setup key from the HKEY_LOCAL_MACHINE \Software \Microsoft \Exchange registry key entirely.
3. Rename the Exchsrvr folders on all disks on the computer.
4. Uninstall Microsoft Internet Information Services completely.
5. Restart the server.
Delete the renamed Exchsrvr folders from the system.
From the Exchange Server 5.5 installation compact disc, run setup /r. Choose the same installation choices that were on the original server. Choose to create a new site with the same organization and site names.
When Setup finishes, run Performance Optimizer, and configure the file locations to the same places in which the files were located before.
From the appropriate Exchange Server 5.5 service pack compact disc, run update /r.
Install any post-service pack hotfixes that were previously on the server.
Restore the directory and information store from a previous backup.
Start the directory and information store services.
Force intrasite directory replication.
Use the Active Directory Connector Management Microsoft Management Console (MMC) snap-in to force replication on the Configuration Connection Agreement.
Use the Exchange Server 5.5 Administrator program to change the alias name, admin display name, and e-mail addresses for the Site Replication Service to Directory Service, and in the e-mail address, change SRS to DSA.

Use the Exchange Server 5.5 Administrator program to change the Serial-Number attribute to "Version 5.5 (Build 2650.24: Service Pack 3)," or whatever it was before.

Use the Exchange Server 5.5 Administrator program to navigate to the server-level Protocols container of the server that failed to upgrade. If there is no lightweight directory access protocol (LDAP) object, perform the following operation:

On the File menu, click New Other, and then click Raw Object.
Double-click Protocol-Cfg-LDAP-Server.

Give the new object the following attributes:

Attribute	Value
Admin-Display-Name	LDAP (Directory) Settings
Anonymous-Access	1
Association-Lifetime	10
Directory-Name	LDAP
Enabled-Authorization-Packages	0[sect]DPA
	0[sect]DPASSL
	1[sect]CLEARTEXT
	1[sect]CLEARTEXTSSL
	1[sect]NTLM
	1[sect]NTLMSSL
Enabled-Protocol-Cfg	1
LDAP-Search-Cfg	1
Object-Class	2A864886F71401034D
	2A864886F71401034B
	2A864886F714010344
	550600
Outgoing-Msg-Size-Limit	100
Port-Number	389 (or some other number if this server is a domain controller)
Use-Site-Values	1

Restart the directory service on the Exchange Server 5.5 computer so that the LDAP addition takes effect.
Use the ADSIEdit tool from the Microsoft Windows 2000 Resource Kit to change the serialNumber attribute on the Exchange Server 5.5 computer that failed to upgrade to "Version 5.5 (Build 2650.24: Service Pack 3)," or whatever the serial number of the Exchange Server 5.5 computer is, and then change the versionNumber to 2650, or whatever major revision the Exchange Server 5.5 computer is.
Force intrasite directory replication in the Exchange Server 5.5 site, and use the Active Directory Connector Management MMC snap-in to force replication through the ConfigCA.

You can now attempt the Exchange 2000 upgrade process again.

Top Of Page

Summary

In this chapter, you learned how to upgrade an existing server running Exchange 5.5 to Exchange 2000. You learned how to limit your risk by backing up your system before the upgrade and backing it up again after completing the upgrade.

This may be the end of your upgrade path on this server. However, if you plan to migrate other resources (mailboxes, public folders, or connectors) to this machine, these processes are detailed in later chapters of this guide.

For information about migrating mailboxes and folders, refer to Deployment Chapter 6, Moving Mailboxes and Public Folders to Exchange 2000 Server. To move connectors and transports to Exchange 2000, refer to Chapter 7, Migrating Transports, Connectors, and Hubs. For all other messaging components, refer to Chapter 9, Tuning Exchange 2000 Server for Performance.

Give Us Your Feedback

We would like you to give us feedback on this material. In particular, we would be grateful for any guidance on the following topics:

How useful was the information provided?
Were the step-by-step procedures accurate?
Did you use the job aids and were they useful?
Were the chapters readable and interesting?
Overall, how do you rate the series?

Send your feedback to the following e-mail address:

TechNet_PAG_Exchange@css.one.microsoft.com

We look forward to hearing from you.

Top Of Page

Site Feedback

On This Page

Introduction

Chapter Start Point

Chapter End Point

Chapter Sections

Resource Requirements

Design Considerations

System Prerequisites

Process Flowchart

Preparing for Possible Upgrade Issues

What You Will Need

What You Should Know

Preliminary Steps

Final Preparation

Performing the Upgrade

What You Will Need

What You Should Know

Upgrading an Exchange 5.5 SP3 Mailbox Server

Connection Agreements

Verifying the Upgrade

Performing Post-Upgrade Procedures

What You Will Need

Recovering After a Failed Upgrade

Recovery Steps

Summary

Give Us Your Feedback