Article ID: 555262 - Last Review: April 12, 2006 - Revision: 1.0

Common Mistakes When Upgrading Exchange 5.5/2000 To a Exchange 2003

Author: Yuval Sinay MVP
Expand all | Collapse all

SUMMARY

The following knowledgebase will help you to upgrade from Exchange 5.5/2000 to Exchange 2003.

SYMPTOMS

The process of upgrading Exchange 5.5/2000 to Exchange 2003 might present some problems and issues
that may be avoided using these basic steps.
In addition these steps should provide some roll back options that may be helpful should a failure occurs.

RESOLUTION

 
Prior to upgrading the current system to Exchange 2003, some precautions and considerations must be taken:
 
1. Verity that the current system conforms to the System Requirements for Exchange Server 2003 guide:
 
      System Requirements for Exchange Server 2003
 
      http://www.microsoft.com/exchange/evaluation/sysreqs/2003.mspx
 
2. Is the version of the Exchange 2003 the suitable one for the task?
 
     Exchange Server 2003 Edition Comparison
 
     http://www.microsoft.com/exchange/evaluation/editions.mspx
 
3. Should the Active Directory schema be fixed? More information on this issue is available here:
 
      http://support.microsoft.com/default.aspx?scid=kb;en-us;325379

      http://support.microsoft.com/default.aspx?scid=kb;en-us;314649
 
4. Check the current system for third party software/hardware that is not supported by Exchange 2003? More information here:
 
     http://www.microsoft.com/hcl
 
5.  WINS infrastructure may present issues during the upgrade process, as described in the following link:
 
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3HighAvGuide/161d472d-7f13-4584-83c2-7e4420fa48a0.mspx
 
    Tip1: Avoiding using WINS can eliminate from legacy clients to connect to Exchange system.
    Tip2: Some service, like Windows 2003 Cluster require proper WINS infrastructure - even if you are
              using "Native" mode of Exchange and/or Windows 2003 and update client operating system.

6. Verify that you use the correct Active Directory Connector (ADC)? The latest version of the Active Directory Connector (ADC)
      is available in the Exchange 2003 Service Pack 1.
 
Upgrading Exchange Server 5.5 to Exchange 2003 in a Medium-Sized Organization
 
http://www.microsoft.com/downloads/details.aspx?FamilyID=38F816A4-FB6A-4CDB-991C-2D8FF73B5CE5&displaylang=en
 
7. Is there a need to enable Windows 2000 Schema update? Windows 2000 Schema should be configured to allow Schema updates.

       http://support.microsoft.com/?kbid=285172
 
8. Make sure that you move Exchange Enterprise Servers Group and Exchange Domain Servers Group to another container?

       http://support.microsoft.com/default.aspx?scid=kb;en-us;260914
 
9. Are you using Inet Org Person object in the domain?

       http://support.microsoft.com/default.aspx?scid=kb;en-us;307998
 
10. Consider changing the domain mode from "Mixed" to "Native".
       Exchange 5.5 allows you to configure access permission using distribution lists.
       Installing the Active Directory Connector (ADC) will convert distribution lists to Security Groups.
       If you are using Windows 2000/2003 Domain in "Mixed" mode this stage cannot be implemented
       and the upgrade process may fail.
 
11. Review "Exchange Server 2003 Disaster Recovery Operations Guide":
 
 http://www.microsoft.com/downloads/details.aspx?FamilyID=A58F49C5-1190-4FBF-AEDE-007A8F366B0E&displaylang=en
   
12. Review: "Messaging Backup and Restore at Microsoft":

 http://www.microsoft.com/downloads/details.aspx?FamilyID=1BCF89B5-4E61-40BC-87B5-1E33542ADFD0&displaylang=en
 
13. Review "Exchange Server 2003 Clustering Quality Assurance Checklist":

 http://www.microsoft.com/downloads/details.aspx?FamilyID=0E9B809D-2A7A-4ADF-9FDE-897210A461DB&displaylang=en
 
14. Disable inbound and outbound mail flow during the upgrade stage.
 
15. Make sure that the Exchange Service Account details (username and password) are available and handy
 
15. Verify that the following hotfix is installed on the Windows 2003 server that will host the Exchange server prior to the upgrade:
     - IIS 6.0 compression corruption causes access violations

       http://support.microsoft.com/default.aspx?scid=kb;en-us;831464
 
     - Windows 2003 Hotfixes from Windows Update web site

16. Map all the users that own more than one mailbox. While Exchange 5.5 allows a domain user to connect to more
        than one mailbox, Exchange 2003 will only allow a domain user to connect to a single mailbox.
17. Verity that your new Exchange Database/s are stable, and function correctly:
 
       http://support.microsoft.com/?scid=kb;en-us;825088&spid=1773&sid=global
    
18. Defrag the source Exchange Database/s before the upgrade:
 
       http://support.microsoft.com/default.aspx?scid=kb;en-us;192185
 
19 Design roll back plan:
 
      http://support.microsoft.com/?kbid=839356
 
20. Outlook and Exchange 5.5 give you option to delegate permissions to distribution list.
       However, Exchange 2003 allow to give delegate permissions only to security groups.
       Please aware to this issue before you start the migration process.

21. Redirecting the users and computers containers in Windows Server 2003 domains
 
       http://support.microsoft.com/kb/324949/
 
     May be need to be disable in the migration stage or to be consider in the design stage so the
     new accounts that need to be created the by Exchange Migration Wizard will be created in the correct container.
 
 
 
