Broadcasting live from Redmond, Washington
When you create overrides for a Management Pack in Operations Manager 2007, it's a good idea to put them into a custom Management Pack instead of the Default Management Pack:
For example, if you use the Exchange Management Pack, create an "Exchange Overrides" Management Pack and store all your Exchange overrides in that Management Pack. You'll probably want one of these override Management Packs for each Management Pack you use (assuming you plan to apply overrides to it, of course).
If you don't store your override in an override Management Pack, the override automatically goes into the Default Management Pack. This won't cause problems during day-to-day operations, but makes it difficult to remove the Management Pack later. In particular, it creates a dependency between your Management Pack and the Default Management Pack that is not removed even when you remove the overrides:
I talk more about how to remove this dependency in this post.
New Comments to this post are disabled
About Jonobie Ford
I joined Microsoft in October of 2006, right in the middle of a flurry of Ops Manager activity. After joining, I started work on planning for the Management Pack guides and later wrote the Active Directory MP Guide. Prior to joining Microsoft, I was a writer at IBM in the Tivoli brand, most recently for the Response Time Tracker product, although I also worked on the Enterprise Console product.
I now work as the content publishing manager for System Center Capacity Planner, System Center Service Manager, and the Connector and Cross-Platform extensions for Operations Manager.
