GLPI Agent: deployment, configuration, and troubleshooting

GLPI Agent: deployment, configuration, and troubleshooting

GLPI Agent is a standalone tool that runs on an endpoint, collects detailed hardware and software inventory, and ships it to the GLPI server. Without the agent you maintain records by hand (or via CSV — see getting started with GLPI inventory). With the agent you have a fresh inventory every day with no human in the loop.

What GLPI Agent collects

From an endpoint the agent gathers three layers of data:

  • Hardware: manufacturer, model, serial number, BIOS version, CPU, RAM, disks, network adapters, MAC addresses, monitors connected via DDC, laptop battery health.
  • Software: installed applications with versions, OS with patch level, antivirus state, attached printers.
  • Network (via SNMP discovery task): switches, routers, access points, IP phones, printers — anything reachable in the assigned subnet.

On each run the agent posts an XML payload to the GLPI server, which updates or creates records. Default cadence is once every 24 hours; configurable.

Installation: three platforms

Linux (Debian/Ubuntu):

curl -fsSL https://github.com/glpi-project/glpi-agent/releases/latest/download/glpi-agent.deb \
  -o /tmp/glpi-agent.deb
apt install /tmp/glpi-agent.deb
glpi-agent --server https://glpi.example.com/marketplace/glpiinventory/ --tag prod-linux

Windows: download the MSI from GitHub releases and install:

msiexec /i glpi-agent-x64.msi /qn \
  SERVER=https://glpi.example.com/marketplace/glpiinventory/ \
  TAG=prod-windows

macOS: pkg installer or Homebrew. Place configuration in /Applications/GLPI-Agent.app/Contents/Resources/etc/agent.cfg.

After install the agent registers the device with GLPI; the first inventory arrives within a few minutes.

Mass deployment

For hundreds of devices, manual installation is out of the question. Three proven paths:

  • Windows via GPO: stage the MSI on a network share, create a Group Policy with Computer Configuration → Software Installation → Assigned. The MSI installs on the next reboot. Pre-configure (server URL, tag) via an MST transform file.
  • Windows via Intune/SCCM: upload the MSI as a Win32 app, define parameters, deploy to a device group.
  • Linux via Ansible: a small role that downloads the deb/rpm, installs it, and writes /etc/glpi-agent/conf.d/server.cfg with the right parameters. Run via systemd timer.
  • macOS via MDM (Jamf, Mosyle, Intune): upload the pkg as a custom installer, distribute via smart group.

Tags (e.g. prod-linux, devs-mac) are worth setting — in GLPI they become a filter field for bulk actions or reports.

Discovery vs Inventory tasks

The agent runs two task types:

  • Inventory — collects data from the local device. Runs automatically on schedule.
  • Network Discovery — the agent scans an IP range, looking for other devices (typically unmanaged ones — switches, printers, IoT). Requires SNMP credentials stored in GLPI.

Delegate Network Discovery to one or two agents on strategically placed servers — typically one per network segment. You don't need every laptop scanning the network.

Troubleshooting common issues

Agent installed, but GLPI doesn't see it

Check /var/log/glpi-agent/glpi-agent.log (Linux) or %PROGRAMDATA%\GLPI-Agent\glpi-agent.log (Windows). Most common cause: wrong server URL or outbound HTTPS on port 443 blocked by firewall.

TLS error

A self-signed certificate on the GLPI server will be rejected by the agent. Either install a valid cert, or temporarily add no-ssl-check = 1 to agent.cfg (not for production).

Inventory arrives but some fields are missing

Some data requires root/admin privileges — for example, BIOS serial on Linux (dmidecode). Verify the agent runs as root (Linux) or SYSTEM (Windows). MSI install via GPO does this by default.

Duplicate records

After an OS reinstall (same hardware, new hostname) GLPI creates a second record. Fix: in Setup → General → Inventory, configure deduplication by serial number, MAC address, or UUID. Resolve existing duplicates via the bulk merge in admin.

When to go agentless

For most servers and endpoints the agent is ideal. For some scenarios it isn't:

  • Network devices — switches, routers, firewalls — typically agentless via SNMP discovery.
  • IoT and embedded devices — no way to install an agent. SNMP or manual records.
  • Foreign devices in BYOD scenarios — where you don't have permission to install software.

A hybrid approach (agent on everything managed plus SNMP for the rest) covers more than 95% of a typical fleet. The remainder you add manually when they show up in an incident.

Need help with this topic?

Get in touch