Knowledge Base

XADM: How to Upgrade from Exchange 2000 RC2 to RTM

PSS ID Number: 272082

Article Last Modified on 12/13/2002

The information in this article applies to:

Microsoft Exchange 2000 Server

This article was previously published under Q272082

IMPORTANT: Before you upgrade Microsoft Exchange 2000 Server Release Candidate 2 (RC2) to the Release to Manufacturing (RTM) version, Microsoft strongly recommends that you consider the advantages and disadvantages of doing so. Support is provided for customers who previewed Exchange 2000 Server RC2 and who want to upgrade to the RTM version (build 4417.5). However, Microsoft cannot guarantee that issues that result from an incorrect upgrade from the RC2 Beta version to the released version of the product can be resolved. Microsoft recommends that you install the RTM version of Exchange 2000 Server on a clean computer to minimize possible issues that are associated with upgrading a Beta version.

Upgrading versions of Exchange 2000 Server earlier than RC2 is unsupported. Only installations that started with RC2 can be reliably upgraded to the RTM version of the product. Additionally, you can upgrade from the evaluation edition of Exchange 2000 Enterprise Edition Server to the fully purchased Enterprise Edition. However, because of Exchange 2000 Enterprise Edition support for databases larger than 16 gigabytes (GB), you can only upgrade from the Exchange 2000 Enterprise Server Evaluation Edition to Exchange 2000 Enterprise Server. Upgrading from Enterprise Server Evaluation Edition to the fully-purchased, standard Exchange 2000 Server is not supported by Exchange 2000 Setup.

SUMMARY

This article outlines the procedures for upgrading from Exchange 2000 Release Candidate 2 (RC2) to Exchange 2000 Release to Manufacturing (RTM) including issues concerning a character restriction imposed on the Organization, Administrative Group, and Site display names after RC2 was released. This article covers the upgrade procedures for non-clustered servers, clustered servers, and conference servers, and is intended for experienced Microsoft Exchange Server system administrators.

This article assumes practical experience with:

The Microsoft Exchange Server Administrator program
Core Exchange Server functionality, connectivity, and terminology
Microsoft Windows NT(r) networking and security functionality
Microsoft Active Directory(tm) concepts and tools

The Release Notes on the Exchange 2000 RTM CD-ROM contain information that might be important for your installation. For example, Exchange 2000 requires Microsoft Windows 2000 with Service Pack 1 (SP1), which you can download from the following Microsoft Web site:

http://www.microsoft.com/windows2000/downloads/servicepacks/sp1/default.asp

For additional information about how to remove Exchange 2000 Server from a computer so that you can perform a new installation of the RTM version, instead of upgrading to the RTM version, click the article number below to view the article in the Microsoft Knowledge Base:

260378 XADM: How to Manually Remove an Exchange 2000 Installation

MORE INFORMATION

Upgrade Procedure for Exchange 2000 (Non-Clustered Server)

If you currently use the ADC, upgrade your ADC servers by closing down all management consoles and Microsoft Management Console (MMC) snap-ins. Then run the ADC Setup program, and click the Reinstall option. For example:

drive:\adc\i386\setup

where drive is the letter of your CD-ROM drive.
Use the root Administrator account (which is a part of the Enterprise Administrators and Schema Administrators groups). Log on to the domain where your schema Flexible Single Master Operation (FSMO) role exists (normally the root domain), and then run the Exchange 2000 Setup program with the /forestprep switch. For example:

drive:\setup\i386\setup /forestprep

It is preferable, but not required, to run ForestPrep on the Schema FSMO role owner.For additional information about locating the schema master, click the article number below to view the article in the Microsoft Knowledge Base:

234790 How to Find FSMO Role Holders (Servers)
Wait for the new schema changes to be replicated throughout your forest. This can take an extended period of time depending on the complexity of your Active Directory deployment. Because of the schema updates made during ForestPrep, your global catalogs can also be rebuilt at this time.
In each Active Directory domain, log on as a Domain Administrator, and then run the Exchange 2000 Setup program with the /domainprep switch. For example:

