Upgrading a two Node – Exchange 2007 CCR cluster to Service Pack 1…

by Andy Grogan on December 28, 2008 · 0 comments

in Exchange 2007 (CCR), Windows Clustering

If you look over the Internet you will find loads and loads of article which tell you what is enhanced in Service Pack 1 (which I will not go into here, but if you are interested the following TechNet article gives you a good overview of what is new http://technet.microsoft.com/en-us/library/bb676323.aspx ).

However one (perhaps not obvious) cool thing about this service pack that is worthy of note is that it is slip streamed – therefore, if you have the original Exchange Binaries on your mail server you can delete them and replace with the Service Packs extracted files – this is the first Exchange Service Pack to do this (apparently it has been made possible due to a change in setup technology).

Generally speaking the installation of the service pack is very straight forward for normal Exchange 2007 Roles (such as Hub Transport, Basic Mailbox, Client Access) – however when you get into the realms of looking at CCR upgrades things change a little and become a tiny bit more complex.

In this article I would like to go through how you can safely deploy Exchange 2007 Service Pack 1 onto your CCR installation with (hopefully) as minimum of fuss as possible.

Before we begin

Please ensure that before you begin the upgrade that you have take a full backup of your Exchange Databases and configuration – I know that this goes without saying, but it can be tempting to skip this step – please don’t – just in case.

Step 1 – Installation work on your Secondary Node:

Like in Exchange 2003 clustering – most of the initial Service Pack installation takes place on the Secondary Node (Passive) – therefore all of the following steps MUST be done on the Secondary Node of you CCR cluster – please do not perform any Actions on the Primary Node until advised:

Preparation work on the secondary node

  • Take a System State Backup – this should also encompass the configuration of your cluster.
  • Ensure that all cluster resources (including the Cluster Group itself are on the Primary Node) – to do this run the following commands
    • Open an Exchange Management Shell Session and type:
    move-clusteredMailboxServer –identity -Target -MoveReason  “Service Pack 1”
    • Open a command prompt and type:
    Cluster group

If the command reports that the Cluster Group Resources are resident on the Secondary Node (which in my example above they are) – type in the following command:

Cluster group “Cluster Group” /move
  • Disable any File Level Virus checker (to ensure that none of the Service Packs processes are interfered with) on the Secondary Node – If you are running the RTM build of Forefront on your Exchange Server – you must either remove it or upgrade to a later version BEFORE you run the CCR upgrade process.
  • TIP: Copy the Binaries to a LOCAL disk which will speed up the upgrade process however do not copy them to a Network Drive this will affect how the .NET components of the Installer function.
  • Install .NET Framework 2.0 SP1 (x64) from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=029196ED-04EB-471E-8A99-3C61D19A4C5A&displaylang=en or the patch for .NET 2.0 (x64) from here: http://go.microsoft.com/fwlink/?linID=101219 – Exchange 2007 SP1 will install without either of these, but it is recommended that you apply the updates – please not installing .NET 3.0 does not negate this recommendation.
  • Run the RmtStBackup.reg file:

Essentially in Service Pack 1 of Exchange 2007 “Remote Streaming Backups” are disabled by default. The reason for this is to reduce Exchange 2007 from being open to attack from malicious users.Under Exchange 2007 RTM Remote Streaming is enabled by default, this could allow for users with the correct rights to take a back of the Exchange server over non-encrypted network links to un-encrypted destinations SP1 disables this functionality.However, Remote Streaming is REQUIRED to be enabled by CCR cluster nodes for operations such as the “seeding” (where database copies are synchronised between the nodes) .File changes or adds the following data to the Registry on the node:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\]
Name: Enable Remote Streaming Backup
Type: DWORD
Value: 1 (Decimal)

This file (which is provided below) is for your convenience;

RmtStBackup.reg

  • Reboot the node – when the above has been completed you should restart the secondary node.

When the node has finished rebooting you will need to continue with the following steps:

  • Set the Windows 2003 Windows Firewall and Internet Connection Sharing service to “Manual” in the services manager – and then start the service – this is required so Exchange 2007 SP1 can add exceptions to the Windows Firewall for Exchange – see below for an example:

  • Restart the Remote Registry Service – see below:

  • From computer management check for Open File Handles on the server close any which are not required (you will see entries for the Cluster Service DO NOT TOUCH THESE) – see below for an example of what the Open Files window in Computer Management should look like:

  • Check the Task Manager for instances of PowerShell.exe – if you find any end the process – if you don’t then Exchange server setup will fail (see example below)

