This article outlines the procedure for installing a service pack or on Windows Server Failover Cluster. The process of applying a service pack to a server cluster is the same as applying it to Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003. However, special consideration must be taken to ensure a high level of access for clients when you perform this system maintenance.
You can install Windows service packs on Windows Server Failover Cluster nodes using the following procedure. Always install the same service packs or hotfixes to each node. Use this procedure to install the service packs or hotfixes unless otherwise directed by a particular service pack version.
Steps to install Windows service pack or hotfixes in Windows Server 2003.
Check the System event log for errors and ensure proper system operation.
Make sure you have a current backup and updated emergency repair disk for each system. In the event of corrupt files, power outage, or incompatibility, it may be necessary to revert back to the state of the system prior to attempting to install the service pack/hotfixes.
Open Cluster Administrator, right-click Node A, and then click Pause Node.
Expand Node A, and then click Active Groups. In the left pane, right-click the groups, and then click Move Group to move all groups to Node B.
Install the service pack on Node A, and then restart the computer.
Check the System event log for errors. If you find any errors, troubleshoot them before continuing this process.
In Cluster Administrator, right-click Node A, and then click Resume Node.
In Cluster Administrator, right-click Node B, and then click Pause Node.
Right-click Node B, and then click Move Group for all groups owned by Node B to move all groups to Node A.
Install the service pack on Node B, and then restart the computer.
Check the system event log for errors. If you find any errors, troubleshoot them before continuing this process.
In Cluster Administrator, right-click Node B, and then click Resume Node.
Right-click each group, click Move Group, and then move the groups back to their preferred owner.
Steps to install Windows service pack or hotfixes in Windows Server 2008 and Windows Server 2008 R2 using Failover Cluster Manager. Membership in the local Administrators group on each clustered server, or equivalent, is the minimum required to complete this procedure.
Check the event log for errors and ensure proper system operation.
Make sure you have a current backup and updated emergency repair disk for each system. In the event of corrupt files, power outage, or incompatibility, it may be necessary to revert back to the state of the system prior to attempting to install the service pack/hotfixes.
In the Failover Cluster Manager snap-in, right-click Node A, and then click Pause.
On Node A, Expand Services and Applications, and then click the service or application
Under Actions (on the right), click Move this service or application to another node, then choose the node.
Note: As the service or application moves, the status is displayed in the results pane (in the center pane). Follow the Step 4 and 5 for each service and application configured on the cluster.On a cluster with more than two nodes, from the options next to Move this service or application to another node, you can choose Best possible. This option has no effect if you have not configured a Preferred owners list for the service or application you are moving (in this case, the node will be chosen randomly). If you have configured a Preferred owners list, Best possible will move the service or application to the first available node on the list.
Install the service pack/hotfixes on Node A, and then restart the computer.
Check the event log for errors. If you find any errors, troubleshoot them before continuing this process.
In Failover Cluster Manager snap-in, right-click Node A, and then click Resume.
From the Failover Cluster Manager snap-in, right-click Node B, and then click Pause.
Under Actions (on the right), click Move this service or application to another node, then choose the node. Note: As the service or application moves, the status is displayed in the results pane (in the center pane). Follow the Step 9 and 10 for each service and application configured on the cluster.
Install the service pack/hotfixes on Node B, and then restart the computer.
Check the event log for errors. If you find any errors, troubleshoot them before continuing this process.
In Failover Cluster Manager, right-click Node B, and then click Resume.
Right-click each group, click Move Group, and then move the groups back to their preferred owner.
Steps to install Windows service pack or hotfixes in Windows Server 2008 R2 Failover Cluster using PowerShell commandlets. Membership in the local Administrators group on each clustered server, or equivalent, is the minimum required to complete this procedure.
Check the event log for errors and ensure proper system operation.
Make sure you have a current backup and updated emergency repair disk for each system. In the event of corrupt files, power outage, or incompatibility, it may be necessary to revert back to the state of the system prior to attempting to install the service pack/hotfixes.
In the Windows Server 2008 R2, there will be a ‘Windows PowerShell Modules’ link under your Administrative Tools which will automatically import all the PowerShell modules for features or roles which you have installed.
Open Failover Cluster PowerShell Management from the shortcut in Administrative Tools or Open PowerShell on your machine through right-clicking and selecting Run as administrator.
Load the module with the command: Import-Module FailoverClusters
Suspend (Pause) activity on a failover cluster nodeA: Suspend-ClusterNode nodeA
Move a clustered service or application (a resource group) from one node to another: Move-ClusterGroup <clustered service> -Node nodeB
Tip: You can also use following command to move all groups of the node to the preferred owner of the best possible:
Get-ClusterNode NodeA | Get-ClusterGroup | Move-Cluster Group
Install the service pack on Node A, and then restart the computer.
Check the System event log for errors. If you find any errors, troubleshoot them before continuing this process.
Resume activity on nodeA that was suspended in step 5: Resume-ClusterNode nodeA
Suspend (Pause) activity on other failover cluster node: Suspend-ClusterNode nodeB
Move a clustered service or application (a resource group) from one node to another: Move-ClusterGroup <clustered service> -Node nodeB
Note: You can again use following command to move all groups of the node to the preferred owner of the best possible:
Get-ClusterNode NodeB | Get-ClusterGroup | Move-Cluster Group
Install the service pack on Node B, and then restart the computer.
Check the System event log for errors. If you find any errors, troubleshoot them before continuing this process.
Resume activity on nodeB that was suspended in step 10 above: Resume-ClusterNode nodeB
Move the clustered service or application (a resource group) back to their preferred owner: Move-ClusterGroup <clustered service> -Node <nodename>.
Back to the top
