| Deployment Issue | Possible Cause | Resolution |
| Nodeware service is stopped |
Security software interference
Agent can’t find the Customer ID (lack of the customer id will not prevent installation of the MSI because it will try to read the ID from the msi filename, but it will prevent registration) |
Start/restart the Windows Service
Contact support@nodeware.com |
| Agent not installing |
Security software blocking installation
Customer ID not identified in the script. |
See Third-Party Software section
Enter the Customer ID in the script. If that doesn’t work, open the Registry Editor (Regedit) and navigate to HKLM\SOFTWARE\Nodeware\Agent and set the value of CidData to the desired Customer ID. |
| Agent not in dashboard | The UUID wasn’t registered because Customer ID not found or incorrect or Security software blocking full installation | Contact support@nodeware.com |
| Operational Issue | Possible Cause | Resolution |
| Asset w/no Score | Scans have not completed | Issue a rescan and wait for scan to complete (up to 3 hours) |
| No Recent Data | Nodeware has not received any data from the asset in the last 30 days. The agent stopped reporting. |
Check that the Agent service is installed and currently running.
Restarting or starting the Agent service should bring the asset back online |
Comments
0 comments
Article is closed for comments.