Sample PowerShell Script (Without Auto Provisioning)

This script requires manual provisioning in the CYRISMA Command Center after installation.

$a = "/verysilent /key=XXXXXX /URL=XX"
$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 -FilePath $process -ArgumentList $a -Wait

Optional: Sample PowerShell Script (With Auto Provisioning)

This version automatically provisions the agent, skipping the manual provisioning step in the Command Center.

$a = "/verysilent /key=XXXXXX /URL=XX /autoprovision=yes"
$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 -FilePath $process -ArgumentList $a -Wait

Instructions

Customize the Script

Replace XXXXXXXX with your unique key and instance URL, which can be found in the CYRISMA Command Center under Admin > Scan Agents.

Choosing Between Manual and Auto Provisioning

• The first script requires the agent to be manually provisioned in the Command Center after installation.
• The second script includes the /autoprovision=yes switch, which automatically provisions the agent.
• If using auto provisioning, place the switch after the key and URL with no spaces around the "=" sign.

Deployment

After customizing the script, run it using your preferred remote management or software deployment platform.

Important Notes

• Avoid using $args as a variable in PowerShell scripts, as it is a reserved keyword in PowerShell.
• Ensure that your deployment platform is properly configured to run PowerShell scripts on remote systems.
• Auto provisioning should be used carefully, especially in environments with multiple instances, to prevent accidental installations.

Conclusion

Both scripts provide an efficient way to deploy CYRISMA Agents. The manual provisioning method adds an extra layer of control, while the auto provisioning option allows for large-scale deployments with minimal manual intervention. Choose the method that best fits your deployment needs.