I have done some pretty extensive research and cannot find something comprehensive enough to tell me how to systematically do the following.

1. Collect information via powershell and based upon this data change state in a monitor. (actually this part works)
2. Pass data collected using the PropertyBag API and that shows when exploring to this in the health explorer to a notification

So what I have researched and found so far.

• Alerting subsystem has a VERY limited subset of information with which to draw upon (primarily the custom fields are it)
• Monitor scripts do not generate alerts, they are reacted to and then generated.
• Rules seem to be capable of more but do not affect state.
• Scripts that are used via command channels can do some of this but there are a lot of replies (posts) that say that the methods people post cause multiple iterations of the same alert to be generated.  And in some rare cases there is a delay or inconsistency in generating the alerts

I didn't think what I was looking to do was that hard.  Apparently there is still some missing logic in how the monitoring occurs in SCOM.

To me, if you have such a robust system to allow scripted monitors to determine state that information collected in that determination would not have value in the alerts and subsequent notifications to key personnel.

Daren

Property bags are just key- value pairs we use in workflows. Just like any other data ( perf counter value etc) they are  generated and destroyed   at the rule / monitor.  If you need them later on then you  put them in alert description or  assign the data  to a custom field so you can reference them.

If you need  state changes and granular control on property bag all I can think of is  generating event containing property bag   and   alert based on the vent not on the state change which should refer to the same propertybag data