Manual Server Agent Installation

The Kabeen server agent is the component responsible for collecting information about the information system infrastructure: host configuration, system metrics, installed programs and running processes.

It is a standalone system service to be installed on each server you want to analyze in Kabeen. Data is transmitted to the Kabeen backend over gRPC on TLS, using outbound port 443/TCP only.

New in 3.0. The server agent is now distributed as a signed MSI installer on Windows (replacing the .exe) and its configuration uses a TOML file (config.toml) instead of application.conf. If a previous agent is present on the machine, its configuration is migrated automatically on first start (see Migrating from the previous agent).

Prerequisites

• Outbound connection allowed to intake.kabeen.io on port 443/TCP. No inbound connection is required.
• Administrator privileges (root on Linux, member of local Administrators on Windows).
• On Linux, systemd is required as the init manager.

Package Download

Download the package matching your operating system from your Kabeen console (Infrastructure > Add a server > Automatic installation).

Installation on Windows

1. Double-click the MSI file and accept the UAC elevation.
2. Read and accept the End-User License Agreement (EULA).
3. On the Kabeen API key screen, paste the API key retrieved from your Kabeen account. You can also leave the field empty and set the key later in config.toml.
4. Click Install.

The installer copies the binary to C:\Program Files\Kabeen\Server Agent\, writes the configuration to C:\ProgramData\Kabeen\Server Agent\config.toml, registers the Windows service KabeenServerAgent (automatic startup) and starts it.

Silent installation. For a standalone machine, in an administrator PowerShell:

msiexec /i "kabeen-server-agent-x86_64.msi" /qn /norestart APIKEY="YOUR_KABEEN_API_KEY"

For mass deployment (GPO, Intune, SCCM), see the dedicated guides in the Infrastructure Agent section.

Installation on Linux (Debian / Ubuntu)

Install the downloaded .deb package (apt-get install resolves dependencies automatically):

sudo apt-get install ./kabeen-server-agent_amd64.deb

Installation creates the configuration file, enables the kabeen-server-agent.service unit and starts it. Then set the API key (see API Key Configuration).

Installation on Linux (Red Hat and derivatives)

Install the downloaded .rpm package:

sudo dnf install ./kabeen-server-agent.x86_64.rpm
# or, on distributions without dnf:
sudo yum install ./kabeen-server-agent.x86_64.rpm

As on Debian, the service is enabled and started automatically. All that remains is to set the API key.

API Key Configuration

On Linux, the API key must be set in the /etc/kabeen-server-agent/config.toml file:

api_key = "YOUR_KABEEN_API_KEY"

sudo install -m 600 -o root -g root /dev/stdin /etc/kabeen-server-agent/config.toml <<'EOF'
api_key = "YOUR_KABEEN_API_KEY"
EOF

On Windows, the file is located at C:\ProgramData\Kabeen\Server Agent\config.toml.

No need to restart the service. The agent re-reads config.toml automatically every 10 seconds: the new key is picked up at the next tick. Since the file contains a plaintext key, keep restrictive permissions (0600 / root on Linux).

Migrating from the previous agent

If a previous agent is already installed, the Kabeen server agent automatically imports its configuration on the very first start:

Reusing the agentUUID ensures that the machine keeps the same identity in the Kabeen console — it does not appear as a new host.

Migration runs only once and never overwrites an already-configured setup. Recommended procedure: install the server agent, verify in the Kabeen console that the machine reports under the same identifier, then uninstall the previous agent.

Verifying Operation

Linux:

sudo systemctl status kabeen-server-agent.service
sudo journalctl -u kabeen-server-agent.service -f

Windows (administrator PowerShell):

Get-Service -Name KabeenServerAgent

Once a valid API key is set, the logs should display All tasks running. Agent is operational., and the machine should appear in your Kabeen console with a recent heartbeat (less than 2 minutes).