SolarWinds uses cookies on our websites to facilitate and improve your online experience. By continuing to use our website, you consent to our use of cookies. For further details on cookies, please see our cookies policy.
Hide this message
Updated June 22, 2017
This article describes how to determine if the certificates bind and connect to a SolarWinds agent and to determine which database tables are defined in the agent provision file.
The SolarWinds Orion certificate is either in MD5 or SHA1 and should match with the SolarWinds agent provision file that signs it.
The SolarWinds agent provision file is defined in the database through the following tables:
NPM 12.0
Perform the following steps to verify that the certificate and agent matches:
Perform the following steps to determine the defined tables in the SolarWinds Agent Provision file:
SELECT TOP 1000 * FROM [dbo].[AgentManagement_Pkcs12Certificates]
http://<orionservername>/Orion/AgentManagement/Admin/ManageAgents.aspx
).C:\ProgramData\Solarwinds\Logs\Agent\
.SolarWinds.Agent.Service.exe xxxxx.xxxx.log
file in Notepad.loadCertificate - added Agent certificate to SSL store
handshake info : cipher name [ECDHE-RSA-AES256-SHA], cipher version [TLSv1/SSLv3]
cipher: NULL
.If the SolarWinds agent is not set to auto =-update, the MSI installer will not be able to find the temp cache file to uninstall. See Fix problems that block programs from being installed or removed if you run into this issue. Perform the following to force the old installer to update: