Grant Fritchey (8/25/2009)
Nah, let's keep it on here. If the article wasn't clear, this can help to explain the issues for someone else.No, don't put in the name of a single server. You're right, that's not how it's supposed to work. This is from our local management pack:
-Microsoft.SQLServer.Library
6.0.6247.5
XXXXXX
That Reference Alias, that's what you need from your own management pack. I had a hard time figuring that part out too.
Thx again Grant. tantalisingly close.
I am using R2 for SCOM and the latest SQL(2005) MP.
For this exercise a new MP was created SQLa.
I can do everything EXCEPT enter parameters.
If the parameters are left out, I can save the new rule, no proplems.
I can also from the Properties of the rule, Edit the script and select Parameters from the little Target button. They work fine. I can then save the rule.
BUT, when I try to enter the two lines as mentioned previously, SCOM spits the dummy and won't save the rule.
So I went in to the XML for the new MP and can't find Microsoft.SQLServer.Library that looks like the example given.
Mine looks like:
Reference Alias="MicrosoftSQLServerLibrary6066480">
Microsoft.SQLServer.Library
6.0.6648.0
31bf3856ad364e35
So I cut out the MicrosoftSQLServerLibrary6066480 and get
$Target/Host/Property[Type="MicrosoftSQLServerLibrary6066480!Microsoft.SQLServer.DBEngine"]/ConnectionString$
$Target/Property[Type="MicrosoftSQLServerLibrary6066480!Microsoft.SQLServer.Database"]/DatabaseName$
That then saves OK! Seems like a strange string to paste in.
Let's see what populates.
Now to get the view working....
Thx,
John Bradshaw