There's a known bug of SCOM 2007 R2, when you're trying to create a subscription based on the value in any Custom field of alert.
This subscription won't work. Because when you save it, it is being saved as:
<ValueExpression>
<Property>Custom2</Property>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Critical Alert</Value>
<Version>6.1.7221.1</Version>
<Property>CustomField2</Property>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Critical Alert</Value>
Notice that if you do any change in this subscription in future, you have to do the same operation, because it always been saved in wrong way :)
This subscription won't work. Because when you save it, it is being saved as:
<ValueExpression>
<Property>Custom2</Property>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Critical Alert</Value>
in Notifications Internal Library management pack.
The solution is to export, update and import this management pack again as I did it in my previous post.
You should replace Custom2 to CustomField2 (in my example) and increase the version of management pack:
...
<ValueExpression> <Property>CustomField2</Property>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Critical Alert</Value>
Notice that if you do any change in this subscription in future, you have to do the same operation, because it always been saved in wrong way :)
Thanks for the post - saved me a lot of headaches.
ReplyDelete