SCOM 2007 R2 Root Management server showing Not Monitored State in Ops Mgr Console

Question

Hello Experts,
In my Prod SCOM 2007 R2 environment RMS server state is "Not Monitored", But we are receiving alerts with limitation. By mistakenly I put Maintenance Mode while rebooting RMS server due to slow performance of the server.
Can anybody help me to revert back to the RMS Health state ?

Answer 1

We can identify the Performance Signature Data Collection Rules in this example by executing the following SQL Query. This query should be executed in SQL Management Studio against the Operations Manager database.
-- Return all Performance Signature Collection Rules
Use OperationsManager
select 
managementpack.mpname, 
rules.rulename
from performancesignature with (nolock)
inner join rules with (nolock)
on rules.ruleid = performancesignature.learningruleid
inner join managementpack with(nolock)
on rules.managementpackid = managementpack.managementpackid
group by managementpack.mpname, rules.rulename
order by managementpack.mpname, rules.rulename
This query will return all Performance Signature Collection Rules and their respective Management Pack name. A column is returned for Management Pack name and Rule name.
The following Performance Monitor Counters on a Management Server will provide information concerning Database and Data Warehouse write action insertion batch size and time. If the batch size is growing larger, for example the default batch size is 5000 items,
this indicates either the Management Server is slow inserting the data to the Database or Data Warehouse, or is receiving a burst of Data Items from the Agents or Gateway Servers. 
· OpsMgr DB Write Action Modules(*)\Avg. Batch Size 
· OpsMgr DB Write Action Modules(*)\Avg. Processing Time 
· OpsMgr DW Writer Module(*)\Avg. Batch Processing Time, ms 
· OpsMgr DW Writer Module(*)\Avg. Batch Size 
From the Database and Data Warehouse write action account Average Processing Time counter, we can understand how long it takes on average to write a batch of data to the Database and Data Warehouse. Depending upon the amount of time it takes to write a batch
of data to the Database, this may present an opportunity for tuning. 
Event ID 2115 A Bind Data Source in Management Group
http://blogs.technet.com/b/kevinholman/archive/2008/04/21/event-id-2115-a-bind-data-source-in-management-group.aspx
Niki Han
TechNet Community Support