Execute a .bat or .ps1 script file on a node

Hi,

I am trying to create an alert which will triggers when the Solarwinds detected that the services that it monitored is down. The things that I am trying to achieve is:

1. I have created a SAM template which monitors a Windows service (e.g. edp.exe)

2. If the service is down (it can only starts back if certain steps are fulfilled), it will trigger a script to run on the node. The script will

Delete a file
Then start the services

3. End

I have tried this, simulate on the newly created alerts and it was successful (FYI, the script is located on the Solarwinds \ drive. But on the actual node, it does nothing. Tried these few command, does not work, any help would be good. Thanks.

Below script used - Does not work

Powershell.exe -executionpolicy remotesigned -File \Scripts\EDPFix.ps1 -computer ${N=SwisEntity;M=Caption}

Powershell.exe -executionpolicy remotesigned -File \Scripts\EDPFix.ps1

Find more posts tagged with

external_scripts

external_program

script

Alerts

Accepted answers

All comments

mark.gover

Have you tried the bypass option instead of remotesigned on your script?

Powershell.exe -executionpolicy bypass -File \Scripts\EDPFix.ps1

adam.beedell

This is hard to answer because security stuff will vary what works

If you can run it from RUN on the SW box, then it should run.

You've got remotesigned on here, so hopefully the script is signed or it wont do anything

Next up your script is going to try and connect from that box to the target server, if you're connecting via remote PS it'll need remote PS enabled, etc. It doesnt seem like your passing any credentials in, so it's going to try and operate it as the system account maybe, if so then the system account needs those permissions on the target box, else swap in some creds.

There's a cool trick where you can set a SAM monitor to fix the problem, and have an alert un-disable it, and have that node monitored with an agent to skip some of the permissionsey issues, but this takes some real looking after

oithim_yew

Just tested, doesnt work.

chad.every

I'd add a PowerShell component monitor to that application template.

Simply have the script follow this logic (I didn't build the script but you'll want the last line identical to what i have)

...Stuff to detect if process is stopped

...if stopped, delete file

...start process

Write-Output "Statistic: 0"

The last line simply returns 0 so this component will also stay green. It's there to auto-remediate the problem.

Alert Actions to remote hosts have a large set of work-arounds needed based on security/environment (as seen by previous comments). So if you already have the SolarWinds Agent deployed AND the application templates run natively on that remote host because of the agent, just use an extra component monitor to fix it (since the agent handles all of the remote execution part)