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.
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.
A VBScript (Visual Basic Script) is provided to deploy the installer on a network:
Leonardo Bernardes published Glpi-Agent Monitor tool which provides a systray icon to survey the agent status and permit to ask a tasks run.
You can download it from the Glpi-Agent Monitor project release page. You simply have to download the exe into any folder (the Glpi-Agent installation folder is just fine) and start it.
If you want to add it to all users auto-started softwares, you can directly install it into the C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp folder.
Glpi-Agent Monitor has been integrated into GLPI-Agent MSI installer and can be enabled using AGENTMONITOR=1 on the MSI commandline. When installed this way, you don't need to copy it manually and it starts when a user is logs in.
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
You can for example create a
local.cfg file and :
server = GLPI_URLline to point to your GLPI server,
debug = 1to generate some debug in logs,
tag = MyLovelyTag.
A MacOSX installation video tutorial is available here: GLPI Agent Demonstration - macOS Monterey - Apple M1
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.
snap install --classic --dangerous GLPI-Agent-1.5_amd64.snap
After installation, you can easily configure the agent with the set
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.5-linux-installer.pl --help
or if you use the installer embedding snap package:
perl glpi-agent-1.5-with-snap-linux-installer.pl --help
If your GNU/Linux distro is not supported, you still can install it from sources.
Unofficial repositories are not supported by GLPI-Agent editor. Use them at your own risk.
Thanks to ligenix, a COPR repository can be used to install glpi-agent on Fedora 35 & 36, CentOS Stream 8 & 9, EPEL 7, 8 & 9: ligenix/enterprise-glpi10
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.5.tar.gz cd GLPI-Agent-1.5
Makefile.PL will verify all the required dependencies are available
and prepare the build tree.
If you don't want to use the default directory (
/usr/local), you can use the
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 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:
You can use the
--notest flag if you are brave and want to skip the tests suite execution for each install perl module.
This requires the cpanminus script to be installed.
First grab the tarball from the website and extract it:
tar xzf GLPI-Agent-1.5.tar.gz cd GLPI-Agent-1.5
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
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
lspci will be used to collect PCI, AGP, PCI-X, ... information.