drive:\setup\i386\setup /domainprep
Wait for the DomainPrep changes to be replicated throughout your domain.
On the Exchange 2000 server to be upgraded, quit all management consoles and MMC snap-ins. If you do not do this, it creates file contention during the upgrade. Additionally, stop all Exchange services before you run Setup to prevent timing issues during the upgrade.
Run the Exchange 2000 Setup program. Click the Reinstall option when you are presented with the component page, and allow the upgrade to finish.

If you receive a file contention warning during the upgrade process, click the Continue button. This replaces the file with the updated version. Setup prompts you to restart the server at the end of the upgrade process, which allows the Exchange installation access to the updated files.
After the first server has been upgraded to the released product, continue to upgrade all the other RC2 servers one at a time.
After all servers have been upgraded to the released product, on the Start menu, point to Programs, point to Microsoft Exchange, and then click Exchange System Manager.
Double-click Recipients, and then click Recipient Update Services.
In the right pane is a list of all Recipient Update Services. Right-click each one, and then click to select the Rebuild check box. Depending upon the number of objects in your Active Directory, this process may take an extended period of time to finish. Until the rebuild is complete, clients cannot access their mailboxes, and they may receive an error message when they attempt to log on.

Upgrade Procedure for Exchange 2000 Clusters

Complete Steps 1 through 5 from the "Upgrade Procedure for Exchange 2000 Servers (non-clustered server)" section.
Individually move all Exchange virtual servers to node 2.
Quit all Microsoft Management Consoles (MMC) and snap-ins on node 1.
Upgrade node 1 by running the Exchange 2000 Setup program, click Reinstall, and then allow the upgrade to finish.
Individually move all Exchange virtual servers to node 1.
Quit all MMC consoles and snap-ins on node 2.
Upgrade node 2 by running the Exchange 2000 Setup program, click Reinstall, and then allow the upgrade to finish.
Move the Exchange virtual servers to their preferred nodes.
Continue steps 8 through 9 from the "Upgrade Procedure for Exchange 2000 Servers (non-clustered server)" section.

Upgrade Procedure for Exchange Conferencing Server

Insert the Exchange Conferencing Server CD-ROM in the CD-ROM drive, and share it using Windows Explorer. Map a drive to this share.
At a command-prompt, change directory to the mapped drive, and then change directory to the Conferencing\Setup\I386 folder.
Type msiexec.exe /fvemus, and wait for the upgrade to finish.
You may be asked to restart the server at the end of the upgrade; it is not necessary to do so.
Disconnect the mapped drive, and stop sharing the contents of the CD-ROM.

NOTE: You must not attempt to upgrade Exchange Conferencing Server directly from the CD-ROM because the upgrade may not complete properly. Additionally, you must not attempt to upgrade by using the Setup program supplied on the Exchange Conferencing Server CD-ROM.

If you encounter issues after Setup, use Explorer or Filever.exe (available on the Exchange 2000 CD-ROM) to ensure that the contents of your Program Files\Microsoft Exchange Conferencing Server folder contains version 4417.x binaries.

Procedure for Removing Invalid Characters

You only need to follow this procedure if you have installed Exchange 2000 RC2 using characters other than those listed below for the Organization, Administrative Group, or Site display names.

Valid characters for Organization and Administrative Group names in Exchange 2000:

A - Z
a - z
0 - 9
Space
Hyphen/Dash

Additionally, if you have joined a Microsoft Exchange Server 5.5 Organization that has characters other than those listed in its Organization or Site names, you must also remove these invalid characters from the display names of these objects before you begin the upgrade.

This procedure relies on the use of the Active Directory Services Interface (ADSI) Edit tool. This is included with the Microsoft Windows 2000 Support Tools (found on the Windows 2000 CD in the \Support folder). After you have installed the Support Tools, register the ADSIEdit tool. To register the tool:

