GLPI Agent on Windows: Install and Send Inventory to GLPI

This guide is for admins who already have a GLPI server (or are building one) and want Windows PCs and servers to report their hardware and software on their own. The short answer: install the GLPI Agent from its 64-bit MSI, give it your GLPI address with SERVER=, leave it running as a service, and the machine shows up under Computers within minutes. For a fleet, the same MSI takes command-line options, a GPO startup script or winget.

Facts below were checked on 13 November 2026 against the project’s GitHub release data, the agent documentation on Read the Docs and the GLPI help center. Not tested yet: we have not run this version ourselves, so try it on one test machine before a wide rollout.

Agent facts at a glance

The agent is only the client half. The server that stores records, applies rules and shows the inventory is GLPI; this page covers the agent from the GLPI Agent catalogue entry.

Before you install

• Server address. GLPI’s help center says to use the value in Setup > General > General Configuration > URL of the application, for example https://glpi.example.com/. The documented GPO example uses the longer form ending in /front/inventory.php; start with the base URL and try the long form only if uploads fail.
• Native inventory. Since GLPI 10 the inventory is built into the server; FusionInventory is no longer supported. Network discovery, data collection and package deployment still need the separate GLPI Inventory plugin from the marketplace.
• Old agents. If you are replacing the FusionInventory agent, uninstall it first. The documentation says you can reuse your settings if they sit in the conf.d folder.
• Shell. The documentation warns against PowerShell for the installer and the agent command line, because it changes the environment in ways the installer does not handle well. Use an elevated cmd.exe.

Install on one machine (graphical)

Run the MSI and go through the full wizard once; GLPI’s own tutorial recommends this so you can see every choice. You will be asked for the server address, then how the agent runs: as a service (always running), as a scheduled task, or manually. Further screens cover certificates, proxy, a tag, scanning of user home directories for virtual machines and scanning of software inside user profiles. You can also ask for an inventory at the end of the install. If you do, the computer should appear a few minutes later in the Computers list.

The optional Glpi-AgentMonitor puts a tray icon on the machine so a user can force an inventory, read the log or open a ticket. It is part of the MSI and only works when the agent is installed as a service.

Install silently with command-line options

This is the form to put in a script or a deployment tool. Options are case-sensitive, need an equals sign with no spaces around it, and values with spaces need quotes.

msiexec /i GLPI-Agent-1.21-x64.msi /quiet SERVER="https://glpi.example.com/" TAG=office-pcs RUNNOW=1 ADD_FIREWALL_EXCEPTION=1

The options you will use most, from the Windows installer page:

Roll it out to many PCs

winget

The documentation shows a winget route for Windows 10 and 11. A configured install looks like this:

winget install glpi-agent --custom="SERVER='https://glpi.example.com/' RUNNOW=1"

It needs administrator rights, so expect a UAC prompt from a normal console.

GPO startup script

The project ships a VBScript, glpi-agent-deployment.vbs, meant for a computer startup script in a Group Policy Object. You edit a few lines at the top: the agent version, the network share that holds the MSI, and the install options. The GLPI example sets /quiet RUNNOW=1 ADD_FIREWALL_EXCEPTION=1 plus the server and a tag. The script can also remove FusionInventory or OCS Inventory agents, repair a broken install, and reconfigure an agent that is already at the same version. Every PC must be able to read the share or download URL at startup.

Check that it works

1. Open http://localhost:62354 on the machine. If the agent runs as a service, this is its status page, and from a trusted address it offers a link to force an inventory.
2. Or force a run from an elevated cmd.exe: cd "C:\Program Files\GLPI-Agent", then glpi-agent --force. The documentation describes --force as running the task even if the server did not ask for it.
3. Read the log at C:\Program Files\GLPI-Agent\logs\glpi-agent.log (default path; the log rotates at 4 MB by default).
4. In GLPI, open Assets > Computers and look for the machine.

Settings live in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\GLPI-Agent. After a change, restart the service. GLPI’s help center also notes that a “400 Bad Request, Protocol not supported” message in the log is expected for the Collect and Deploy tasks when the GLPI Inventory plugin is absent; the machine inventory itself still works.

Limitations

• The agent reports only to a server. It is not a remote-control or monitoring tool.
• In service mode a privileged process listens on a network port (62354) unless you set NO_HTTPD=1. The documentation also points out that whoever controls the GLPI server can run code on agents if the Deploy task is installed and enabled; since version 1.8 no task beyond Inventory is selected by default.
• Network discovery, SNMP inventory, collection and deployment need the GLPI Inventory plugin on the server as well.
• 32-bit Windows systems are stuck on 1.7.3.
• If your estate is mostly agentless, a scanner such as Open-AudIT may fit better; see the IT asset management and help desk tools guide for the options.

Who it suits

It suits teams running GLPI who want laptops and servers to fill their own records: free, open source, one MSI, scriptable. It does not suit teams without a GLPI server or anyone who needs a 32-bit Windows build.

FAQ

Where do I download the GLPI agent for Windows?

From the project’s official GitHub releases page, which the agent documentation links to. Pick the x64 MSI and check that the file name matches the release you intended.

What port does the GLPI agent use?

The embedded web interface listens on 62354 by default (HTTP_PORT in the installer, httpd-port in the configuration). The server may contact this port to start an out-of-schedule run.

Where is the GLPI agent configuration on Windows?

In the registry at HKEY_LOCAL_MACHINE\SOFTWARE\GLPI-Agent. On Linux it is /etc/glpi-agent/agent.cfg.

How do I force an inventory on Windows?

Open http://hostname:62354 from a trusted address, use the tray monitor, or run glpi-agent --force.

Does the GLPI agent work on 32-bit Windows?

Not in current versions. The 32-bit installer ended with 1.7.3; since 1.8 only the 64-bit package is built.

What does the GLPI agent monitor do?

It adds a tray icon that lets a user force an inventory, check the agent log and open a ticket. It needs the agent installed as a service and the embedded web server enabled.

Last updated: 13 November 2026 · AdminHub Plus editorial team. Licence, version and platform details are checked against each developer's official documentation.