System Center 2012 Availability

The last month more and more System Center 2012 product guides, addons and other stuff was released.
Also the availability of the 2012 suite to Volume License Cusomers was already known by the public.

This week at MMS (no I'm not attending) the announcement was made that System Center 2012 is now generally available. So the coming weeks and months, more in-depth product knowledge will be shared Technet, forums, blogs and other media. Now the MVP's can finally share what they know already.

Just read a blog where Microsoft introduced a new console for creating basic management packs for Operations Manager 2007 and 2012: http://systemscentre.blogspot.com/2012/04/visio-management-pack-designer-for.html

SCOM: 2012 Wish List

Last week I was present at the first SCUG (System Center User Group) meeting for this year. It was a great source of information. Two speakers from Microsoft USA were present to tell us about the application monitoring feature (AviCode) and Network Monitoring feature. It looks great and promising!

As SCOM 2012 is going to be released and everyone is wondering what new features it might bring, I would like to share my ideas/wishes for the next SCOM releases. I'm pretty sure these are not available in SCOM 2012.

• Remove boundary for sealed en unsealed MP's.
  • Microsoft Best Practices for SCOM conflict with available functionality in SCOM.
    
  • Using one management group all self developed MP's are unsealed and their is no way to include objects from those unsealed MP's in a distributed application.
  • Currently sealing is the only solution. However sealing breaks MP's in which MP templates are used. Yeeh!
    
• Light-weight Operator Console for better performance
  
• Scale down Authoring in Operator Console, move functionality to Authoring Console.
  
• Increase usability
• Decrease complexity
• Create intuitive GUI layer on top of current console.
• Ease up using the Authoring Console as it was easy to create MP's in MOM 2005 with the adminstrator console.
• Possibility to use templates in the Authoring Console.
• Allow role 'Author' to make use of the Management Pack templates. Currently only a SCOM Administrator is allowed to make use of them.
  
• Dynamic component groups for DA's from the GUI to avoid XML usage.
• Log file monitoring for circular log files
• Out of the box better alert message possibities (read property bag definition from script, alert message templates)
• Possibility to use XPath expressions in alert suppression or a GUI layer for xpath dummies, like $Data/Context/Params[Contains(Param[1],"Fatal"). This can be handy when monitoring error events in logfile
• Review the current class model. There so much classes now. Is this really necessary? The new Network Monitoring features add classes for each component and each brand. Why not using multiple discoveries for 1 class?

If you have other good ideas/wishes, let me know!