Why Are CYRISMA Agents Not Showing Up for Provisioning?
This guide explains how to troubleshoot and resolve issues when CYRISMA Agents fail to show up for provisioning after being deployed.
Written by Liam Downward
Updated at November 25th, 2024
- User Manual
- Self Onboarding Guide
- Agents
- The Cyber Risk Assessment Process
- PSA Integrations
- General Questions and Troubleshooting
- The Cyber Risk Assessment Process (Video Tutorials)
- Sales and Prospecting Articles
- CYRISMA Partner Portal Access
- Glossary
- API Documents
- CYRISMA Change Log
- Support Ticket SLA
- Billing Questions
Table of Contents
Problem Description
Newly deployed PCs were not appearing in CYRISMA for provisioning, even though the installation script successfully ran. The root cause was an error in the script's syntax, specifically with the formatting of the CYRISMA server URL.
Steps to Resolve the Issue
Inspect the Script Syntax
Review the deployment script carefully. In this case, the issue was found in this segment:
https:="" cc8b9cbb.cyrisma.com
- There was a double quote and space error.
- Correct syntax:
https:="cc8b9cbb.cyrisma.com"
Update the Script
Replace the problematic line in your deployment script with the corrected syntax. The updated script should look like this:
#!ps #timeout=100000
$a="/verysilent /key=2181-8A0B-5FFB /URL=https:="cc8b9cbb.cyrisma.com"
$WebClient = New-Object System.Net.WebClient
$WebClient.DownloadFile("https://dl.cyrisma.com/6167656E7473/Cyrisma_Setup.exe","C:\windows\temp\Cyrisma_Setup.exe")
$process="C:\windows\temp\Cyrisma_Setup.exe"
Start-Process $process -ArgumentList $a -Wait
Reinstall the CYRISMA Agent
After updating the script:
- Run the corrected script on affected PCs.
- Verify that the agent is installed and appears in the CYRISMA portal.
Check Logs if Issues Persist
If the issue continues:
- Navigate to
C:\CYRISMA_Agent\logs\on the affected machine. - Zip the logs and share them with CYRISMA Support for further analysis.
Example Resolution
In the reported case:
- After fixing the syntax error (
https:=""corrected tohttps:="), the script was rerun, and the agents successfully appeared in CYRISMA.
Support Note
If you experience similar issues or need assistance, check logs and ensure scripts are free of syntax errors. Contact CYRISMA Support for additional help if required.