Powershell save output of batch file to variable

Dear user

There are a few differences when using Powershell via PRTG:

• Unless you use the security context of the sensor's parent device, the shell runs with the local system user. This can affect the output.
• Since the PRTG probe is a 32 bit service, it starts the 32 bit Powershell. Script execution (Set-ExecutionPolicy) must be set for this Powershell version as well.
• Because the PRTG service has no GUI context, it cannot run anything accessing the GUI. However, file output itself is possible.

Please check if you can isolate the issue.

Hi,

thanks for your answer, I already considered these things.

I used local system as well as the credentials of the parent device, both had the same result. (Although security context should not matter, as this script only uses the Navseccli to connect to our EMC Storage)

I tested the Script in both 32 and 64bit powershell, both worked for me (on the command line).

The script does not access any gui objects, it can be run totally headless.

I am kind of stuck here, because, at the moment, I don't see any particular reason, why the script should not work. Are there any differences, how PRTG runs powershell scripts (besides the ones you mentioned)?

Thanks,

Matthias

Dear user

Please expand your script to include more extensive logging. Please also enable the "Write Exe result to disk" option in the sensor settings and review the according log file. It is usually located in C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors). Are you getting any useful information?

Hi,

i changed the powershell script to only run the bactch file and not to save the output to $output.

It seems like the batch file is not run at all because in the sensor logs I get zero output.

I checked permissions and Local System has rights to execute the script.

So, the batch file is not executed at all, but I can't find a reason why in the logs.

BR,

Matthias

Dear user

Which sensor message are you getting in PRTG?

There are no sensor error messages, this is the output of the sensor from the log files:

OUTPUT 0:Hardware OK Result:

You can find the script here: http://pastebin.com/CqwhQwk6 (If you want, I can paste it here, as well!)

KR,

Matthias

Dear user

The script seems to have multiple statements which output something to the console. Please make sure that during the program execution, just one single line is written to the console, in the format

value:message

Are you now getting the desired result? If not, please do it reversely: Begin with just a fixed output, like

write-host "1:Okay"

and work from there, expanding the script step by step.

Hello,

these multiple outputs were for debugging reasons (I tried to look into the sensor logs, if $output contains something, which was not the case).

In the beginning, the script output only occured after "' PRTG Sensor condition", but it did not work, because $output doesn't contain anything.

For some strange reason, PRTG does not run the batch script at all...is there some kind of security setting, which prevents the script to run, when used in a powershell sensor?

Dear user

Please contact [email protected] Please describe the issue and include screenshots of the Exe/Script sensor. We need

• The sensor overview tab
• The sensor logs tab
• The sensor settings (if necessary, multiple screenshots to cover all settings)

Please capture the complete PRTG interface in any screenshot, as a cut-out removes important context.