I had this on my list of things to blog about but it is worth pointing out a key area that confuses people and the KB tells you not to do.
If you want to just disable a rule then it looks logical to pick the first object on the override list – Disable the ObjectName. This does actually work but when you do it it just disappears. There is no choice about where to put the override. What it does do is put it in the Default MP. This is against Microsoft best practice which says that you should create a new unsealed MP for overrides belonging to a sealed MP. So for instance you would create an MP called Exchange 2003 Overrides for the Exchange 2003 MP and so on. You can create the MP on the fly when you do the first override or go to the Administration tab and create it under Management Packs. I prefer the second as I can then create the new MP with exactly the same name as the original MP and put Overrides at the end. In an alphabetical list you will see which MPs have override MPs and which ones don’t. If you want to see all the override MPs together you can sort on management packs to show all unsealed ones.
The way to disable a rule is to use the Override option which gives you all the options you can override and for the Enabled parameter change that to False and choose the unsealed MP to save it.
The KB also mentions that the override may need changing in multiple places. Kudos to the SystemCenterForum.org team as their spreadsheet is referenced in the KB.
It does not mention if this is fixed in SP1.
- Posted in: System Center Operations Manager 2007