Hi
Thanks for the feedback :), pleased to see it works for you.
I wanted to see if I could get a PowerShell script to run without specify HASH and HASHVALUE, the example in the documentation of external:everyscan:sync:fsmon.vbs doesn't seem to work for .ps1 scripts, I assume because you need to use the powershell.exe process to call the script.
Correct - if there's no default handler, you need to specify the process.
I had a lot of trouble with the optional arguments and settled for documenting the guaranteed way it works! I'll have another look and see if I can make it clearer.
Longer term, I'd like to make the hashes mandatory - it makes sense when deploying stuff to many servers to use them, in case the web server is compromised or returning error pages.
Zak
From: Brandon Dale [mailto:BDale at kitchengroup.com.au] Sent: 30 April 2016 10:15 To: Beck, Zak <zak.beck at accenture.com>; xymon at xymon.com Subject: RE: Windows PowerShell client v2.15
Hi Zak,
Just wanted to say the new externals functionality is awesome and makes everything easier, I have converted one of my PowerShell scripts to write the file in the expected format using the HASH and HASHVALUE and it all works as expected - very cool.
I wanted to see if I could get a PowerShell script to run without specify HASH and HASHVALUE, the example in the documentation of external:everyscan:sync:fsmon.vbs doesn't seem to work for .ps1 scripts, I assume because you need to use the powershell.exe process to call the script.
In the documentation it says this "If PROCESS is used, HASH, HASHVALUE and ARGUMENTS must be specified. " but I decided to try it anyway without specifying them and it seems to work fine, here is an example:
external:everyscan:sync:test.ps1|powershell.exe|-file "{script}"
So the documentation doesn't seem to be completely clear on how you run a PowerShell script without the HASH and HASHVALUE specified.
Regards,
Brandon.