Clustering the SCOM 2007 R2 RMS Role on a Microsoft SQL 2008 R2 Cluster (Part 1)
Clustering the SCOM 2007 R2 RMS Role on a Microsoft SQL 2008 R2 Cluster (Part 2)
Clustering the SCOM 2007 R2 RMS Role on a Microsoft SQL 2008 R2 Cluster (Part 3)
Clustering the SCOM 2007 R2 RMS Role on a Microsoft SQL 2008 R2 Cluster (Part 4)
Clustering the SCOM 2007 R2 RMS Role on a Microsoft SQL 2008 R2 Cluster (Part 5)
Following the instructions detailed in my previous 5 posts, you should now have your SQL 2008 R2 Cluster built and your SCOM 2007 R2 RMS Cluster built and tested. This post will outline some troubleshooting steps to take in the event of an issue with your newly built SCOM 2007 RMS Cluster and also explain how to install SCOM 2007 R2 Reporting into an SQL 2008 R2 environment.
Preparing an Inaccessible Management Server
The following procedure is required only if, in bringing the cluster group online, the output stated that you are required to run the ManagementServerConfigTool.exe tool by using the AddRMSNode action on any of the non-root management server cluster nodes. This is most likely caused by a cluster node that is not accessible when the InstallCluster action was executed or you are adding a new node to the cluster.
1. Log on to the computer that hosts the management server as a member of the Administrators group.
2. Open the services snap-in and if the startup type for the System Center Data Access Service is set to Disabled, change it to Manual.
3. As an administrator, open a Command Prompt window , change directories to the installation folder, and type the following:
ManagementServerConfigTool.exe AddRMSNode /vs:<VirtualServerNetbiosName> /Disk:<VirtualServer Disk Resource>
VirtualServerNetbiosName is the Network Name resource allocated to the same cluster group. The value you enter for VirtualServerNetbiosName must be the value that appears in the Name box on the General tab of the Properties dialog box for the Network Name Cluster resource.
VirtualServerDiskResource is the disk resource allocated to the cluster group being used to create this Virtual root management server. The Disk location can be found in the results pane of the properties for the RMS application.
Installing SCOM 2007 R2 Reporting into an SQL 2008 R2 Environment
If you are installing the SCOM 2007 R2 Reporting Services into an SQL 2008 R2 environment, ensure you have renamed the local SQL group by removing the _50 section from its name on the SCOM server as outlined near the start of this document (see below for a reminder):
Once the SCOM 2007 Console installation is completed, re-run the installer again and select the ‘Install Operations Manager 2007 R2 Reporting’ option
Within the ‘Operations Manager 2007 Reporting Setup’ window, when selecting components to install, DO NOT install the ‘Data Warehouse’ component if you are installing into a Windows SQL 2008 R2 instance, if installing into an older version of SQL, then leave all components selected and continue on
When prompted, enter the credentials for the ‘Data Warehouse Write Account’ (srv_scom_datawrite) and select ‘Next’
When prompted, enter the credentials for the ‘Data Warehouse Read Account’ (srv_scom_dataread) and select ‘Next’
Move through the remaining menu’s selecting the default options until you see the ‘Install’ button and then press this to initiate the reporting services installation
When the installation of SCOM 2007 R2 Reporting Services is completed, you then need to rename the local group modified at the start of this page back to what it was beforehand (example below):
2. Open the services snap-in and if the startup type for the System Center Data Access Service is set to Disabled, change it to Manual.
3. As an administrator, open a Command Prompt window , change directories to the installation folder, and type the following:
ManagementServerConfigTool.exe AddRMSNode /vs:<VirtualServerNetbiosName> /Disk:<VirtualServer Disk Resource>
VirtualServerNetbiosName is the Network Name resource allocated to the same cluster group. The value you enter for VirtualServerNetbiosName must be the value that appears in the Name box on the General tab of the Properties dialog box for the Network Name Cluster resource.
VirtualServerDiskResource is the disk resource allocated to the cluster group being used to create this Virtual root management server. The Disk location can be found in the results pane of the properties for the RMS application.
Installing SCOM 2007 R2 Reporting into an SQL 2008 R2 Environment
If you are installing the SCOM 2007 R2 Reporting Services into an SQL 2008 R2 environment, ensure you have renamed the local SQL group by removing the _50 section from its name on the SCOM server as outlined near the start of this document (see below for a reminder):
- On the SQL Server Reporting Services server, rename the local group SQLServerReportServerUserlt;hostname>$MSSRS10_50.<SQLInstanceName> to SQLServerReportServerUserlt;hostname>$MSSRS10.<SQLInstanceName>
Once the SCOM 2007 Console installation is completed, re-run the installer again and select the ‘Install Operations Manager 2007 R2 Reporting’ option
Within the ‘Operations Manager 2007 Reporting Setup’ window, when selecting components to install, DO NOT install the ‘Data Warehouse’ component if you are installing into a Windows SQL 2008 R2 instance, if installing into an older version of SQL, then leave all components selected and continue on
When prompted, enter the credentials for the ‘Data Warehouse Write Account’ (srv_scom_datawrite) and select ‘Next’
When prompted, enter the credentials for the ‘Data Warehouse Read Account’ (srv_scom_dataread) and select ‘Next’
Move through the remaining menu’s selecting the default options until you see the ‘Install’ button and then press this to initiate the reporting services installation
When the installation of SCOM 2007 R2 Reporting Services is completed, you then need to rename the local group modified at the start of this page back to what it was beforehand (example below):
- SQLServerReportServerUserlt;hostname>$MSSRS10.<SQLInstanceName> back to original name SQLServerReportServerUserlt;hostname>$MSSRS10_50.<SQLInstanceName
This completes the installation of SCOM 2007 R2 Reporting Services into an SQL 2008 R2 environment and also brings to an end the final chapter of my 6 part series on 'Clustering the SCOM 2007 R2 RMS Role on a Microsoft SQL 2008 R2 Cluster'.
Hopefully somebody will find this series helpful and it will assist you in working through the numerous pitfalls of carrying out this type of installation.
Fantastic article. I have followed every step and have successfully instlled an RMS cluster, which failsover like a charm.
ReplyDeleteI am having a problem where l install an agent from the console, but it always stays in the pending state.
Similarly if l do a manual install, l never get the server to appear in pending so l can approve it, even though l have changed the security settings to allow manually installed agents.
Any advice?
Hi g00ner, glad the blog posts come in handy. Its not easy trying to cluster the RMS role on an SQL 2008 R2 cluster so was well worth sharing my experiences on it!
ReplyDeleteIt sounds like your agents stuck in pending might be related to your SPN configuration. I think you may even have some duplicate SPN's in there and this is a common reason for agents held in pending state when using an RMS cluster.
Also, check the 'Operations Manager' event logs on both the servers that you have deployed the agents to and on your SCOM management servers for more information.
You will find the answer you are looking for from one of the following 4 mlinks below:
http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/7efbe8dd-f211-4bbc-a309-693d7a1a3a90
http://social.technet.microsoft.com/Forums/en/operationsmanagergeneral/thread/6e15c4ad-4f79-4bbf-8d84-5312624eb28e
http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/1b0708c1-6111-4a71-8064-cb8fcb82f0e8/
http://blogs.technet.com/b/smsandmom/archive/2008/03/13/opsmgr-2007-agents-stuck-in-pending-management-with-event-id-21016.aspx
Thanks Kevin, the fourth post did the trick.
ReplyDeleteI must be missing something, but why is the command shell excluded from the install? I can't run any SCOM Powershell script on the RMS?
ReplyDeleteHi John,
DeleteThanks for the comment.
To answer your query, the command shell is part of the User Interfaces deployment and can be deployed as normal once the RMS role has been clustered.
A couple of things to point out though. In SCOM 2007 R2, it's recommended to have a second Management Server to point your agents at that is separate from the RMS (standalone or clustered). With this in mind, then I'd keep the Web Console and most of the user interface features on your secondary management server as opposed to your RMS cluster.
Also, unless there's an absolutely compelling reason to build a new SCOM 2007 R2 RMS cluster, I'd say to you don't bother. Instead deploy SCOM 2012 and use the new Resource Pool functionality that provides HA out of the box. Plus, migrating from a SCOM 2007 R2 RMS cluster to SCOM 2012 at a later date will prove tricky.
Hope this helps,
Kevin.
I've followed your steps and everything went great, Thanks. Right now I am facing another problem, Both nodes of the cluster will ran out of warranty very son and I need to replace them. would it be possible to add two more nodes to the cluster and remove the original ones without any problem?
ReplyDelete