Rule Engine Failing to Add Script Monitor

Hi All,

I have just created a script monitor which I would like to deploy out to all windows computers and the only way I could see to do this in bulk was to create a new rule in Rule Engine.

Currently the rule has the following criteria and is set to match on all criteria:

Criteria	Condition	Value
Type	contains	Windows
Vendor	equals	Microsoft

The action for the rule is as follows (the name of my script monitor is 'Service Account Audit'):

Action	Action Properties
Associate a Script Monitor	Service Account Audit

When I choose the option to Re-run the rule against "All Windows Devices", I can see in the log called discoveryLogs_0.txt the following message for each device it tries to associate the monitor to:

*************************************************************************************************

[15:32:39:127]|[07-21-2017]|[com.adventnet.opmanager.discovery]|[INFO]|[4202]: RULEENGINE::

******** Rule Engine Evaluation for the device <DEVICE NAME> starts........ **********

Discovery Tempalte Id : 301 Condition is : ALL

Rules evaluation starts........

Rule ID : 601 [DEVICEPROPS : TYPE CONTAINS Windows] Present value - Windows 7 ---> Evaluation Result : true

Rule ID : 301 [DEVICEPROPS : VENDOR EQUALS Microsoft] Present value - Microsoft ---> Evaluation Result : true

Rule Engine SATISFIED!

Performing the Actions.........

Script Monitor Templates not associated{1185=Service Account Audit}

Time taken to execute Rule Engine is 16ms.

*************************************************************************************************

So the rules are confirmed to be satisfied for the device, however the action of associating the script monitor never succeeds.

I will also mention that I can manually associate the script monitor to individual devices successful and it works well, however we have over 1000 devices in inventory and I do not want to have to go through and try to pick out the windows machines manually.

Would be interested to hear where I'm going wrong from anyone who has managed to get this working!

Thank in advance,

Rick