GLPI Inventory
Sources
Prerequisites (Self-hosted)
10.0.x
8.1
8.2
11.0.x
8.2
8.4
This plugin is available without a subscription from GLPI Network. It is also available on GLPI Cloud.
Features
GLPI Inventory allows GLPI to automate certain actions such as network discovery, SNMP reporting, information collection, and application remote deployment. Coupled with the GLPI agent, it is a complementary component to native inventory if you want to optimize your IT assets.
Install the Plugin
Download and install the GLPI Inventory plugin from the marketplace

General
Agent Management
This tab switches you to the native inventory agent management. It allows you to manage agent modules, among other things.
Computer Groups
Groups allow tasks to be performed on targeted workstations. For example, deploying the 7zip application to all computers in the IT group. There are 2 types of groups:
Dynamic Group: This group is populated based on specific criteria (entity, location, OS, etc.) which can be combined. This group will be dynamically modified over the lifecycle of the hardware and according to changes in related criteria.

Static Group: Static groups contain computers that you have manually added.
General Configuration
The general configuration defines the behavior of GLPI Inventory during its execution.

SSL-only for agent: When enabled, the GLPI server refuses any communication from an agent if it is not encrypted (HTTPS).
Agent Port: Allows modification of the agent port; this must also be modified in the agent configuration.
Delete tasks logs after: Define the number of days to retain logs (from 1 to 240).
Re-prepare successful jobs: Allows defining whether a job can be prepared after success so that it is relaunched during the next execution.
Maximum number of agents to wake up in a task: The number of agents a task can process simultaneously.
Extra-debug: Enables debug mode.
Debug mode can consume a lot of disk space. Activate it only when necessary.
Network Inventory

Threads Number (Network Discovery): Determines the number of requests made simultaneously during network discovery. For example, if the number of threads is set to 10, the agent queries 10 IP addresses at the same time. As soon as a thread finishes with an IP, it moves to the next available one in the range.
Threads Number (Network Inventory (SNMP)): Same behavior as for threads (Network Discovery).
SNMP Timeout (Network Discovery): Number of requests before a timeout occurs during network discovery.
SNMP Timeout (Network Inventory (SNMP)): Same behavior as for network discovery timeout.
Package Management

Use this GLPI server as a mirror server: Allows storing files on the GLPI server that will be used for remote deployment.
Match a mirror to agents: Allows isolating mirrors by location, entity, or both.
Delete successful on demand tasks after (in days): Purge successful tasks after a certain period (from never to 1000).
Agent Modules
Allows defining which agent will be able to perform the available tasks from the list:
Computer inventory
VMware host remote inventory
Network inventory (SNMP)
Network discovery
Package deployment
Collect data

You can also add exceptions for certain agents if you do not want them to be able to perform a task.
Tasks
Task Management
Task management allows you to perform actions using the agent. Tutorials are available to guide you through each task:
Printers / Network InventoryCollect DataDeploy via GlpiInventoryMonitoring / Logs

This tab allows you to view all logs for configured tasks. It is possible to set the refresh interval to monitor task progress:
Import Agent XML
This section redirects to GLPI's native inventory. Follow the link below to view the inventory options:
Native Inventory (coming soon)
Collection Information
1. Query the Registry (Windows)
Administrators can ask the agent to read the value of a specific registry key and report it to GLPI.
Example: Verify if a security GPO (Group Policy) is correctly applied to the workstation, or check the configuration of software (e.g., AutoCAD, an ERP, VPN client, etc.).
2. Execute WMI Queries (Windows)
WMI (Windows Management Instrumentation) collection allows running custom WMI queries.
Example: Report the BitLocker encryption status on disks, or check the status of a specific Windows service (linked to business software, for example).
3. Inspect Files (Multi-OS)
Data collection allows checking for the existence of files, their metadata (modification date, size), or even extracting a specific line from a file's content.
Example: Search for the presence of a business application
.iniconfiguration file, or read the exact version configured within that file.
An article is dedicated to data collection
Time Slot

