Sdílet prostřednictvím


How to Upgrade a Clustered Mailbox Server in a CCR Environment to Exchange 2007 SP1 or later

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007 SP1, Exchange Server 2007 SP2

This topic explains how to use Setup.com to upgrade a clustered mailbox server in a cluster continuous replication (CCR) environment from the release to manufacturing (RTM) version of Microsoft Exchange Server 2007 to Microsoft Exchange Server 2007 Service Pack 1 (SP1) or later versions. Clustered mailbox servers can be upgraded using only the command-line version of Setup. You can't use the graphical user interface (GUI) version of Setup (also known as the Exchange Server 2007 Setup Wizard, or Setup.exe) to upgrade a clustered mailbox server.

The following procedure should be used only to upgrade a clustered mailbox server in a CCR environment. For detailed steps about how to upgrade a clustered mailbox server in a single copy cluster (SCC), see How to Upgrade a Single Copy Cluster to Exchange 2007 SP1 or later.

Before You Begin

We recommend that you make a complete backup of the clustered mailbox server prior to upgrading to Exchange 2007 SP1 or later and again after successfully completing the upgrade to Exchange 2007 SP1 or later.

To perform this procedure, the account you use must be delegated membership in the Exchange Server Administrator role. For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

Note

Performing this procedure results in a brief outage during the upgrade process. Exchange Setup /m:upgrade should be run only on the passive node in the cluster. Setup /UpgradeCms must be run on the active node. Both nodes need to be updated to Exchange 2007 SP1 or later to be supported, but you must upgrade the nodes one at a time. After each node has been upgraded, the clustered mailbox server is upgraded, and then brought online.

In the following procedure, the designations of the active and passive node change. Therefore, for ease of reference in the following procedure, the original active node is NodeA and the original passive node is NodeB.

Procedure

To use Setup.com to upgrade a clustered mailbox server in a CCR environment to Exchange 2007 SP1 or later

  1. Prepare NodeB to be upgraded by moving all cluster resource groups to NodeA. The clustered mailbox server can be left in an online (running) state during the first part of this procedure; however, during this procedure it will be taken offline and moved between nodes in the cluster. Perform Steps 2–11 on NodeB.

  2. Stop any services that have open handles to performance counters. Known services that should be stopped include Performance Logs and Alerts and any Microsoft Operations Manager agents.

  3. Stop and then restart the Remote Registry service.

  4. Open a Command Prompt window, and then navigate to the Exchange 2007 SP1 or later installation files.

  5. Run the following command:

    Setup /m:upgrade
    

    Setup performs the Exchange 2007 SP1 or later upgrade prerequisite checks and, after those are complete, Setup upgrades NodeB to Exchange 2007 SP1 or later.

  6. Restart NodeB after Setup has completed the upgrade to Exchange 2007 SP1 or later.

  7. After the restart process is complete, log on to NodeB and open the Exchange Management Shell.

  8. Use the Stop-ClusteredMailboxServer cmdlet to stop the clustered mailbox server. For example, you can use the following command to stop a clustered mailbox server named EXCLUS1:

    Stop-ClusteredMailboxServer EXCLUS1 -StopReason "Upgrade to SP2"
    
  9. Use the Move-ClusteredMailboxServer cmdlet to move the clustered mailbox server from NodeA to NodeB. This cmdlet must be run from NodeB. For example, you can use the following command to move a clustered mailbox server named EXCLUS1 to NodeB:

    Move-ClusteredMailboxServer EXCLUS1 -TargetMachine NODEB -MoveComment "Upgrade to SP2"
    
  10. In a Command Prompt window, navigate to the Exchange 2007 service pack installation files.

  11. Run the following command to upgrade the clustered mailbox server that is now owned by NodeB:

    Setup /upgradecms
    

    Setup performs the clustered mailbox server prerequisite checks and, after those are complete, Setup upgrades the clustered mailbox server and brings it online.

  12. On NodeA, stop any services that have open handles to performance counters. Known services that should be stopped include Performance Logs and Alerts and any Microsoft Operations Manager agents.

  13. Stop and then restart the Remote Registry service.

  14. Open a Command Prompt window, and then navigate to the Exchange 2007 SP1 or later installation files. Run the following command on NodeA to upgrade it to Exchange 2007 SP1 or later:

    Setup /m:upgrade
    

    Setup performs Exchange 2007 upgrade prerequisite checks and, after those are complete, Setup upgrades NodeA.

  15. Restart NodeA after Setup has completed the upgrade to Exchange 2007 SP1 or later.

    The clustered Exchange 2007 mailbox server has now been upgraded.

During the upgrade procedure, ownership of the clustered mailbox server changed nodes. If you want, you can move the clustered mailbox server back to the original node. You can perform the move operation by using the Move-ClusteredMailboxServer cmdlet. You can also perform the move operation by using the new Manage Clustered Mailbox Server wizard in the Exchange Management Console, which is a feature of Exchange 2007 SP1 and later versions.

For More Information

For detailed steps about how to move a clustered mailbox server in a CCR environment using the Exchange Management Shell or the Exchange Management Console, see How to Move a Clustered Mailbox Server in a CCR Environment.

For more information about the Move-ClusteredMailboxServer cmdlet, see Move-ClusteredMailboxServer. For more information about the Stop-ClusteredMailboxServer cmdlet, see Stop-ClusteredMailboxServer.