How the Cross-Platform Agent Works (Windows, macOS & Linux)
Understand the single Plenix agent that runs on Windows, macOS, and Linux — what it collects, how it stays connected, and what you can do with it remotely.
Overview
The Plenix agent is a single, lightweight program that runs natively on Windows, macOS, and Linux. Once installed on a device, it reports telemetry, inventory, and health back to your Plenix tenant and lets you act on that device remotely — all over an encrypted connection, with no inbound firewall rules or VPN required.
What the agent collects
| Data | Description |
|---|---|
| Telemetry | CPU, memory, disk, uptime, and OS details, refreshed continuously |
| Hardware inventory | Make, model, serial, CPU, RAM, disks, network adapters |
| Software inventory | Every installed application and its version |
| Network scan | Devices discovered on the local subnet |
| Process list | Running processes, with the ability to end one remotely |
How it connects
- The agent makes an outbound secure WebSocket connection to Plenix — nothing needs to be opened on the client firewall.
- If the connection drops, the agent reconnects automatically and backfills any queued data.
- Each agent authenticates with a per-device token issued at enrolment.
What you can do remotely
- Remote control — live screen share, file transfer, and a full terminal session (see How to Remote Control a Device)
- Run scripts — execute PowerShell, Bash, or shell scripts from the script library
- Patch & update software — approve and deploy patches across the fleet
- Apply policies — enforce configuration standards on device groups
Platform notes
| Platform | Remote screen share | Terminal | Scripts |
|---|---|---|---|
| Windows | Yes (WebRTC / DXGI capture) | Yes | PowerShell / CMD |
| macOS | Scaffolding in place | Yes | Bash / zsh |
| Linux | Scaffolding in place | Yes | Bash / sh |
Where to find it
- Monitoring → Devices — every enrolled device across all platforms
- RMM → Device detail — telemetry, inventory, remote actions
- Download installers from Monitoring → Devices → Add Device
Where to go next
- Understand the whole module → How Device Monitoring Works
- Next in this module → Add a Device
- Configure Alert Thresholds
- Read the Network Map
- See where this fits in the bigger picture → How a Device Problem Becomes a Fix
Was this article helpful?