Rules
Asset skipped during import
Ignored hardware refers to equipment that has been scanned by the GLPI Agent and whose inventory file has been successfully transmitted to the server. However, the GLPI server has deliberately chosen to block their creation. They are placed in this section, which acts as a waiting room or quarantine, to avoid cluttering the IT inventory with unnecessary or erroneous data.
This section is populated by voluntary filtering that occurs primarily at two levels during the inventory file processing:
The Rule Engine (Asset Import and Linking Rules): When an inventory arrives, it passes through the rule engine. It is possible to create specific rules stating, for example: "If the equipment's IP address starts with 192.168.1.x (guest/remote work network), then refuse it." The "Refuse Import" action directly sends the equipment to the ignored hardware.
Blacklists: GLPI natively has blacklist dictionaries to prevent the accidental merging of different machines.
Blacklisted MAC Addresses: VPN network cards (e.g., Fortinet, OpenVPN, etc.) or virtual cards often generate identical MAC addresses on all PCs.
Blacklisted Serial Numbers: It can happen that a PC manufacturer or assembler does not flash the BIOS. The PC then reports with a generic serial number such as "To Be Filled By O.E.M", "Default string", or "0123456789". GLPI detects and blocks them.
Computer entity rules
This tab links to administration rules, particularly rules for assigning an item to an entity.
These rules allow, based on defined criteria, to automate actions on hardware reported by GLPI.
Example: if the subnet is 192.168.1.0/24, assign it to the entity corresponding to this subnet
These rules simplify, compartmentalize, and automate hardware distribution within the inventory.
Blacklist
Unlike "Rules" (which use complex "If... Then..." logic), blacklists are simple lists of prohibited values.
The Different "Types" of Blacklists (and Use Cases)
IP Address: allows ignoring loopback addresses (loopback) or networks that should not be inventoried.
Common examples:
127.0.0.1,0.0.0.0, or::1(for IPv6).
MAC Address: allows blocking virtual network cards (VMware, VirtualBox) or MAC addresses generated by VPN software.
Serial Number: Essential for assembled PCs or those whose motherboard has been replaced without the BIOS being updated by the repair technician.
Common examples:
To be filled by O.E.M.,System Serial Number,Default string.
UUID: The Universally Unique Identifier is unique for each motherboard. However, some series share the same UUID from the factory or a "quirky" number.
Model / Manufacturer: Allows blocking the import of equipment from brands or models deemed irrelevant for inventory management.
Network
IP Ranges
IP ranges are linked to network discovery and network inventory (SNMP) tasks. They allow defining IP addresses on which tasks will be launched. It is possible to create multiple ranges and to break down discovery and inventory into several ranges to avoid scanning the entire network and overloading the network (IP range for printers, network devices, etc.).
Caution: the agent must have access to these IP ranges to perform the tasks associated with them.
Remote devices to inventory (VMware)
It is possible to inventory virtual machines from an ESX or vCenter. It is not necessary to install an agent on the ESX; a GLPI agent installed on Windows or Linux will perform remote inventory via an automatic task. For Windows, the task module must be added to the installation. For Linux distributions, you must install an additional package.
From
Administration>GLPI Inventory>Network>Remote devices to inventory (VMware), click+ AddAdd:
a name
a comment (optional)
the host type
authentication (see Authentication for remote devices(VMware))
the ESX server IP

Authentication for remote devices (VMware)
Authentication for ESX(i) is necessary for GLPI to access virtual machines.
From
Administration>GLPI Inventory>Network>Authentication for remote hardware (VMware), click+ AddAdd:
a name
a comment (optional)
the type
the login
the password

Discovery status
Displays the results of network discoveries performed (status, task start and end time, number of devices discovered, etc.).

Network inventory status
Displays the results of network inventories performed (status, task start and end time, number of devices discovered, etc.).
Deploy
Package Management
This tab allows you to manage the packages you wish to deploy to your workstations. When you create a new package, you can specify conditions for which this package will be deployed.
Audits
Thanks to audits, you can define execution criteria. For example, if the registry key value exists (meaning the software is installed) and the disk size is greater than 20 GB, then the application will be installed. You can define for each audit whether this step prevents or allows the deployment of the package.

Registry:
Registry key exists
Registry value exists
Registry key missing
Registry value missing
Registry value equals to
Registry value not equals to
Type of registry value equals to
File
File exists
File is missing
file size is greater than
file size is equal to
file size is lower than
the SHA-512 hash value matches
the SHA-512 hash value mismatch
Directory
Directory exists
Directory is missing
Other
Free space is greater than
If any of the audits fail, you will be able to configure the task's behavior for each criterion.
In case of failure:
Abort job
Skip the job
Start job now
Report info
Report warning
Files
You can download a file (msi, exe, zip, etc.) either from your computer or from the GLPI server (files/_plugins/glpiinventory/upload/).

Type: Choose the file from your PC or the GLPI server
File: Upload the desired file
Uncompress: Indicate if the file should be decompressed before installation
P2P: Allows the file to be installed from another client machine
Retention - Minute(s): Defines for how long the installation file can be kept on the client machine
Actions
Allows defining a list of actions before or after the package installation.
Command: List of commands to execute on the package
Move: Move a file from a source to a destination
Copy: Copy a file from a source to a destination
Delete directory
Create directory
For each action, you will need to define either the list of commands to perform, or the files/folders and paths to add/move/delete.

User interactions
It is possible to leave a message for users in several cases:
Before download
After download
After actions (actions from the previous step)
On download failure
On action failure
For each interaction, you can either customize it completely on the fly or use a template.

Mirror servers
Mirror servers allow you to specify where the packages to be installed are located during remote deployment. You can add as many as needed.
From
Administration>GLPI Inventory>Deploy>Mirror Servers, click+ AddEnter:
A name
A location (See location)
Comments (optional)
Active : Yes / No
Mirror server address
Save your entry

User Interaction Templates
User interaction templates allow defining which actions will be sent to the user when they are defined in package remote deployment. You can also define the behavior of each button based on the user's response.

General
From
Administration>GLPI Inventory>Deploy>User Interaction Templates,click+ Add.Enter:
A name
The interaction format
The interaction type (in the form of a button)
OK
OK (asynchronous)
OK - Cancel
Yes - No
Retry - Cancel
Abort- Retry - Ignore
Cancel - Try - Continue
Yes - No - Cancel
The alert icon:
None
Warning
Information
Error
Question
Retry job after
Maximum number of retries
The duration of alert display
When an interaction is requested, the user will receive a popup with the action you have configured.
Behavior
Each button can have a different behavior depending on the action. You can define these in the Behavior tab.

For each button you can define whether the action should:
Contiue job with no user interaction
Retry job later
Cancel job
List of buttons
Yes :
No
Cancel
No active session
Alert timeout exceeded
Several active sessions
Guide
SNMP Inventory
The guide helps you configure your SNMP inventory step by step, taking you through each necessary stage for its proper configuration.

Last updated