Running the Upgrade on the CCR Secondary Node;

When you have completed the above open a Command Prompt and navigate to the location where you have placed the extracted Service Pack files and run the following command:

Setup.com /m:Upgrade (see below)

Setup will begin to check a number of aspects of your Exchange configuration if it encounters any issues you will be told at this point – for example below you will see what is displayed when SP1 for .NET 2.0 is not installed :

Also if there is an error with the configuration or the prerequisites you will be notified at this point – the example below is the error you get when PowerShell.exe still has an instance running:

Providing that all of the stages have gone to plan setup will complete with a message that looks like the following:

  • When Setup has completed on the Secondary Node – restart the system.

When the system has rebooted – Log back onto the Secondary Node then open the Exchange Management Shell and type the following:

Stop-ClusterMailboxServer -stopReason “SP1 Upgrade”

Which should look like the following example:

You will be prompted with a question asking if you are sure – type in “A” for all.

When the above command has completed type in the following command:

move-clusteredMailboxServer -target -MoveComment “SP1  Upgrade”

Again you will be prompted to confirm type in “A” for all.

Below is an example of both the above commands and their output:

What we have done here is moved the Exchange resources to the SECONDARY NODE, but left them offline – We are now ready to upgrade the Exchange CCR Cluster

When all commands have completed – exit the Exchange Management Shell.

Whilst still on the Secondary Node navigate to the location of the Service Pack 1 binaries and run the following command:

Setup.com /upgradeCMS

Again Exchange will go through the normal checks and then perform the required updates to the Exchange databases and cluster entries in AD – the following is a successful output from the process:

Running the upgrade on the Primary Node;

When the upgrade of the Clustered Mailbox Server has completed on the Secondary Node you need to move to the Primary Node – at this point you should ensure that you move the “Cluster Group” (and only the Cluster Group) over to the Secondary Node.

REMEMBER: All of the following MUST be done on your Primary Node – please do not perform any Actions on the Secondary Node until advised:

  • As before take a System State Backup
  • Disable any File Level Virus checker (to ensure that none of the Service Packs processes are interfered with) on the Primary Node – If you are running the RTM build of Forefront on your Exchange Server – you must either remove it or upgrade to a later version BEFORE you run the CCR upgrade process.
  • TIP: Copy the Binaries to a LOCAL disk which will speed up the upgrade process however do not copy them to a Network Drive this will affect how the .NET components of the Installer function.
  • Install .NET Framework 2.0 SP1 (x64) from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=029196ED-04EB-471E-8A99-3C61D19A4C5A&displaylang=en or the patch for .NET 2.0 (x64) from here: http://go.microsoft.com/fwlink/?linID=101219 – Exchange 2007 SP1 will install without either of these, but it is recommended that you apply the updates – please not installing .NET 3.0 does not negate this recommendation.
  • Run the RmtStBackup.reg file
  • Reboot the node – when the above has been completed you should restart the secondary node.

When the node has finished rebooting you will need to continue with the following steps:

  • Set the Windows 2003 Windows Firewall and Internet Connection Sharing service to “Manual” in the services manager – and then start the service – this is required so Exchange 2007 SP1 can add exceptions to the Windows Firewall for Exchange
  • Restart the Remote Registry Service
  • From computer management check for Open File Handles on the server close any which are not required (you will see entries for the Cluster Service DO NOT TOUCH THESE) – see below for an example of what the Open Files window in Computer Management should look like:

  • Check the Task Manager for instances of PowerShell.exe – if you find any end the process – if you don’t then Exchange server setup will fail (see example below)
  • Using the Windows Command Prompt navigate to the location where you have placed the Exchange Binaries, and type
Setup.com /m:Upgrade

Should everything go to plan the Primary Node will then upgrade correctly.

Final Steps:

On both nodes (should you wish) stop the Windows Firewall and Internet Connection Sharing service and set it back to a disabled state.

Re-Enable Anti Viral counter measures

On the secondary node open a Exchange Management Shell session and type the following commands (in this order):

Stop-ClusterMailboxServer -stopReason “SP1 Upgrade”
move-clusteredMailboxServer -target -MoveComment “SP1  Upgrade”
Start-ClusterMailboxServer

After the above commands have been run, and were successful open a Windows command prompt and type:

Cluster group “Cluster Group” /move

I hope that you find the above guide useful

{ 0 comments… add one now }

Leave a Comment

*

Previous post:

Next post: