I use a custom sensor to monitor my windows certificate : WinCertExpiration.exe. It works on 2 windows server 2008 and 2012. But it doesn't work on a SBS2008.

When I write my command directly on the SBS prompt with all parameters (IP, certificate store name, account and thumprint) it works but when i use those parameters in PRTG, it say "certificate not found" but i search in the good certificate store !!

Have you an idea ? i think something block me on the SBS...

Article Comments

Dear maianoinfo

Please use the "write result to disk" option in the Exe/Script sensor to see the full output which PRTG gets when the script is executed. This might help with the debugging of the issue.


Feb, 2016 - Permalink

It write the same things as my sensor : "certificate not found" I try to install it on an ohter SBS server today and i have the same problem


Feb, 2016 - Permalink

Dear maianoinfo,

You are saying that the sensor works from the command prompt.

Have you tried adding the -u= and -p= parameters running it from PRTG?
These parameters can be used to supply credentials like those from the user account that can run the sensor with expected result from the command prompt.


Feb, 2016 - Permalink

yes it works in the command prompt and i use -u and -p in my sensor. for example i launch this command in the windows command prompt : wincertexpiration.exe -h=192.168.253.203 -s=CertificateAuthority -s=Disallowed -s=My -u=mydomain\user -p=mypassword -t=??123456789abcdef (the thumbprint of my certificate) and it return the number of remaining. when i use all parameters in my sensor : -h=192.168.253.203 -s=CertificateAuthority -s=Disallowed -s=My -u=mydomain\user -p=mypassword -t=??123456789abcdef, the sensor return "certificate not found"


Feb, 2016 - Permalink

I think that the "My" store for the user running the sensor from the command prompt differs from the "My" store for the account that runs the PRTG probe (by default the local system account)


Feb, 2016 - Permalink