Question: How do you disable a rule in a sealed MP and show that rule is disabled?
This is another question that I encountered with OpsMgr aka SCOM 07 (I am counting…!).
Facts:
1. All the rules have default Yes/No in the Enabled column.
2. You wouldn’t be able to disable/enable a rule if the Management Pack is sealed.
The preferred way to enable/disable a rule of a sealed MP is via an override, which means changing the Enabled value to True/False. It is a pain in itself because:
1. God knows how many rules that you have to disable/enable, not to mention changing other parameters, but that’s a problem for another day.
2. When you create an override, there’s no easy way to see if the override has been applied because (a) it is still greyed out or not greyed out in the console and (b) the Enabled by default value has not changed. I know, I know… you may say it’s cosmetic, but wouldn’t you like to be able to point out straight away if a rule is enabled/disabled – without too much efforts, that is.
OK, let’s solve one thing at a time.
You CAN actually enable/disable multiple rules. Boris Yanushpolsky has created this awesome tool called Override Creator which allows you to enable and disable multiple rules at once. That’s about it. I reckon it saves you half the work, at least. The other half? No such luck, my friend, you gotta do it manually
To view all the overrides, use Override Explorer. This simple tool lists all the overrides applied in a Management Pack or in a server. There is no so-called a user manual, but the application is quite intuitive and after clicking around several times, I found my way.
Another tool that I found useful is the MP Viewer. The tool will give you an overview of a Management Pack: overrides, dependencies, views, etc. Works on both sealed and not sealed MPs.
Before I reveal the solution for No2, let me say this: this is experimental only and it is not in production. I have not yet investigated the full impact of what I did and I am not sure what sort of implication it may bring. I just want to show you what’s possible. It would be great if someone from the System Centre Community (http://systemcentercommunity.com/) can blog about this and gives a full-on explanation, but at the time of writing, no such thing.
All right, having said that, let’s dig.
When you go to the Authoring mode and check out the Rules under Management Pack Objects, you would see something like this:

Collect Transaction Log Free Space (MB) rule in SQL Server 2005 (Monitoring) pack is disabled by default. You wouldn’t know that this rule has actually been enabled via an override.

So I went to the OperationsManager database and run the below query:
SELECT RuleName, RuleCategory, RuleEnabled
FROM Rules
WHERE RuleEnabled =0
AND RuleCategory =’performancecollection’
AND RuleName like ‘%transactionlog%’
Here’s the result:

So we want to enable the Microsoft.SQLServer.2005.Database.TransactionLogSpaceFree.Collection rule.
UPDATE Rules
SET RuleEnabled = 4
WHERE RuleName =’Microsoft.SQLServer.2005.Database.TransactionLogSpaceFree.Collection’
Why 4? Any value above zero in reality will enable the rule (1-4). There’s no formal explanation of these numbers (URL? White paper? Books? Blogs? C’mon, someone must have known something!), but my observation concludes the following:
0 – rule is disabled
1 – not used for anything
2 & 3 – for Windows Server MPs
4 – for others (System Center MPs, SQL Server MPs)
So number 4 it is!
Here’s what it looks like after. See my point about visibility? Now you can tell straight away if the rule is enabled.

Other Reference:
Jakub Olesky – Overrides