On the Start menu, click Run.
In the Open box, type regsvr32 adsiedit.dll, and then click OK.

WARNING: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Exchange 2000 Server, or both. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

To use the ADSI Edit tool:

On the Start menu, click Run.
In the Open box, type mmc, and then click OK.
On the Console menu, click Add/Remove Snap-in.
Click Add.
In the Add Standalone Snap-in box, click to select ADSI Edit Tool, and then click Add.
Click Close, and then click OK.
Right-click ADSI Edit, and then click Connect to.
When the Connection dialog box appears, change the Naming Context to Configuration container.

For more information on ADSI Edit, refer to the Windows 2000 Resource Kit documentation.

Steps to Follow If You Have Invalid Characters in Your Organization Name

If you have Exchange Server 5.5 computers in your Organization:

Start the Exchange Server 5.5 Administrator program, log on to an Exchange Server 5.5 computer in each Exchange site in the Organization, and then change the display name of the Organization object so that it only includes valid characters. There is no requirement to change the directory name of the object.
Follow the next procedure, "If you have Exchange 2000 servers in your Organization".

If you have Exchange 2000 servers in your Organization:

Shut down all Exchange and Microsoft Internet Information Service (IIS) services on all Exchange 2000 servers in the Organization.
Start ADSI Edit, and connect to the configuration naming context of your Active Directory.
Click Configuration, click Services, and then click Microsoft Exchange.
Right-click your Exchange Organization name, and then click Rename. Change the name so that it only includes valid characters.
Right-click your Exchange Organization name, and then click Properties.
In the Select which properties to view box, click Both.
Edit the adminDisplayName attribute so that it matches the adjusted name from step 4. Click Set, and then click OK.
ADSI Edit by closing the MMC console program.
Wait for Active Directory replication to replicate this new value throughout the forest.
Restart all Exchange 2000 servers, and verify that all Exchange services start correctly.
Verify mail flow between all of your Exchange 2000 servers.

Steps to Follow If You Have Invalid Characters in Your Administrative Group Names

If you have "pure" Exchange Server 5.5 Sites in your Organization that contain invalid characters in the Site display name, these sites may show up as "ghosted" objects in Exchange System Manager. Ghosted objects refers to the black and white icons in Exchange System Manager that represent Exchange Server 5.5 sites that do not have any Exchange 2000 servers.

Start the Exchange Server 5.5 Administrator program, and log on to a server in the site that contains the invalid characters.
Change the display name of the site so that it only includes valid characters. There is no requirement to change the directory name of the object.
Wait for Exchange Server 5.5 directory replication to replicate this new value throughout the Organization.
Start ADSI Edit, and connect to the configuration naming context of your Active Directory.
Click Configuration, click Services, click Microsoft Exchange, click org, and then click Administrative Groups. The Exchange 2000 administrative groups as well as the objects representing the Exchange Server 5.5 sites are displayed in the right pane.
Right-click the names of the sites that you changed at the beginning of this procedure, and then click Delete.
Quit ADSI Edit by closing the MMC console program.
Wait for Active Directory replication to replicate the deletion of these objects throughout the forest.
Use the Active Directory Connector management snap-in to locate all Config CA_* Connection Agreements. Right-click each Configuration Connection Agreement, and then click Properties. Click the Schedule tab, and then click to select the Replicate the entire directory the next time the agreement is run check box. Click OK.
Right-click each Config CA_* Connection Agreement, and then click Replicate Now.
Wait for the ADC to replicate the new Exchange Server 5.5 Site names into Active Directory. This creates new "ghosted" Administrative Group objects.
Wait for Active Directory replication to replicate the new objects around the forest.

Please note that Exchange 2000 clients may receive non-delivery report (NDR) messages if they attempt to send messages to Exchange Server 5.5 mailboxes before this process is finished. If you have mixed Exchange Server 5.5 and Exchange 2000 Administrative Groups in your Organization that contain invalid characters in the display name:

