CeburuAI supports both interactive installation and automated unattended deployment for the Ceburu Probe and Ceburu End Agent.

Interactive installation is recommended when installing a small number of systems manually. Silent installation is useful for larger environments where the Probe or End Agent must be deployed through automation tools such as WinRM, RMM platforms, software deployment tools, scripts, or other centralized management systems.

The Ceburu Probe must be installed before deploying End Agents because the End Agents communicate with the Probe for registration and ongoing communication.

Installation Components:

Both installers require Administrator privileges.

The Probe connects to the CeburuAI backend.

The End Agent connects to the Probe over the local network.

Probe Communication Flow:

The communication path is:

Ceburu End Agent → Ceburu Probe → CeburuAI Cloud

The Probe maintains communication with the CeburuAI backend using WebSocket Secure communication.

The Probe backend connection is constructed as:

wss://<backend-host>/api/ws/agent

The End Agent communicates with the Probe using:

ws://<probe-ip>:<probe-port>/ws

The Probe listening port configured during installation must therefore also be used as the Probe Port when configuring End Agents.

For example, if the Probe is configured to listen on port 8080, the End Agents must also be configured with Probe Port 8080.

Selecting the Correct Backend Region

Before installing the Probe, confirm the region selected in the CeburuAI Portal.

The Probe must be configured for the backend associated with the selected region.

For example:

US Region

us-portal.ceburuai.com

EU Region

eu-portal.ceburuai.com

Always verify the appropriate backend host and Agent Token from the CeburuAI Portal before beginning automated deployment.

The API key or Agent Token must correspond to the correct CeburuAI region.

Interactive Installation with Preconfigured Values:

Normally, users can double click the installer and enter the required configuration information through the installation wizard.

It is also possible to start the installer with some values already populated.

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

The installation wizard will still open, but the supplied values will already be entered.

The administrator can review or modify the values before proceeding with installation.

This method can be helpful when providing standardized installation commands while still allowing the administrator to verify the configuration before installation.

Silent Probe Installation:

For automated deployment, the Probe installer supports silent installation.

Silent mode runs without displaying the installation wizard or requiring user interaction.

Use /S to enable silent mode.

Example:

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

The important configuration values are:

The API key is required when performing a silent installation.

If other settings are not supplied, the installer uses its configured default values.

Running the Silent Installer from Command Prompt:

Windows installers operate as GUI applications. When launching the installer directly from cmd.exe, the command prompt may return immediately without waiting for the installation to finish.

To make Command Prompt wait for the installer and return the actual installation result, use:

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

To display the installer exit code:

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.

Running the Silent Installer from PowerShell

The Probe can also be installed silently through PowerShell.

Example:

$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 the Probe through PowerShell automation.

Probe Installation Parameters:

The following parameters are supported by the Probe installer.

When specifying /D, it must be the final installer parameter and should not be enclosed in quotation marks.

For most deployments, /INSTALLDIR= is recommended because it supports quoted directory paths and can appear anywhere in the command.

Silent End Agent Installation:

The End Agent installer also supports silent deployment.

Example:

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

The End Agent uses the following information:

Probe IP

The IP address of the Ceburu Probe that will manage the endpoint.

Example:192.168.33.174

Probe Port

The listening port configured during the Probe installation.

The default value is:8080

The Probe Port configured for the End Agent must match the listening port configured on the Probe.

API Key

The Agent Token obtained from:

Configurations → Downloader

in the CeburuAI Portal.

Ensure that the Agent Token corresponds to the selected CeburuAI region.

End Agent Installation Parameters:

Installation Validation:

During installation, the installer performs several validation steps.

For the Probe, these include:

1. Validating required installation parameters.

2. Verifying that the API key has been supplied.

3. Constructing the backend WebSocket connection.

4. Checking whether the configured listening port is available.

5. Creating the Probe configuration file.

6. Installing the CeburuAIProbe Windows service.

7. Configuring the service for automatic startup.

8. Starting the Probe service.

9. Performing a service health check.

10. Confirming successful communication.

A successful installation ends with:

Installation completed successfully RESULT: exit=0

Installation Logs

Installation activity is recorded in:

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

