The System Center Operations Manager Support Team Blog

This is the OpsMgr 2007 blog for the Microsoft support team. If you were looking for the SCOM 2007 or MOM 2005 blog then you are in the right place.

How to apply a System Center Operations Manager 2007 R2 cumulative update to a clustered RMS

How to apply a System Center Operations Manager 2007 R2 cumulative update to a clustered RMS

  • Comments 1
  • Likes

KBJust a quick heads up on a new System Center Operations Manager 2007 Knowledge Base article we just published. This one shows you how to apply a Microsoft System Center Operations Manager 2007 R2 cumulative update to clustered Root Management Server (RMS) nodes:

=====

This article describes how to apply a Microsoft System Center Operations Manager 2007 R2 cumulative update to a clustered Root Management Server (RMS) set of nodes. For more information about System Center Operations Manager 2007 R2 Cumulative Update 2, click the following article number to view the article in the Microsoft Knowledge Base:

KB979257 - System Center Operations Manager 2007 R2 Cumulative Update 2 Release Notes

For a Windows Server 2003 cluster:
  1. Log on to the cluster node that runs RMS by using an account that has local administrator rights. This account must also be a member of the Operations Manager Administrators role for the R2 management group.
  2. Start Cluster Administrator tool.
  3. In the navigation pane, expand the cluster name, expand Groups, and then click the resource group that contains the RMS service resource.
  4. In the details pane, examine the cluster resources that are listed in Name column, and make sure that they are online.
  5. In the details pane, in the Owner column, note which node owns the cluster.
  6. Log on to the node that owns the cluster. To do this follow these steps:
    1. In the navigation pane, right-click the Operations Manager cluster group.
    2. Click Move Group, and then select the node from the list that represents the node to which you have logged on.
  7. The following cluster resource services may stop when you apply the cumulative update to a multiple-node cluster:
    • OpsMgr Config Service (OMCFG)
    • OpsMgr Health Service (HEALTHSERVICE)
    • OpsMgr SDK Service (OMSDK)
    This occurs because the cluster interprets this update as a failure and then fails over to another node. To prevent this issue, you must limit the nodes on which a service can run to the specific node that you are updating. To do this, follow these steps.
    Note These steps must be followed for every node to which you apply the cumulative update. When the update is complete for each node, users should add failover nodes again to the Available Nodes list. When every node is updated, you must configure your Operations Manager 2007 group to fail over to the original primary node.
    1. In the details pane, right-click the Cluster Resource service that you want to change (for example, OpsMgr Health Service), and then click Properties.
    2. In the Properties dialog box, click Modify.
    3. In the Modify Possible Owner dialog box, under Available nodes, select the node that to which you are applying the cumulative update, make sure that this is the only node that is listed under Possible owners, and then click OK.
  8. Open the folder to which the cumulative update MSI was extracted.
  9. At a command prompt, type the following, and then press ENTER:

    SetupOM.exe

  10. Follow the installation instructions.
    Note You may receive a warning message that a service did not start or stop. Click OK to dismiss the warning.
  11. When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish. Restart the server if you are prompted.

Repeat these steps on all nodes of the cluster. For each successive node, you must select the Second node of a Windows Server Cluster option on the Welcome to the System Center Operations Manager 2007 R2 Server Setup Upgrade Wizard page. For each additional node, make sure that you log on to the node that you are upgrading and that all cluster groups are owned by that node.

 

For a Windows Server 2008 cluster:
  1. Log on to the cluster node that runs RMS by using an account that has local administrator rights. This account must also be a member of the Operations Manager Administrators role for the R2 management group.
  2. Start the Failover Cluster Management tool.
  3. Expand the cluster, expand Services and Applications, and then select the RMS application.
  4. In the details pane, in the Owner column, note which node owns the cluster.
  5. Log on to the node that owns the cluster. To do this follow these steps:
    1. In the navigation pane, right-click the Operations Manager cluster group.
    2. Click Move Group, and then select the node from the list that represents the node to which you have logged on.
  6. Examine all the resources, and make sure that they are all online.
  7. The following cluster resource services may stop when you apply the cumulative update to a multiple-node cluster:
    • OpsMgr Config Service (OMCFG)
    • OpsMgr Health Service (HEALTHSERVICE)
    • OpsMgr SDK Service (OMSDK)
    This occurs because the cluster interprets this update as a failure and then fails over to another node. To prevent this issue, you must limit the nodes on which a service can run to the specific node that you are upgrading. To do this, follow these steps:
    Note These steps must be followed for every node to which you apply the cumulative update. When the update is complete for each node, users should add failover nodes again to the Available Nodes list. When every node is updated, you must configure your Operations Manager 2007 group to fail over to the original primary node.
    1. In the details pane, right-click the Cluster Resource service that you want to change (for example, OpsMgr Health Service), and then click Properties.
    2. In the Properties dialog box, click Modify.
    3. In the Modify Possible Owner dialog box, under Available nodes, select the node o which you are applying the cumulative update, make sure that this is the only node listed under Possible owners, and then click OK.
  8. Open the folder to which the MSI was unpacked.
  9. At a command prompt, type the following, and then press ENTER:

    SetupOM.exe

  10. Follow the installation instructions.
    Note You may receive a warning message that a service did not start or stop. Click OK to dismiss the warning.
  11. When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish. Restart the server if you are prompted.

Repeat these steps on all nodes of the cluster. For each successive node, you must select the Second node of a Windows Server Cluster option on the Welcome to the System Center Operations Manager 2007 R2 Server Setup Upgrade Wizard page. For each additional node, make sure that you log on to the node that you are upgrading and that all cluster groups are owned by that node.

=====

The information above was published today in the following Microsoft Knowledge Base article written by Filip Lazar:

KB2184500 - How to apply a System Center Operations Manager 2007 R2 cumulative update to a clustered RMS

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials

clip_image001 clip_image002

Comments
  • it should be Root Management Server and not Right Management Services!!

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment