That would make script rules and monitor creation so much easier and less error prone.

Thank you :-)

It would be great to be able to configure the default value of a reference Alias in VSAE. The function within the Authoring Extensions always chooses the first letter of each node in the XML Name.I'd like to change it to use my default..
For example, If I add Unix.Authoring.Library, the default value of the alias will be UAL, in each new project....

I have had multiple customers ask if we can dynamically compile product knowledge.

By this I mean an alert is raised within Operations Manager, the knowledge associated with the alert could be tailored for a specific Rule or Monitor AND Discovered Instance.

This would then allow such knowledge as internal escalation procedures to be concise and contextual.

A suggested example of this could be applying some sort of condition detection using the Full Path Name as a string and if it matches, display certain text for that specific instance.

visual studio tools such as mp simulator are not usable now. Improving these developing tools and the extension itself, will make authoring new management packs a more easier job.

Currently only vbs is supported, when creating Agent based task. For now, PS is mostly installed on all recent OS please implement support for adding Powershell scripts here.
You can mark it somehow- to distinguish VBS/PS based tasks, so users are not running ( or know and accepts) it on systems which do not support PS.

If you open a VSAE project on a new machine, the version number for the MP (if using Auto-increment) will reset to the default 1.0.0.1. However this Mp could be on version 1.0.41 and won't install unless you rebuild the soltion 40+ times or turn off Auto-Increment.

It would be nice if we could set the value in the deployment tab of the MP properties and VSAE increment from that number on the next build

Brian Wrens documents and MVA course are excellent, however they could be complimented by some examples (i.e. how to create a relationship based on a reg key etc). Information of this type currently needs to be gleamed from forums, Community MPs and at times just hours of experimentation. Which takes a long time and is extremely frustrating. Surely there is enough content in the standard Microsoft MPs to be able to quickly create a library of examples. I

Currently we could create web tests in Visual Studio and run them from agents in GSM, but it works only for public facing web sites. That would be awesome for internal use as well.

Microsoft would offer a new great feature to SCOM and would have the opportunity to sell more VS Ultimate Editions ;-)

Thanks,
Patrick

like a wizard to select which MP (monitors , discoveries, and rules ) to be run on which Group of servers.

so customer just want to monitor the base OS for a group of servers and not to discover or be alerted for other MPs
so that will scope the alerts and discovers more !

When import data to snippets data can be ruined randomly

For example, we have Columns:

Number
Interval
URL
ProcessDataMode
DayWindow
IS
XmlEnabled
Xpath
Operator
XmlValue
NumSamples
StatusCodeText
XMLText

And data for it

1,60,http://mss-mmvb4/,<Daily><Start>09:15</Start><End>22:00</End><DaysOfWeekMask>62</DaysOfWeekMask></Daily>,108MC,true,/Root/source/@connectionStatus,Equal,Connected,-,-

After importing to VSAE values will be in random columns. No difference if we have column names in csv in 1 line. Its a bug and it forces me to edit data in vsae, not in excel, for example

These is screen shot with error , as you can see all data above red line is wrong !

https://yadi.sk/i/jIHrtYOiq4LnJ

If you create a custom author role, users in that role can't use the MP Templates, only MP Objects.

(In that case the users are advanced Operators as well)

/patrick

If you use a customized author role with no selected views and folders the user in this role (and only in this role) still sees all folders (empty) in the monitoring pane.

VSAE now can only import csv files. I think it should export to. It will be very great

I created rules to alert when users were added to Domain Admins, Schema admins etc. The company wanted separate subject lines per group. A simple Subject: [USER] added to [GROUP] would have prevented me creating loads of individual rules.

Within the GUI there is no easy way to create PowerShell script monitors and rules. Please add a GUI driven wizard to create those.

You can "get-scomrule" but not "set-scomrule". I had to create a lot of rules recently and it took ages. (This would have been mitigated by being able to add variables to the subject line of an alert)

We need an option to associate components to each other to prevent an alert storm created by a failure of a central component.
For example if a central router on a remote location fails we get alerts from each component monitored at the location even though its still available locally.