
/filters:no_upscale()/articles/extension-manager-2010/en/resources/image10large.jpg)
Up to the year 2015, not much changed and soon Visual Studio 2015 was released. Which was basically only a compatibility support release for Visual Studio 2013. In the mean time Microsoft released support of Visual Studio 2013 for Visual Studio Authoring Extensions 2013 for System Center Operations Manager. The current version of MP Author is MP Author SP 5.

which was fixed in the later released service packs. In its first version, MP Author was a kind of buggy and also some basic functionality like editing an authored MP, PowerShell script support etc.
#VISUAL STUDIO EXTENSIONS MANAGER PRO#
This tool was / is meant for the IT Pro who gets wizard driven support for authoring management packs.
#VISUAL STUDIO EXTENSIONS MANAGER FREE#
Some time later, Microsoft discontinued to invest in this tool and started a co-operation with Silect, to build a free “successor” of the former Authoring Console called Silect MP Author. This way of authoring was very limited by some basic monitors, rules and health model. The idea behind was, to author MPs in a graphical way, utilizing Visio as a graphical interface and by pressing a button the MP was pushed to SCOM. Microsoft’s answer to this problem was a huge flop, called System Center 2012 Visio MP Designer VMPD and was an add-in for Visio 2010 Premium.

The downside of VSAE was / is that it is focused on experienced IT Pros or MP developers, but not for an average SCOM administrator because of the MP authoring knowledge needed – “You need to know what you do”.

Back in the days where MOM 2005 used to rule the monitoring world, you had these AKM management pack files which could not be changed or authored outside of MOM. If you have been working for some time with SCOM, you know there is a (long) history behind authoring MOM/SCOM management packs. I usually don’t blog about new releases of management packs or similar things, but this time I feel I have to do so.