Start the Exchange Server 5.5 Administrator program, and log on to a server in the sites that contain the invalid characters
Change the display name of the sites so that it only includes valid characters. There is no requirement to change the directory name of the object.
Wait for Exchange Server 5.5 directory replication to replicate this new value throughout the Organization.
Shut down all Exchange and IIS services on all Exchange 2000 servers in the Organization.
Start ADSI Edit, and connect to the configuration naming context of your Active Directory.
Click Configuration, click Services, click Microsoft Exchange, click org, and then click Administrative Groups. The Exchange 2000 administrative groups as well as the objects representing any Exchange Server 5.5 sites displayed in the right pane.
Right-click the mixed Exchange Server 5.5 and Exchange 2000 Administrative Group name, and then click Rename. Set this to the new display name used in step 2.
Right-click on the mixed Exchange Server 5.5 and Exchange 2000 Administrative Group name, and then click Properties.
In the Select which properties to view box, click Both.
Change the displayName attribute to correlate with the new name chosen in step 2 of this procedure. Remember to click Set after you change the Edit box, and before you click OK.
Quit ADSI Edit by closing the MMC console program.
Wait for Active Directory replication to replicate these new values throughout the forest.
Restart all Exchange 2000 servers, and then verify that all Exchange services start correctly.
Verify mail flow between all of your Exchange 2000 servers.

If you have "pure" Exchange 2000 Administrative Groups in your Organization that contain invalid characters in the display name:

Shut down all Exchange and IIS services on all Exchange 2000 servers in the Organization.
Start ADSI Edit, and connect to the configuration naming context of your Active Directory.
Click Configuration, click Services, click Microsoft Exchange, click org, and then click Administrative Groups. The Exchange 2000 administrative groups as well as the objects representing any Exchange Server 5.5 sites displayed in the right pane.
Right-click the Exchange 2000 Administrative Group name, and then click Rename. Set this to the new name.
Right-click the Exchange 2000 Administrative Group name, and then click Properties.
In the Select which properties to view box, click Both.
Change the displayName attribute to correlate with the new name. Remember to click Set after you change the Edit box, and before you click OK.
Wait for Active Directory replication to replicate these new values throughout the forest.
Restart all Exchange 2000 servers, and verify that all Exchange services start correctly.
Verify mail flow between all of your Exchange 2000 servers.

Steps to Follow if Exchange 2000 has Expired.

Decide to do one of the following actions:
- Restore from backup.
  
  -or-
- Leave databases in place.
  
  -or-
- Rename the database directories.
NOTE: If you leave the databases in place, they may not get over written.
Use the RTM version of Exchange 2000 to run the setup.exe/disasterrecovery switch
Disaster Recovery may be listed for each component that is currently installed on the server. If Disaster Recovery is not listed, click on the first component and write down the error message. Be ready to send your Setup logs to PSS if you need further assistance.
A prompt appears:

Please use the Exchange Administration Snap-In to ensure you have a valid Exchange Server Object for this server for which you are running setup in recovery mode.

After you check for the object, click OK.
Disaster Recovery begins to copy the files for each component.
A prompt appears:

After Setup has completed, please restore your databases from backup and then restart your computer.

Click OK, and then Post Installation starts
When Post Installation is done, click Finish.
You may Rename the directories or restore from backup.
Restart the server
Go into the Exchange System Manager, as the databases may be dismounted. Right-click the Databases and choose Mount.
Right-click on the databases to get Properties on the database.
Go to the Database tab, and then click to clear the check from the "Do not mount the store at start-up" box

Additional query words: x2ksetupht x2kgentop x2ktranstop x2ksetuptop xmrp

Keywords: kbhowto KB272082
Technology: kbExchange2000Search kbExchange2000Serv kbExchangeSearch

Microsoft KB Archive/272082

Contents