Install and operate the Qixium Agent

Prepare the host

Use a Windows server with access to the required local resources and outbound HTTPS on port 443 to its Qixium instance. The installation guide supports one Agent per server. Confirm the supported Windows and Agent versions for your deployment.

The online source reviewed on 6 November 2026 lists 4 GB RAM / 100 GB storage / 2 GHz with 2 cores as minimum, and 8 GB / 160 GB / 2 GHz with 4 cores as recommended, including Windows. Large datasets may require more memory. The older PDF has different storage figures; confirm capacity for your version.

Create, download and configure

1. Create the Agent under Connector > Connections > Agent in the correct instance.
2. Download its package and extract it on the intended Windows host.
3. Check rootDataFolder, rootConfigFolder and pluginFolder in Agent\config.json. Use the field names present in the generated file and escape Windows path separators as \ in JSON.
4. Protect the package and configuration: they can contain pairing credentials. Do not share them in public documentation or source control.

Console check, then Windows service

In an elevated command prompt in the Agent directory, use cs.agent.win.exe -console to check startup and connectivity. Stop that console process before using the service. Install the service using cs.agent.win.exe -install, configure its account and start it in Windows Services. Grant only required local access.

Configure a connector

Create the connection, select its Agent and reload Agent configurations. Complete the generated connector file in the local configs directory, then reload again. Check the Online status and a controlled read operation.

Operations and troubleshooting

Keep-alive shows connectivity. The source describes automatic Agent updates with instance upgrades; include these in maintenance planning. Inspect Logging > Agent Log and the local AgentLog directory. The PDF mentions seven days of instance log retention; confirm current retention for your version.

Check HTTPS, proxy/certificates, the Windows service account, path settings and JSON syntax. Failed ping alone is not evidence of an HTTPS failure. Investigate endpoint protection alerts with IT rather than disabling protection. Report timing and error context to support without secrets.

Back to Agent and connectors

Sources and version

• Installatie & Configuratie
• Specificaties

Sources reviewed on 6 November 2026. Screen names and capabilities depend on your installed version and configuration.