Message storm occurs after deploying "Forward message changes to service desk" policy

This type of problem may occur when creating and deploying a WMI policy to monitor messages arriving on the management server and to run automatic actions for messages matching conditions defined in the policy. This is a technique often used to enable matching messages to be forwarded to an external application (such as Service Desk, an email program, a page application, etc.

When defining such policies care must be taken to ensure a message 'loop' cannot result. It is a rule that every policy MUST send a message when an automatic action succeeds or fails (or both). Typically, in WMI policies designed to forward mesages to external applications, a message is only sent if the automatic action fails. If the automatic action for one message fails, then a 'failure' message will be generated by the WMI policy and sent to the management server. This 'failure' message will then arrive on the management server and be treated the same as any other message -- it will be examined by the WMI forwarding policy. Therefore, care must be taken to ensure that these 'failure' message do NOT match the conditions of the forwaring policy. If they did match, the forwarding policy would run an automatic action to forward the 'failure' mesage to the external application and if this automatic action also failed another 'failure' message would be sent, and so on, until the problem with the automatic action was corrected. This would cause a 'loop' and a 'storm' of messages.