The title of this post is the issue I'm trying to write about in Operations Manager 2012 Help. The more I dug into it, the more complicated it became. Not being a management pack author, I had never thought too much about references and what that means to things you might do in the Operations console, such as set an override or create a group.
Anyway, the following is what I came up with for the basic guidance to an admin (not an MP developer):
When you create a group, you save it to an unsealed management pack. However, an element in an unsealed management pack, such as a group, cannot reference an element in a different unsealed management pack, such as an override or a view. If you are going to use a group to target an override or scope a view, you must either save the group to the same unsealed management pack as the override or view, or you must seal the management pack that contains the group.
If you save the group to the same unsealed management pack as the override or view, you can only use that group for overrides and views that are also contained in that unsealed management pack.
If you seal the management pack that contains the group, you can reference that group from other unsealed management packs. However, you cannot easily change any group settings in the sealed management pack or add new groups to the sealed management pack.
Before you create any groups in Operations Manager 2012, you should plan what groups you will need, the purpose each group will serve, and how to save the group in a manner that will allow it to be used for its intended purpose.
This is actually an open question to you all. :)
It's common for us to say our audience is the IT pro. But "IT pro" is a lazy shortcut to refer to a wide variety of people and positions. Does every IT pro know how to configure and manage permissions for SQL Server databases? Not necessarily, but the IT pro who uses Operations Manager should. So rather than just relying on the amorphous "IT pro" label, I think we should provide a list or overview of the skills and knowledge you need to successfully install and use Operations Manager.
Think about when you first started using Operations Manager -- what did you need to know about SQL Server, IIS, Windows Server, Active Directory, DNS, PowerShell...? About anything? If you were going to hire someone to set up and run Operations Manager in your environment, what skills and knowledge would you expect them to have? Please click "Email Blog Author" over there on the right and let me know your thoughts!
Edited to add: Just to clarify, I'm looking for the expertise with other products and technologies that you need before getting started with Operations Manager.
The past few months have been all about the Operations Manager 2012 beta release, which, of course, I couldn't blog about while it was still in development. Now it's live, w00t!
The documentation is available on the download site, but we also put it on our TechNet library-- Quick Start, Deployment Guide, Operations Guide, and Supported Configurations. The Quick Start is complete for beta, giving you a set of procedures to try out Operations Manager starting with a clean stand-alone install. The other documents are works in progress -- there will be a lot more content in them by the next release.
And something new...flow diagrams for upgrading an Operations Manager 2007 management group. Interesting viewing, even if you're not upgrading any time soon.
Check them out and let us know what you think. (There's an email link to the writers' team at the bottom of the flow chart. Actually, that email link is at the bottom of every page in our documentation set online for beta - we really do want to hear from you.)
What else do you do with Operations Manager that you think this type of diagram would help you with?
(edited to add tags)