Patching Microsoft Exchange 2007 on Windows clusters

You can use Server Automation Fixlets to patch a Windows® Cluster that is running Microsoft Exchange 2007 on Windows Server 2003 or Windows Server 2008. As per industry standard, patch the passive node first. This avoids moving the Mailbox server twice in a patching scenario. You add the Server Automation Fixlets into a plan to automate the patching process. You can use Fixlet 121 Move Exchange 2007 Mailbox Server from Node to identify the active node as this Fixlet will only be relevant on the node running the Mailbox server.

Before you begin

  • Before running any of the patching steps the control scripts must be installed. Use Task 110-Install Windows Cluster Control Application to install the control scripts.
  • The IBM Exchange Cluster Manager Service must be installed. Use Task 123 Install IBM Exchange Cluster Manager Service to install the service.
  • .Net Framework 4.0 must be installed on each node. Use Fixlet 40301 UPDATE: Microsoft .NET Framework 4.0 Available -Site-Patches for Windows to install or update the .Net Framework 4.0 on each node.

About this task

The IBM cluster patch solution works by using a number of Fixlets and a service to enable patching of an Exchange cluster environment. To move an Exchange Mailbox Server from node to node you must be a domain level user. To achieve this a service is installed on each node which runs with the domain level credentials. Moving the clustered mailbox is governed by a Microsoft Shell Command and might not always successfully move the mailbox.

Start the patching process by patching the passive node. Then repeat the procedure for the active node.

Procedure

  1. Optional: Use Fixlet 121 Move Exchange 2007 MailboxServer from Node to move the Mailbox Server from the node.
  2. Pause the node or nodes in the cluster that you want to patch. Run one of the following Fixlets:
    1. Fixlet ID 112 Pause Node for Windows 2003 Servers.
    2. Fixlet ID 116 Pause Node for Windows 2008 Servers.
  3. Move any groups on the node to another node using one of the following Fixlets:
    1. Fixlet ID 111 Move Groups for Windows 2003 Servers.
    2. Fixlet ID 114 Move Groups for Windows 2008 Servers.
  4. Patch or update the node as required. If you use a Baseline to patch the node, check if the Baseline contains an action script that causes the node to report a status of Pending Restart, for example, action requires restart. If the node returns a Pending Restart status, the system determines this as a wait state and does not complete the step. To correct this, you must include a restart Fixlet as part of the Baseline.
  5. Resume the node using one of the following Fixlets, depending on your operating system:
    1. Fixlet ID 113 Resume Node for Windows 2003 Servers
    2. Fixlet ID 115 Resume Node for Windows 2008 Servers
  6. Repeat this process for the active node in the cluster.