We have been experiencing issues when trying to deploy the Orion Agent (for SAM use).
The following error occurs when the agent deployment fails:
"Agent connected to PAS but provisioning has failed, error code [0x5] - Access is denied. : Failed to create certificate"
The only way to see this error is to remotely connect to the host, launch the Control Panel then view the Orion Agent Settings, and manually enter the connection settings.
In addition to the agent installation failing, the same agent/node consistently keeps on trying to register and displays duplicate entries every few minutes in Manage Agents as shown in the example below:
How many duplicate entries occur you might ask? About 100 per day. The only way to stop the duplicate entries from showing up in the Manage Agents screen is to remotely connect to the target PC then manually remove the agent software from Programs and Features.
Facts:
- The SolarWinds poller server and each target host on the domain we intend to deploy the agent have the same time/date and are joined to the same AD domain.
- The credentials used by SolarWinds have local administrator rights to the target PCs and SolarWinds is able to poll the target PCs using WMI without issue.
- Network communication between the SolarWinds Poller servers and the agents are NOT blocked by any firewall -- SolarWinds is able to PING the target computers.
What we have tried:
1) Reboot the PC, same error occurs.
2) Delete the node from SolarWinds, delete the agent from the admin dashboard, then manually reinstall the agent on the PC and manually enter the connection settings. The same issue occurs.
3) Delete the node from SolarWinds, uninstall the agent from the PC, reboot the PC, delete all duplicate agents from the admin dashboard, wait about 5 minutes, then attempt and start all over again.
We have now seen this same issue several times. This issue seems to be random because we are able to deploy the agent without any issues to many other computers on our network. But this is now the 5th time we've seen this error over the past month.
I'm going to try to add in the agent via SERVER INITIATED mode and see what happens... standby.