XADM: How to Move Exchange to a New Computer with the Same Name

Last reviewed: October 7, 1997
Article ID: Q155216
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SUMMARY

It may be necessary, due to performance or other reasons, to replace a Microsoft Exchange Server computer with a new, more powerful system.

This article explains how to move Microsoft Exchange Server to a new computer, assuming that the old computer will be off the network and the new computer will have the same name as the old computer.

MORE INFORMATION

Before moving Microsoft Exchange Server to the new computer, verify that the computer to be moved is not the only Windows NT domain controller in the domain. While this computer is shut down as part of the moving procedure, there must be a domain controller that can validate logon requests.

If the computer to be moved is a primary domain controller (PDC), make sure that there is at least one other backup domain controller (BDC) in the Windows NT domain. After shutting down the computer to be moved, upgrade the BDC to a PDC.

If the computer to be moved is a BDC, make sure that the PDC in the domain is up and operational or that there are other BDCs that can be upgraded to become the PDC.

The steps below explain how to move Microsoft Exchange Server to the new computer:

  1. On the old computer, stop all the Exchange Services.
2. Copy the entire Exchsrvr directory to another computer on the network,
    or to a tape drive. If the Exchange log and database directories are
    on different drives, use the Performance Optimizer or the Exchange
    Administrator program (from the server object's properties) to move
    all the directories to their corresponding locations under the
    Exchsrvr directory where Exchange was installed. This should be done
    before backing up the Exchsrvr directory.
3. Shut down the old computer. As explained above, make sure that there
    is an operational domain controller in the Windows NT domain.
4. Install Windows NT on the new computer with the same computer name as
    the old computer. If necessary, make it a BDC.
5. Run Setup to install Microsoft Exchange Server on this new computer
    using the same site and organization names as the installation on the
    old computer. Do not select the option to join an existing site.
    Instead, choose to create a new site. Select the same Exchange
    service account that was used on the old machine. Make sure to
    install all the connectors that were installed on the old computer.
    To do this, select the Custom installation option. Do not run the
    Performance Optimizer at the end of the Setup program. Upgrade to
    the same Service Pack as was installed on the old machine.
6. Stop all the Exchange Services. 7. Copy the backed up Exchsrvr directory over the Exchsrvr directory on
    the new computer.
8. Use Performance Optimizer to make any desired changes. 9. Start the Exchange Services.

    If an error 1011 occurs when starting the Information Store, at a 
    command prompt in the Exchsrvr\bin directory, enter the following 
    command:

       Isinteg -patch

  • Connectors may need to be reconfigured.

    Microsoft Exchange should now be running on the new computer in the same way it was on the old computer. Microsoft Exchange clients should be able to connect to the new computer just as they connected to the old computer.


  • Additional query words:
    Keywords : XADM kbenv kbusage
    Version : 4.0 5.0
    Platform : WINDOWS


    THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

    Last reviewed: October 7, 1997
    © 1998 Microsoft Corporation. All rights reserved. Terms of Use.