CeburuAI Advanced Installation, Silent Deployment, and Troubleshooting

CeburuAI supports interactive and silent (automated) installation of the Ceburu Probe and End Agent.

• Interactive: Recommended for small-scale manual deployments.
• Silent: Recommended for automated deployment through WinRM, RMM, scripts, software deployment tools, or other centralized systems.

⚠️ Important: Install the Ceburu Probe before the End Agents. End Agents register and communicate through the Probe, and the End Agent installer validates connectivity to the Probe during installation.

Installation Components

Both installers require Administrator privileges.

Communication Flow and Ports

Ceburu End Agent  →  Ceburu Probe  →  CeburuAI Cloud

The Probe connects to the CeburuAI backend using secure WebSocket communication. End Agents connect to the Probe over the local network.

⚠️ Ports must match: The Probe listening port (/PORT) and the End Agent Probe Port (/PROBEPORT) must be the same. If the Probe uses port 8080, configure the End Agents to use 8080. A port mismatch is the most common cause of End Agent communication issues — if the Probe port is ever changed, the End Agent configuration must be updated accordingly.

Backend Region

ℹ️ Check first: Before any installation or automated deployment, verify the selected region in the CeburuAI Portal and use the corresponding backend host and Agent Token/API key.

Interactive Installation

Double-click the installer and enter the required configuration information through the installation wizard.

The installer can also be started with some values already populated. The wizard still opens with the supplied values pre-entered, and the administrator can review or modify them before proceeding — helpful for providing standardized installation commands while still allowing verification before installation.

Ceburu-AI-Probe-Setup.exe /BACKENDHOST=us-portal.ceburuai.com /APIKEY=<API_KEY>

Silent Installation

Use /S to run either installer silently, without displaying the installation wizard or requiring user interaction. The API key is required for silent installation. Any settings not supplied use the installer's default values.

Silent Probe Installation

Ceburu-AI-Probe-Setup.exe /S /APIKEY=<API_KEY> /BACKENDHOST=us-portal.ceburuai.com /PORT=8080

? Tip: When specifying /D, it must be the final installer parameter and must not be enclosed in quotation marks. For most deployments, /INSTALLDIR= is recommended instead, because it supports quoted directory paths and can appear anywhere in the command. This applies to both the Probe and End Agent installers.

Silent End Agent Installation

Ceburu-AI-Agent-Setup.exe /S /APIKEY=<API_KEY> /PROBEIP=192.168.33.174 /PROBEPORT=8080

ℹ️ Where to get the key: The End Agent API key is the Agent Token obtained from Configurations → Downloader in the CeburuAI Portal. Ensure the Agent Token corresponds to the selected CeburuAI region.

Running the Silent Installer from Command Prompt

Windows installers operate as GUI applications, so when launched directly from cmd.exe, the command prompt may return immediately without waiting for the installation to finish. Use start "" /wait to make Command Prompt wait for the installer and return the actual installation result:

start "" /wait Ceburu-AI-Probe-Setup.exe /S /APIKEY=<API_KEY> /BACKENDHOST=us-portal.ceburuai.com /PORT=8080
echo exit=%ERRORLEVEL%

An exit code of 0 indicates that the installation completed successfully. The same approach applies to the End Agent installer.

Running the Silent Installer from PowerShell

$p = Start-Process .\Ceburu-AI-Probe-Setup.exe -Wait -PassThru `
     -ArgumentList '/S','/APIKEY=<API_KEY>','/BACKENDHOST=us-portal.ceburuai.com','/PORT=8080'
"exit=$($p.ExitCode)"

Start-Process waits for the installer to finish and returns the installation exit code. This method is particularly useful when deploying through PowerShell automation.

Installation Validation and Logs

During installation, the installer performs several validation steps. For the Probe, these include:

1. Validating required installation parameters and verifying that the API key has been supplied.
2. Constructing the backend WebSocket connection.
3. Checking whether the configured listening port is available.
4. Creating the Probe configuration file.
5. Installing the CeburuAIProbe Windows service and configuring it for automatic startup.
6. Starting the Probe service.
7. Performing a service health check and confirming successful communication.

A successful installation ends with:

Installation completed successfully RESULT: exit=0

Probe installation activity is recorded in:

C:\Program Files\CeburuAI\probe\installer.log

The Agent installer maintains its installation log within its own installation location. If the installation directory cannot be used for logging, the installer falls back to the Windows temporary directory.

The API key itself is never written to the installation log — only information such as the API key length is recorded. Installation logs are especially useful when troubleshooting silent deployments where there is no graphical installation window.

Verifying the Installation

After installation, confirm that each Windows service shows a running state. Both services are configured for automatic startup and can also be checked through Windows Services.

Deployment Recommendations

For automated deployments, run the installer from an already elevated administrative session, for example:

• Windows SYSTEM account
• Administrator PowerShell session
• Administrator WinRM session
• Enterprise RMM platform
• Software deployment platform

⚠️ UAC: Silent mode cannot automatically approve a Windows UAC prompt. If the installer is launched from a standard user session, UAC may request administrator approval — the deployment process must already have administrative privileges before launching the installer.

Recommended Deployment Order

1. Install the Primary Ceburu Probe.
2. Confirm the Probe shows Connected in the CeburuAI Portal.
3. If required, install and register the Secondary Probe.
4. Confirm the Probe listening port.
5. Verify network connectivity between endpoints and the Probe.
6. Obtain the correct Agent Token from the Downloader page.
7. Deploy the End Agents.
8. Verify the CeburuAIAgent service.
9. Confirm the End Agent Status shows Active under Configurations → Assets.

Installer Exit Codes

Automated deployment systems can use installer exit codes to determine whether an installation completed successfully.

Troubleshooting

Failed Installation Behavior

By default, if a Probe or End Agent installation fails during its validation process, the installer removes the incomplete installation. This prevents partially configured services or installation files from remaining on the system.

For troubleshooting, add /KEEPONFAIL so the installation files remain on the machine even when validation fails:

Ceburu-AI-Agent-Setup.exe /S /KEEPONFAIL /APIKEY=<API_KEY> /PROBEIP=192.168.33.174 /PROBEPORT=8080

The installer still returns the corresponding nonzero exit code so the deployment system can identify that the installation was unsuccessful.

Uninstalling

The Probe and End Agent can be removed interactively or silently. Uninstall logs are stored in the Windows temporary directory.