Based on the responses in several threads here, I downloaded and installed the PTFWinCertExpiration custom sensor. From Command line, it works PERFECT, returning the right number of days, however when I pass the parameters to the sensor in the web-interface, it fails. (I've copy and pasted, and manually typed both, to check for any accidental garbling)
I do notice that the only Primary Channels I see as options are Downtime and Execution Time, Value, as noted in the documentation, is not a choice.
Am I missing anything obvious? :(
For the record, this is for a code signing certificate, not a web cert, if that matters.
Article Comments
Hello raubrey,
thank you for your KB-post.
What exact error message do you get in the sensor within PRTG? Please note that it's possible to configure the "Write result to disk" option within the sensor's settings, this will generate a file with the actual output/error in the following path of the probe were the sensor was deployed:
| C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)\ |
Since you've mentioned that the sensor works from the command-line but doesn't work in PRTG this sounds very much like an account/permission/impersonation issue. Which parameters did you configure in the sensor's settings? It should look like this:
| -h=%host -t=THUMBPRINT -u=%windowsdomain\%windowsuser -p=%windowspassword |
This way PRTG will replace this parameters as defined in the parent object (or inherited), make sure that in PRTG the Device's Address is correct and that the Credentials for Windows Systems are correct (or are correctly inherited).
It may be able to run the sensor without providing an username and password as parameter if you use the security context of probe service and run the PRTG Probe Service with account allowed to log-in both on the probe and remote system. The default Local System account will most likely not have this privilege.
Best Regards,
Luciano Lingnau [Paessler Support]
Aug, 2016 - Permalink
Luciano,
Thank you for the quick reply! I was hoping to get around passing credentials, but then I realized that since the cert is in the Trusted Publisher store, I can check locally instead of having to pass around. Changing the server I pointed to allowed me to drop the credentials and it's all happy now. Thanks for helping me get the last piece of the puzzle together! :)
Aug, 2016 - Permalink
Hello raubrey,
thank you for your KB-post.
What exact error message do you get in the sensor within PRTG? Please note that it's possible to configure the "Write result to disk" option within the sensor's settings, this will generate a file with the actual output/error in the following path of the probe were the sensor was deployed:
Since you've mentioned that the sensor works from the command-line but doesn't work in PRTG this sounds very much like an account/permission/impersonation issue. Which parameters did you configure in the sensor's settings? It should look like this:
This way PRTG will replace this parameters as defined in the parent object (or inherited), make sure that in PRTG the Device's Address is correct and that the Credentials for Windows Systems are correct (or are correctly inherited).
It may be able to run the sensor without providing an username and password as parameter if you use the security context of probe service and run the PRTG Probe Service with account allowed to log-in both on the probe and remote system. The default Local System account will most likely not have this privilege.
Best Regards,
Luciano Lingnau [Paessler Support]
Aug, 2016 - Permalink