This is a known defect with the way the agent handles the vbscript being called within the policy's two conditions. From what I understand the agent lab is working on addressing this issue and there is no workaround/solution at this time.
"I am glad to inform you that the issue you are seeing is a defect on the Operations Agent (not on the ADSPI) which had already reported to us by a couple of other customers. Our Agent Lab is working on addressing it. I will contact the developer engineer in charge of this case to check what the investigation status is and I will let you know."
Just a suggestion - make sure that the updated vbscript that is being discussed in this thread has a different name and you call that script in the ADSPI policy. This way you won't run into any problem if HP releases a newer version of the script and it just simply overwrites what you have used.
Small update. I have got a hotfix from HP Support to address this issue. And a correction - the problem is in AD SPI and not the agent. The problem is that this policy shares a script with another policy, and that script has a bug in calling command line opcmon.