I've come across others with this issue and nothing seems to work for me. I have a Powershell script that I'm trying to use as a custom sensor. The script is supposed to call TFTP.exe in the System32 folder to test retrieving a file from another server. Whenever it gets to that part is responds with

C:\Windows\System32\TFTP.EXE' is not recognized as the name of a cmdlet, function, script file, or operable program.

The script runs fine when I test it manually. I've confirmed the credentials that PRTG is using to run the script (via sensor settings) and I've tested the script with that security context. I've also check that the script is running elevated and it is. I've also verified that the execution policy is set to bypass for both 64 AND 32 bit versions of Powershell.

I don't know what else to check and can't figure out why I'm having such trouble doing such a simple task.

Any help would be really appreciated!

Article Comments

Hello there,

Try putting the executable into the same path as the Powershell script and adjust the call accordingly. Does it work then?

Kind regards,

Erhard


Oct, 2017 - Permalink

YOU DID IT! It works great when I copy TFTP.exe into the custom sensor folder for PRTG. I'm not sure why it couldn't access the system32 folder since UAC was turned off and the account being used was an admin. Either way, I don't care anymore because this works just as well.

Thanks again for the suggestion!


Oct, 2017 - Permalink