The Agent installer also maintains installation logging within its installation location.

If the installation directory cannot be used for logging, the installer can fall back to the Windows temporary directory.

The API key itself is not written to the installation log. Only information such as the API key length is recorded.

Installation logs are useful when troubleshooting silent deployments where there is no graphical installation window.

Verify the Probe Service:

After installation, verify the Windows service.

From Command Prompt:

sc queryex CeburuAIProbe

The service should show a running state.

You can also verify the service through:

Windows Services → CeburuAIProbe

The service is configured for automatic startup.

The default Probe installation directory is:

C:\Program Files\CeburuAI\probe

Verify the End Agent Service:

After installing the End Agent, run:

sc queryex CeburuAIAgent

The service should show a running state.

You can also verify it through Windows Services.

The default Agent installation directory is:

C:\Program Files\CeburuAI\agent

After successful registration, the CeburuAI Portal should display the End Agent Status as Active.

Installer Exit Codes:

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

Exit Code 3

This commonly occurs during silent installation when /APIKEY= was not provided.

Verify that the installation command includes:

/APIKEY=<API_KEY>

Exit Code 4

For an End Agent, this normally means the Probe cannot be reached using the configured Probe IP and Probe Port.

Verify:

PROBEIP PROBEPORT

Also confirm that network communication is permitted between the endpoint and the Probe.

Exit Code 5

The Probe rejected the Agent API key.

Verify that:

1. The API key is correct.

2. The API key belongs to the correct CeburuAI region.

3. The Probe is registered successfully.

4. The Probe is connected to the CeburuAI backend.

Exit Code 6

The Probe listening port is already being used by another application.

Check the configured port and either stop the conflicting application or configure another available Probe port.

If the Probe port is changed, End Agents must use the same value for /PROBEPORT.

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 purposes, administrators can use:

/KEEPONFAIL

Example:

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

with /KEEPONFAIL, installation files remain on the machine even when validation fails.

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

Deployment Recommendations:

For automated deployments, run the installer from an already elevated administrative session.

Examples include:

1. Windows SYSTEM account.

2. Administrator PowerShell session.

3. Administrator WinRM session.

4. Enterprise RMM platform.

5. Software deployment platform.

If the installer is launched from a standard user session, Windows UAC may request administrator approval.

Silent mode cannot automatically approve a UAC prompt.

Therefore, the deployment process should already have administrative privileges before launching the installer.

Recommended Deployment Order:

For environments using End Agents, use the following deployment sequence:

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.

Installing the Probe first is important because the End Agent validates connectivity with the Probe during installation.

Nmap Requirement:

Nmap is not included with the CeburuAI Probe installer.

If network discovery functionality requires Nmap, install Nmap separately on the Probe machine.

After installing Nmap, restart the Probe service:

net stop CeburuAIProbe net start CeburuAIProbe

The Probe will then detect Nmap through the Windows system PATH.

Uninstalling the Ceburu Probe:

The Probe can be removed interactively or silently.

Silent uninstall:

start "" /wait "%ProgramFiles%\CeburuAI\probe\Uninstall.exe" /S

Interactive uninstall:

"%ProgramFiles%\CeburuAI\probe\Uninstall.exe"

Uninstalling the Ceburu End Agent:

Silent uninstall:

start "" /wait "%ProgramFiles%\CeburuAI\agent\Uninstall.exe" /S

Interactive uninstall:

"%ProgramFiles%\CeburuAI\agent\Uninstall.exe"

Uninstall logs are stored in the Windows temporary directory.

Troubleshooting Automated Installation:

Important Configuration Check:

The most common End Agent communication issue is a mismatch between the Probe listening port and the End Agent Probe Port.

For example:

Probe:

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

Agent:

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

Both configurations use port:8080

If the Probe is configured with another port, the End Agent configuration must be updated accordingly.

Security Considerations:

Do not publish actual Agent Tokens or API keys in Knowledge Base screenshots, command examples, email messages, tickets, or documentation.

Always use placeholders such as:

<API_KEY>

when documenting installation commands.

Administrators should obtain the actual token directly from the appropriate CeburuAI Portal region before beginning deployment.