The latest release is available from our github releases page.


In the case you're replacing FusionInventory agent with GLPI Agent, you should first uninstall FusionInventory agent before installing GLPI Agent. You can use the same dedicated configuration if you placed it in conf.d configuration subfolder.


Nightly builds are also available from our dedicated GLPI-Agent Nightly Builds page.


The installer integrates its native, although reduced but recent, version of Strawberry Perl including recent OpenSSL support.

You can download the lastest GLPI Agent installer or current nightly build. It is available for both 32 and 64 bits systems and provides a graphical interface as well as command line facilities.

By default, it will perform a graphical installation, unless you use the msiexec /i and /quiet options. All installer parameters are described in Windows installer dedicated page.


All graphical installer options are related to a command line one. Check Windows installer if you need help.

Large Installations

A VBScript (Visual Basic Script) is provided to deploy the installer on a network: glpi-agent-deployment.vbs.


The installer integrates its native, although reduced but recent, version of Perl including recent OpenSSL support.

Get the latest .pkg package from our releases page or the nightly build page. After installing it, you'll have to configure the agent to your needs by creating a dedicated .cfg file under the /Applications/GLPI-Agent/etc/conf.d folder.

You can for example create a local.cfg file and :

  • add the server = GLPI_URL line to point to your GLPI server,

  • eventually set debug = 1 to generate some debug in logs,

  • set a tag like tag = MyLovelyTag.


We support major distros as we provides generic packages for RPM and DEB based distros as well if they supports Snap packaging. You can install required packages after getting them from our github releases page or the nightly build page.


When possible, prefer to use our linux perl installer as it supports RPM and DEB based distros. There's a version also including the Snap package. The linux installer accepts few options to configure the agent so it can simplify manual or automatic installation. It also can be handy for tools like Puppet or Ansible.

Linux AppImage installer


When not sure or linux perl installer doesn't support your distro, try Linux AppImage installer.

See Linux AppImage installer dedicated page


The Snapcraft Snap package integrates its native, although reduced but recent, version of Perl including recent OpenSSL support.

If your system support Snap, you can simply install the agent with the snap command after getting the Snap package from our releases page or the nightly build page. Then, you just have to run:

snap install --classic --dangerous GLPI-Agent-1.2-git*_amd64.snap

After installation, you can easily configure the agent with the set snap sub-command:

snap set glpi-agent server=http://my-glpi-server/

Any supported glpi-agent option can be set this way. If you need to unset a configuration parameter, just set it empty:

snap set glpi-agent tag=


You won't find the package in the Snapcraft store as their standard policies are too restrictive for GLPI Agent features and requirements.

Linux Perl Installer


The linux installer main requirement is the perl command.

It also requires one of the following command, depending on the targeted system:

  • dnf for recent RPM based systems

  • yum for previous generation of RPM based systems

  • apt for DEB based systems like Debian & Ubuntu

  • snap for other systems supporting Snapcraft Snap packages

We also provide a dedicated linux installer which includes all the packages we build (RPM & DEB) and eventually the snap one. On supported distros (DEB & RPM based), the installer will also eventually try to enable third party repositories, like EPEL on CentOS if they are required.

The installer is a simple perl script. It supports few options to configure the agent during installation. You can check all supported options by running:

perl glpi-agent-1.2-git* --help

or if you use the installer embedding snap package:

perl glpi-agent-1.2-git* --help

If your GNU/Linux distro is not supported, you still can install it from sources.

From sources


We strongly recommend the use of GNU tar because some file path length are greater than 100 characters. Some tar version will silently ignore those files.

First, you need to extract the source and change the current directory.

tar xfz GLPI-Agent-1.2-git*.tar.gz
cd GLPI-Agent-1.2-git*

Executing Makefile.PL will verify all the required dependencies are available and prepare the build tree.

perl Makefile.PL

If you don't want to use the default directory (/usr/local), you can use the PREFIX parameter:

perl Makefile.PL PREFIX=/opt/glpi-agent


At this point, you may have some missing required modules. See PERL Dependencies section for installing them. Once this is done, run the same command again.

You now can finish the installation. Here again we recommend GNU make (gmake):

make install



The tests suite requires some additional dependencies like Test::More.

GLPI agent comes with a test-suite. You can run it with this command:

make test

Perl dependencies

The easiest way to install perl dependencies is to use cpanminus script, running:

cpanm .

You can use the --notest flag if you are brave and want to skip the tests suite execution for each install perl module.

Offline installations


This requires the cpanminus script to be installed.

First grab the tarball from the website and extract it:

tar xzf GLPI-Agent-1.2-git*.tar.gz
cd GLPI-Agent-1.2-git*

We use cpanm to fetch and extract the dependencies in the extlib directory:

cpanm --pureperl --installdeps -L extlib --notest .

If this command fails with an error related to Params::Validate, then just run this last command:

cpanm --installdeps -L extlib --notest .

Now you can copy the directory to another machine and run the agent this way:

perl -Iextlib/lib/perl5 -Ilib glpi-agent

Other dependencies

On Solaris/SPARC, you must install sneep and record the Serial Number with it.

On Windows, we use an additional dmidecode binary shipped in the windows MSI package to retrieve many information not available otherwise, including fine-grained multi-cores CPUs identification. Unfortunately, this binary is not reliable enough to be used on Windows 2003, leading to less precise inventories.

On Linux, lspci will be used to collect PCI, AGP, PCI-X, ... information.