The next section contains some useful tips that may save time and help in applying a successful upgrade process:
 
 
1. It is strongly recommended to review and implement the "Exchange Server 2003 Deployment Guide":

      http://www.microsoft.com/downloads/details.aspx?familyid=77b6d819-c7b3-42d1-8fbb-fe6339ffa1ed&displaylang=en

      http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/fa02f087-7fe7-4eb7-b859-12632d762f9e.mspx
 
2. Consult your backup and anti-virus software official website for known issues regarding the upgrade,
      whether the version currently installed on your system is supported by Exchange 2003, and last but
      not least, should these software packages be disabled or removed during the upgrade stage.
 
3. Follow the Recommended private "Heartbeat" configuration on a cluster server:

     http://support.microsoft.com/?id=258750
 

Post Upgrade Actions, Troubleshooting, and Recovery
 
1.  How to configure RPC over HTTP on a single server in Exchange Server 2003:

     http://support.microsoft.com/default.aspx?scid=kb;en-us;833401
 
     And also: Upgrading Your Exchange Server 2003 RPC over HTTP Messaging Environment
 
     http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/ex2k3rpc.mspx
 
2. Use the Microsoft Exchange Server Best Practices Analyzer Tool to verity that the installation was successful
 
    http://www.microsoft.com/exchange/downloads/2003/ExBPA/default.mspx
 
3. Review the Exchange Server 2003 Message Security Guide:
 
   http://www.microsoft.com/downloads/details.aspx?FamilyID=2305405C-FAF1-488A-A856-AD467BB59B26&displaylang=en
 
4. Review the Exchange Server 2003 Operations Checklists
 
   http://www.microsoft.com/downloads/details.aspx?FamilyID=C5133F35-8E10-4477-B31C-BFD1DC09AB1E&displaylang=en
 
5. Review the Exchange Server 2003 Security Hardening Guide
 
   http://www.microsoft.com/downloads/details.aspx?FamilyID=6A80711F-E5C9-4AEF-9A44-504DB09B9065&displaylang=en
 
6. Review the Downloads section for Exchange Server 2003 for new hotfixes, manuals and tools:
    
   http://www.microsoft.com/exchange/downloads/2003/default.mspx
 
7. Review the Windows Server 2003 PKI Operations Guide:

     http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/ws03pkog.mspx
 
8. Consult the following link for information on how to remove the last Exchange Server 5.5 computer from an Exchange Server 2003 administrative group:
 
    http://support.microsoft.com/default.aspx?scid=kb;en-us;822450
 
9. Consider changing the Exchange system mode to Native mode. More information is available here:
 
    How To Convert from Mixed Mode to Native Mode in Exchange
 
    http://support.microsoft.com/kb/327779
 
10. Verity correct mailbox and account creation by using the article bellow:
     How accounts and mailboxes are created and mapped when you use the Migration Wizard to migrate
      from Exchange Server 5.5 to Exchange 2000 Server or to Exchange Server 2003
 
    http://support.microsoft.com/?scid=kb;en-us;281583&spid=1773&sid=global
 

Known issues:
 

"500 - Internal server error" error message when a user tries to access a clustered Exchange Server 2003 back-end server using Outlook Web Access
 
   http://support.microsoft.com/kb/841561
 
Overview of the spelling checker in Outlook Web Access for Exchange Server 2003
 
   http://support.microsoft.com/default.aspx?scid=kb;EN-US;825430
 
Outlook Web Access session unexpectedly quits when forms-based authentication is used
 
   http://support.microsoft.com/?kbid=820378
 
"Outlook Web Access was unable to check the spelling on this item due to an error" error message when you use the spelling checker
 
   http://support.microsoft.com/default.aspx?scid=kb;en-us;822699
 
Backup of the Exchange Server 2003 Information Store and the Windows Server 2003 System State Data Does Not
 Complete Successfully and Event ID 8019 Is Logged
 
   http://support.microsoft.com/?id=820852
 
You receive a non-delivery report when you send a message from an Exchange Server 5.5 computer to a distribution group that is hosted in a
     mixed administrative group
 
   http://support.microsoft.com/?kbid=841834
 
The Internet Address template does not appear correctly after you upgrade to Exchange Server 2003
 
   http://support.microsoft.com/?scid=kb;en-us;870581&spid=1773&sid=globa
 
You receive an "A connection could not be made to the remote directory service...ID no: c1030b11" error message when you try to install a Site Replication
   Service in Exchange Server 2003 or in Exchange 2000 Server

http://support.microsoft.com/default.aspx?scid=kb;en-us;901052
 
An e-mail message that is addressed to a recipient on an external domain is unexpectedly forwarded through an Exchange Server 5.5 server in an Exchange 2000 Server mixed-mode topology
 
http://support.microsoft.com/kb/320504
 
 

MORE INFORMATION

 
Exchange 2003
 
http://www.microsoft.com/exchange/default.mspx
 
How to obtain the latest service packs for Exchange Server 2003
 
http://support.microsoft.com/kb/836993

comparison of the migration methods for migrating from Exchange Server 5.5 to Exchange Server 2003 or to Exchange 2000 Server
 
http://support.microsoft.com/?id=327928
 
How to obtain the latest ISA Server 2004 service pack
 
http://support.microsoft.com/kb/891024
 
Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain
 
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;555040
 

APPLIES TO
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange 2000 Enterprise Server
  • Microsoft Exchange 2000 Conferencing Server
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbpubmvp kbpubtypecca kbhowto KB555262
Community Solutions ContentCOMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
 

Article Translations