I'm hoping my Operations Manager/Command Shell presentation during meeting #1 was helpful.

If you have any suggestions/comments/questions as to what you might like to see maybe in a future session, leave a comment here!

Marco

Scripting in SCOM, like creating a custom monitor or rule that utilizes your custom VBScript? Or how to fire off alerts in VBScript in a rule or monitor? How to use property bags? Could you give an example of what you'd like to see?

thank you,

Scott Moss

I think how to create custom monitor / rule that utlizes custom VBScript that this script may generate alert / create performance counter:

1.  

Set oAPI = CreateObject("MOM.ScriptAPI")

2.

Set oBag = oAPI.CreatePropertyBag()
Call oBag.AddValue("instance", strDirPath)
Call oBag.AddValue("perfValue", nResult)
Call oAPI.Return(oBag)

And in the rule

$Data/Property[@Name='instance']$

$Data/Property[@Name='perfValue']$

 3.

How to use parameters in scripts

e.g.

 set oArgs = WScript.Arguments

srtSever = Split(oArgs.Items(0),",")

oArgs.Items(1) = 1

oArgs.Items(2) = 2

Dont forget to format the Property Bag

Set oBag = oAPI.CreatePropertyBag(StateDataType)

Here are some examples of types of data for Property Bags.

oBag = CreateTypedPropertyBag(0)
property bag can be converted only to alert, it is not convert-able to anything else and would be ultimately dropped with such conversion request        

oBag = CreateTypedPropertyBag(1)
property bag can be converted only to event, it is not convert-able to anything else and would be ultimately dropped with such conversion request        

oBag = CreateTypedPropertyBag(3)
property bag can be converted only to state data, it is not convert-able to anything else and would be ultimately dropped with such conversion request

 Got it from http://blogs.msdn.com/mariussutara/archive/2008/01/24/momscriptapi-createtypedpropertybag-method.aspx

Hope that Helps