X.509 Certificate Expiration

This will find all X.509 certificates from a specified issuer (wildcards allowed).

There are 3 arguments that need to be set.

  1. Issuer Name: I entered a 'SolarWinds' to find all X.509 certificates issued by SolarWinds. No need for wildcards as that is built into the script itself.
  2. Days until Warning: This should match the warning thresholds set on the component monitor itself. It only is needed here so the certificates that are expiring are entered into the script message output.
  3. Days until Critical:This should match the critical thresholds set on the component monitor itself. It only is needed here so the certificates that are expiring are entered into the script message output.

**Note: The Orion Agent is required unless you update the 'Execution Mode' in the component monitor to leverage WinRM/PowerShell Remoting**

The script argument line outlined in red below is what needs to be updated. **Remember, there needs to be a comma between each of the 3 entries.**

Depending on how permissions on setup, you will probably need to set the credentials for monitoring too.

pastedImage_0.png

Thanks to dcrh​ for the assist with DateTime globalization!

Parents
  • The easiest option is to use the Orion Agent. It handles the communication between the remote server you want to monitor and the Orion server.

    If you did not want to leverage the Orion Agent, you would need to configure both the Orion server and the Remote Server for Windows Remote Management (WinRM) SolarWinds has a free tool that can help get this configured.

    FREE Remote Execution Enabler-PowerShell | SolarWinds

    Once enabled, you would need to expand the Component monitor and switch the execution mode from 'Local Host' to 'Remote Host.' Make sure the respective WinRM settings are in place and test.

    pastedImage_1.png

    Once the test is successful, it would execute the powershell script remotely on the remote server and return the results.

    If you keep the component monitor set to 'Local Host' without the use of the Orion Agent then all of the scripts are run locally on the Orion server, even though the Application Template might be assigned to a remote server.

    I've found it easiest to just install the Orion Agent, since there are other parts of monitoring that can also use it outside of the powershell template above.

Comment
  • The easiest option is to use the Orion Agent. It handles the communication between the remote server you want to monitor and the Orion server.

    If you did not want to leverage the Orion Agent, you would need to configure both the Orion server and the Remote Server for Windows Remote Management (WinRM) SolarWinds has a free tool that can help get this configured.

    FREE Remote Execution Enabler-PowerShell | SolarWinds

    Once enabled, you would need to expand the Component monitor and switch the execution mode from 'Local Host' to 'Remote Host.' Make sure the respective WinRM settings are in place and test.

    pastedImage_1.png

    Once the test is successful, it would execute the powershell script remotely on the remote server and return the results.

    If you keep the component monitor set to 'Local Host' without the use of the Orion Agent then all of the scripts are run locally on the Orion server, even though the Application Template might be assigned to a remote server.

    I've found it easiest to just install the Orion Agent, since there are other parts of monitoring that can also use it outside of the powershell template above.

Children
No Data