Archive for the ‘Management Pack Lifecycle’ Category

Don’t do it!

February 27, 2010 Leave a comment

Administrators that are new to OpsMgr can easily be lulled into a false sense of security and download Management Packs directly from the web from the administrator window in OpsMgr. I really don’t recommend it and Kevin Holman gave a great explanation of why it is not good practice on the Technet Forums.

Using this tool to directly import MP’s is a bad idea and a worst practice.

1. You need to manually download and read the guide FIRST.
2. You need to ensure you have handled any “before you import” activities from the guide.
3. The MP might include unsealed MP’s which are required, and unless this has changed – those do not come through the UI download.
4. The new MP might not be upgrade compatible with an existing MP in your environment and the UI will not tell you this.

I’d agree with Kevin in that what we need is a Management Pack notifier like we had in MOM 2005…. where it can generate alerts when an MP upgrade for an existing MP is avalable.


Management Pack Lifecycle

July 10, 2009 Leave a comment

It is interesting to see the number of threads starting about the Exchange 2007 R2 MP not working ….. especially when the actual problem is with OpsMgr administrators not bothering to read documentation or understand what they are doing before they do it … I’m not sure why Microsoft added the capability to import management packs directly into Operations Manager ….. but do people use this? And why?

Potential issues:
1) You can’t read the documentation – in fact, it doesn’t even download. The number of threads that state “Exchange 2007 R2 MP doesn’t work” is going to grow and grow ….

2) It doesn’t always work – the Client OS MPs (such as Business Critical Desktops) actually rely on an xml file that doesn’t get imported unless you download the MP and manually import.

3) It suggests that change management and testing don’t exist in many organisations. Given the issues with a variety of management packs do people really not test them in a dev environment before importing them? Especially given the inability to roll back an MP that does do something that you rather it didn’t.

To me it seems to be a quick way for OpsMgr users (especially those new to the product) to get themselves into a mess by importing way too many management packs way too quickly without understanding what they are doing or why. Or am I just being old fashioned in prefering to understand what I’m doing rather than just blindly importing management packs and trusting to luck 😉

Management Pack Lifecycle: