Using the WAPT console advanced


Some functionalities detailed here are only available with the Enterprise version of WAPT.

Software inventory as registered in the Windows registry of the host

Software inventory as registered in the Windows registry of the host

Using profile bundles in WAPT


New in version 1.7: Enterprise

Working principle

WAPT Enterprise offers Active Directory profile bundle functionality.

It automates installation of WAPT software and configuration packages on hosts, based on their membership to Active Directory Computer Security Groups.


Active Directory Computer’s security groups contains Computers, not Users.

Active Directory computer group

Active Directory computer group

Automatically installing software and configurations based on user and user group membership is not implemented with WAPT. This use case is better served with the differentiated self-service feature that is also available with WAPT Enterprise.

Creating profile bundle packages in WAPT console

You can create profile bundle packages by clicking on Bundles -> Create AD Profile.

Click on New host AD profile to create a *profile* bundle

Click on New host AD profile to create a profile bundle



  • the profile package name must be exactly the same as the AD Security group name;

  • the profile package name is case sensitive;


  • AD Security group: HW_laptops;

  • WAPT profile bundle: HW_laptops;

A window opens and you are prompted to choose which packages must be in the just created profile bundle.

Adding packages to profile bundle

Adding package to profile bundle

Save the profile bundle package and it will be uploaded to the WAPT server.

Using Organizational Unit packages in WAPT


New in version 1.7: Enterprise

Working principle

WAPT Enterprise offers organizational unit packages functionality.

It automates software installations based on your Active Directory infrastructure.

The WAPT agent is aware of its position in the Active Directory tree structure, therefore it knows the hierarchy of Organizational Units that concerns it, for example:


If an Organizational Unit package is defined on each level, the WAPT agent will automatically download packages and configurations that are attached to each level, by inheritance, and will apply attached packages and their dependencies.

Filters and actions available with Organizational Units

WAPT console showing options applicable to OU

WAPT console showing options applicable to OU


You can see in the picture that update and upgrade actions can be performed through this menu, thus selecting hosts by their Organizational Unit.

In the Enterprise version, you may filter how hosts are displayed based on the Active Directory OU they belong to.

The checkbox Include hosts in subfolders allows to display hosts in subfolders.

Creating Organizational Unit packages in the WAPT console

You can create unit packages by Right-clicking on an OU ‣ Create or edit the unit package.

Right-click on OU to create unit package

Right-click on OU to create unit package.

A window opens and you are prompted to choose which packages must be included in the unit bundle.

Adding packages to unit bundle

Adding package to unit bundle.

Save the package and it will be uploaded to the WAPT server.

Faking Organizational Units for WORKGROUP hosts

It can happen that some specific hosts cannot be joined to an Active Directory domain.

With that specificity, such hosts do not show up in your Active Directory Organizational Units in your WAPT Console.

To make all hosts show up in the console under the right Organizational Unit, whether they are joined to an AD domain or not, WAPT allows you to specify a fake Organizational Unit WAPT agent configuration file.

The benefits of this trick are:

  • you can manage these hosts with WAPT as if they where joined to the AD;

  • out-of-domain and workgroup hosts are now showing up in AD tree view;

  • unit packages are usable on these hosts;

To setup a fake Organizational Unit on hosts, create an empty WAPT package;

wapt-get make-template demo-configure-fake-ou

Then use the following code:

# -*- coding: utf-8 -*-
from setuphelpers import *

uninstallkey = []

def install():

  print('Setting Fake Organizational Unit')

The host_organizational_unit_dn must be like below in wapt-get.ini:



Stick to a specific case with your host_organizational_unit_dn (don’t mix “dc”s and “DC”s, “ou”s and “OU”s…). Follow the case used in the DN/computer_ad_dn fields in the hosts grid.

Using WAPT Windows Update Agent (WAPTWUA)


New in version 1.7: Enterprise


Since version 1.7, WAPT is able to manage Windows Updates on your endpoints.

Working principle

Regularly, the WAPT server downloads an updated file from Microsoft servers. By default, downloads happen once a day and no download is triggered if the file has not changed since the last download.

WAPT Windows Update flow process

WAPT Windows Update flow process.


In some cases, you may wish to push new KBs before the next Patch Tuesday release.

To do so, you may follow this documentation on packaging .msu files for these Out-of-band updates.

The file is then downloaded by the WAPT agent from its nearest repository and then passed on to the standard WUA Windows utility to crunch the update tree for the host.

Regularly, the host will analyze the available updates using the file. The host will send its list of needed updates as determined by its WUA to the WAPT server.

If an update is pending on the host and if that update is not present on the WAPT server, the server will download the needed update from official Microsoft servers.


This mode of operation allows WAPT to download only the necessary updates on the computers, thus saving bandwidth, download time and disk space.


Downloaded updates are stored:

  • on Linux hosts in /var/www/waptwua;

  • on Windows hosts in C:\wapt\waptserver\repository\waptwua;

The WAPT Windows Update Agent repository download URL is based on the repo_url parameter in wapt-get.ini:

  • in case of repository replication, it is fully operational with WAPT Windows Update to reduce bandwidth use;

  • do not forget to synchronize the waptwua folder if you are replicating your packages with distant repositories;


If in your company, a proxy is needed to go out on the Internet, then be sure to set the proxy server in the waptserver.ini file.

Difference between WAPT Windows Updates and WSUS

WSUS downloads by default the updates for selected categories. This can lead to a very large update database and lots of storage used.

WAPT Windows Update only downloads updates that have been requested by at least one computer client. This helps to keep the local database small (a few 10s of Gigabytes) and it can be easily cleaned up if you want to recover space.

Major OS upgrades

Major OS upgrades are upgrades from one OS version to another. That includes, for example, upgrades from Windows 7 to Windows 10, or from Windows 10 1803 to Windows 10 1903.

Major version upgrades are not handled in the same way as minor OS upgrades. Major upgrades are handled via the download of the new install ISO content (same content as for a fresh install) and running the setup.exe with the correct parameters. This process is the same for WSUS, SCCM and WAPT Windows Updates.

In the case of WAPT Windows Updates, you need to create a OS update package using a template package provided on

Driver upgrades

Driver upgrades via WSUS are not recommended since it is hard to properly handle side effects. In the case of WAPT Windows Updates, DRIVERS ARE NOT DOWNLOADED since they are not referenced in the files provided by Microsoft.

It is recommended to push driver updates via a custom WAPT package. If the driver patch is packaged as a .msu, you may package it as a standard WAPT package.

Just select the .msu file and click create package in the WAPT console to launch the wizard for simplified package creation.

If the driver update is packaged as a .zip containing the .exe file, you can create a WAPT package containing the necessary files and setup.exe binary with the correct silent flag.

Out of band KB

Microsoft sometimes provides OOB updates that are not contained in the index. Those updates are not included in the main update because they may fix a very specific problem or may have drawbacks in some situations.

If you want to deploy an OOB KB update, you can download it from the Microsoft catalog

Just select the .msu file and click create package in the WAPT console to launch the wizard for simplified package creation.


You have to be careful that OOB updates may break your system, be sure to read the prerequisites on the Microsoft bulletin corresponding to the update and thoroughly test the update.

Configuring WAPTWUA on the WAPT agent

WAPTWUA is configured in wapt-get.ini.

Add [waptwua] section.

You then have several options:

Configuration options in the [waptwua] section in the wapt-get.ini


Default Value




Enable or disable WAPTWUA on this machine.



Download updates directly from Microsoft servers.



Set if missing update is authorized or not by default



Set the Windows Update scan recurrence (Will not do anything if waptwua package rule or file have not changed) (ex: 2h)



Set the Windows Update install recurrence (Will do nothing if no update is pending) (ex: 2h)



Install update when the machine will shutdown



Set a deferred installation delay before publication in the repository (ex: 7d)



Define a severity list that will be automatically accepted during a WAPT windows update scan. ex: Important, Critical, Moderate


These options can be set when generating the agent.

Example [waptwua] section in wapt-get.ini file:

enabled =true
default_allow =False

The install_scheduling option will try every 12 hours to install updates on the client. It is not in graphical options due to a potential danger. Indeed, trying to install updates on your IT infrastructure while working hours can impact your production.

When you create the waptagent.exe from your console, these options are equivalent to this:

WAPT Windows Update agent options

WAPT Windows Update agent options


if default_allow option is True and Wapt WUA is enabled too, clients will contact the WAPT Server and ask to download the missing updates. The clients will install missing updates on their own at time of upgrade.

Example package source code to modify [waptwua] settings:

def install():

Using WAPTWUA from the console

The WAPT Windows Update Agent tab in the WAPT console comes with two sub-menus to manage WAPTWUA.

WAPTWUA Package tab

The WAPTWUA Package tab allows you to create waptwua rules packages.

  • when this type of package is installed on a machine, it indicates to the WAPTWUA agent the authorized or forbidden KBs;

  • when several waptwua packages are installed on a machine, the different rules will be merged;

  • when a cab is neither mentioned as authorized, nor mentioned as prohibited, WAPT agents will then take the value of default_allow in wapt-get.ini;

If a Windows update has not yet been downloaded to the WAPT server, then the WAPT agent will flag the update as MISSING.


  • if the WAPTWUA agent configuration is set to default_allow = True, then it will be necessary to specify the forbidden cab;

  • if the WAPTWUA agent configuration is set to default_allow = False, then it will be necessary to specify the authorized cab;


  • to test updates on a small set of computers, you can set WAPTWUA default value to default_allow = False;

  • you can test updates on a small sample of hosts and if everything is good, you can release the updates to the entire fleet of computers;

Creating a *waptwua* Package

Creating a waptwua Package

Windows Updates list tab

The Windows Update List tab lists all needed Windows Updates.


The server does not scan the itself, it lets the Windows Update Agent utility present on all Windows machines do it. If an update seems to you as missing from the list, you must run a scan on one of the machines present in the console. If you run a WUA scan on a Windows 7 agent, the CAB and Windows 7 files will be displayed on the :guilabel`Windows Update List` tab.

The left pane displays update categories, allowing you to filter by:

  • criticality;

  • product;

  • classification;

In the right panel grid, if the Downloaded on column is empty, it means that the update has not yet been downloaded by the WAPT server and is not present on the WAPT server (This update is not missing on any host).

  • you can force the download of an update by right-clicking ‣ Download;

  • you can also force the download of the file with the Download WSUSScan cab from Microsoft Web Site button;

  • you can see the Windows Updates download on the server with the Show download task button;


To cleanup your waptwua folder, you can remove no longer needed Windows updates. WAPT server will only re-download deleted updates if one of the WAPT equipped hosts requests it;

Listing of Windows Update

Listing of Windows Update

Launching WUA on clients

From the console you have three options.

Windows Update action buttons available in the WAPT console

Windows Update action buttons available in the WAPT console

The Trigger the scan of pending Windows Updates button will launch the scan on the client and list all updates flagged for the OS. You can scan the client from the console like that or by using wapt-get waptwua-scan from the command-line.


Every 30 minutes, the WAPT Server will look for updates that have been requested at least once by WAPT Clients and that have not yet been downloaded and cached. If an update is pending, the WAPT Server will download it from official Microsoft servers.

You can force this scan with the Download index and missing cabs from Microsoft Web site button in tab Windows Updates ‣ Windows Updates list

Pending Windows Updates showing in the WAPT console

Pending Windows Updates showing in the WAPT console

If you want to download from the console, use the Trigger the download of pending Windows Updates button.

The command-line for downloading kb’s from the client is wapt-get waptwua-download, it will scan the current status of Windows against current rules, download missing kb’s and send the result to the server.

If you want to install the pending update(s), use wapt-get waptwua-install from the command-line prompt.

If you want to trigger the installation from the console, click on Trigger the install of pending Windows Updates button.


When you want to install the pending updates stored in cache, the WAPT Service triggers the WUA service.

The WAPT Service will enable and start the WUA Service temporarily to install the updates. When updates are installed, waptservice will stop and disable the WUA service until the next cycle.

Notion of UpdateID

In WAPT we don’t use kbids but updateids.

This allows us to be finer in the management of updates.

Duplicate kb

In this example, KB4537759 appears multiple times because there are 3 different updateids:

  • win10 1803;

  • win10 1903;

  • win10 1909;

You should therefore authorize an updateids and not a kb ids.

WAPT does not force Windows update uninstall

Uninstalling a Windows update can be dangerous for the machine. When an update is detected as forbidden by WAPT, its uninstallation will NOT be forced.

If you really want to uninstall an update, you should package the KB that you to uninstall as a WAPT package.

Here is an example:

from setuphelpers import *

uninstallkey = []

def install():
        with EnsureWUAServRunning():
                run('wusa /uninstall /KB:4023057')

Video demonstration

Using the reporting functions in WAPT


New in version 1.7: Enterprise

Working principle

WAPT Enterprise offers advanced reporting capabilities.

Indeed, who better than you to know what you want in your report.

With WAPT we offer to write your own SQL queries to display the result in the wapt console.

WAPT query Designer

The query designer offers you the ability to edit your own queries on the WAPT PostgreSQL database.

To create a new report, click on Reporting ‣ Design Mode ‣ New query.

Designing a query in WAPT reporting

Designing a query in WAPT reporting


  • to rename a query, press the F2 key;

  • in the top banner, you can write your SQL query;

To edit / modify / save your reports:

  • the Reload queries button is used to reload queries saved on the server, for example, if a colleague has just edited a new query;

  • the New query button will add a new blank query to the list;

  • the Delete query button will delete the selected query from the WAPT server;

  • the Export to Excel button will export the result of your query to a spreadsheet;

  • the Save queries button will save your query to the WAPT server;

  • the Duplicate button will duplicate an existing query to avoid writing a request from scratch;

  • the Execute button executes the selected query;


  • the queries are saved in the PostgreSQL WAPT database;

  • the shortcut CTRL+space allows you to build your queries more effectively;

Query examples

Computers query

  • counting hosts:

    select count(*) as "Nb_Machines" from hosts
  • listing computers:

    from hosts
    order by 4,3,1
  • listing computers MAC addresses and IP:

    select distinct unnest(mac_addresses) as mac,
    unnest(h.connected_ips) as ipaddress,
    h.manufacturer||' '||h.productname as model,
    from hosts h
    order by 1,2,3
  • listing Windows versions:

    host_info->'windows_version' as windows_version,
    os_name as operating_system,
    count(os_name) as nb_hosts
    from hosts
    group by 1,2
  • listing operating systems:

    select host_info->'windows_version' as windows_version,
    os_name as "Operating_System",
    count(os_name) as "Nb_Machines"
    from hosts
    group by 1,2
  • listing hosts not seen in a while:

    h.connected_users from hostsoftwares s
    left join hosts h on h.uuid=s.host_id
    where s.key='WAPT_is1'
    and h.listening_timestamp<'20190115'
  • filtering hosts by chassis types:

    select case
     when 'Portable' then '01-Laptop'
     when 'Notebook' then '01-Laptop'
     when 'Laptop' then '01-Laptop'
     when 'Desktop' then '02-Desktop'
     when 'Tower' then '02-Desktop'
     when 'Mini Tower' then '02-Desktop'
     else '99-'||(dmi->'Chassis_Information'->>'Type')
    end as type_chassis,
    string_agg(distinct coalesce(manufacturer,'?') ||' '|| coalesce(productname,''),', '),
    count(*) as "Nb_Machines" from hosts
    group by 1
  • listing of hosts with their Windows Serial Key:

    host_info->'windows_product_infos'->'product_key' as windows_product_key
    from hosts
    order by 3,1

WAPT query

  • listing WAPT packages in WAPT server repository:

    from packages
    group by 1,2,3,4,5,6
  • listing hosts needing upgrade:

    string_agg(distinct lower(s.package),' ')
    from hosts h
    left join hostpackagesstatus s on s.host_id=h.uuid and s.install_status != 'OK'
    where (last_seen_on::date > (current_timestamp - interval '1 week')::date
    and host_status!='OK')
    group by 1,2,3,4

Packages query

  • listing packages with their number of installation:

    from hostpackagesstatus s
    where section not in ('host','unit','group')
    group by 1,2,3,4,5,6

Software query

  • listing WAPT Discovery agents:

    from hostsoftwares s
    left join hosts h on h.uuid=s.host_id
    and (name ilike 'WAPT%%Discovery%%' or name ilike 'WAPT %%')
  • listing hosts with their 7zip version associated:

    from hosts, hostsoftwares
    where ilike '7-zip%%'
    and hosts.uuid=hostsoftwares.host_id
    order by hosts.computer_name asc
  • listing hosts with their software:

    s.version,string_agg(distinct lower(h.computer_name),' '),
    count(distinct h.uuid)
    from hostsoftwares s
    left join normalization n on (n.original_name = and (n.key = s.key)
    left join hosts h on h.uuid = s.host_id
    where (n.normalized_name is not null)
    and (n.normalized_name<>'')
    and not n.windows_update
    and not n.banned
    and (last_seen_on::date > (current_timestamp - interval '3 week')::date)
    group by 1,2
  • listing normalized software:

    string_agg(distinct lower(h.computer_name),' '),
    count(distinct h.uuid)
    from hostsoftwares s
    left join normalization n on (n.original_name = and (n.key = s.key)
    left join hosts h on h.uuid = s.host_id
    where (n.normalized_name is not null)
    and (n.normalized_name<>'')
    and not n.windows_update
    and not n.banned
    and (last_seen_on::date > (current_timestamp - interval '3 week')::date)
    group by 1

You can also find several more examples of queries on Tranquil IT’s Forum.

Feel free to post your own queries on the same forum with an explanation of what your query does, ideally with a screen capture or a table showing a sample of your query result.

Normalizing software names

Sometimes, the version of the software or its architecture are an integral part of the software name. When they register with the WAPT Server inventory, they appear as different software whereas they are just one software for us humans.

To solve this problem, we propose to standardize the name of the software with WAPT.

Normalizing the name of software

Normalizing the name of software

  • click Normalize Software Names in the Tools menu;

  • select the software to standardize, for example, all different version of Adobe Flash Player;

  • on the column normalized, press F2 to assign a standardized name to the selected software. Then press Enter;


  • to select several programs, select them with the shift-up/down key combination;

  • you can also indicate a software like windows update or banned (Press spacebar in the corresponding column);

  • press on Import to load the changes from the server;

  • press on Write to save your changes;

You can now run your queries on this standardized name.

Connecting to the WAPT database using a PostgreSQL client

You can connect your WAPT database to a client if you prefer to use a PostgreSQL client.

To do so, you’ll have to change some configuration files on your WAPT server.

  • find out in which version your PostgreSQL is:

    ps -ef | grep -i sql
    postgres   512     1  0 Jan05 ?        00:00:24 /usr/lib/postgresql/12/bin/postgres -D /var/lib/postgresql/12/main -c config_file=/etc/postgresql/12/main/postgresql.conf
  • modify pg_hba.conf of the PostgreSQL version in use. In /etc/postgresql/12/main/pg_hba.conf for Debian and /var/lib/pgsql/12/data/pg_hba.conf for Centos under # IPv4 local connections section, add your address:

    host    wapt             all                 md5

    where is your IP address that is authorized to connect to the WAPT database.

  • allow PostgreSQL to listen on every interface in /etc/postgresql/12/main/postgresql.conf for Debian and /var/lib/pgsql/12/data/postgresql.conf for Centos, section Connection Settings:

    listen_addresses = '*'
  • restart the service for your PostgreSQL version.

    systemctl restart postgresql@12-main.service
  • connect to PostgreSQL on waptserver:

    sudo -u postgres psql template1
  • then give a password to wapt user:


Video demonstration

Using WAPT SelfService


New in version 1.7: Enterprise


With WAPT 1.7 Enterprise you can now filter the list of self-service packages available for your users.

Your users will be able to install a selection of WAPT packages without having to be a Local Administrator on their desktop.

The Users gain in autonomy while deploying software and configurations that are trusted and authorized by the Organization. This is a time saving feature for the Organization’s IT support Helpdesk.

How does it work?

With WAPT 1.7 Enterprise, a new type of WAPT package exists beside base, group, host, profile and unit packages: they are selfservice packages.

Create a *selfservice* package

Create a selfservice package

A selfservice package may now be deployed on hosts to list the different self-service rules that apply to the host.

How to use the selfservice feature?


The selfservice feature is only available with WAPT Enterprise.

In the Discovery version, only Local Administrators and members of the waptselfservice group can access self-service on the agent.

In the Discovery version, it is not possible to filter the packages made accessible to the user.

In the console go to the tab Self-service rules.

You can now create your first selfservice rule package.

  • give a name to your new selfservice package;

  • click on Add to add an Active Directory group (at the bottom left);

  • name the selfservice group (with F2 or type directly into the cell);

  • drag the allowed software and configuration packages for this selfservice group into the central column;

  • add as many groups as you want in the package;

  • save the package and deploy the package on your selection of hosts;

  • once the package is deployed, only allowed packages listed in the selfservice group(s) of which the User is a member will be shown to the logged in User;


  • if a group appears in multiple selfservice packages, then the rules are merged;

  • the authentication used is system authentication, local users and groups, but if the machine is in a domain then authentication and groups will also work with users and groups in the domain;

How to use the self-service on the user station?

The self-service is accessible to users in the start menu under the name Self-Service software WAPT.

It is also available directly in <base>\waptself.exe.

The login and password to enter when launching the self-service are the User’s credentials (local or Active Directory credentials).

The self-service then displays a list of packages available for installation.

Self Service

Self Service

  • the user can have more details on each package with the + icon;

  • different filters are available for the user on the left side panel;

  • the Update Catalog button is used to force a wapt-get update on the WAPT agent;

  • the list of package categories is displayed to the user. To add a category to the list, you must specify the category in the categories section of the control file of the relevant package;

  • the current task list of the WAPT agent is available with the task bar button;

  • it is possible to change the language of the interface with the configuration button at the bottom left.

Customizing the Self Service interface

Adding the Logo of your Organization

In the Enterprise version only of WAPT, it is possible to change the logo that appears in the self-service interface and therefore improve the acceptation of the Self Service feature by your users.

To do this, simply place the logo you want in <wapt>\templates\waptself-logo.png


It is highly recommended to use a .png file with a 200 x 150px resolution.

Managing package categories

Default categories are:

  • Internet;

  • Utilities;

  • Messaging;

  • Security;

  • System and network;

  • Storage;

  • Media;

  • Development;

  • Office​​;

You can create your own categories easily by filling the control file’s categories section of any WAPT package and write a new category of your choice, WAPT will automatically show the package in the new category.

WAPT Agent Settings for WAPT Self-Service

WAPT Agent can be configured to force WAPT SelfService packages filtering to Local Administrators Settings for WAPT Self-Service and Waptservice Authentification.

Configuring a different authentication method for the selfservice

As mentioned above, authentication on WAPT service is configured by default in system mode.

This means that the WAPT service transmits the authentication directly to the operating system; it also recovers the groups by directly interrogating the operating system.

This behavior is defined with the value of service_auth_type in wapt-get.ini. The default value is system.

In this mode we assume that Local Administrators can see all the packages. To change this behavior, modify the value of waptservice_admin_filter in wapt-get.ini.

You may be interested in looking up this article describing the settings for WAPT Self-Service and Waptservice Authentification for more options.

Two additional modes are available starting with version 1.8.2:

  • waptserver-ldap: this mode allows authentication to the WAPT server. The WAPT server will make a LDAP request to verify authentication and groups. Warning ! For this to work, you must have configured LDAP authentication on the WAPT server, (the configuration of the admin group will be ignored) See this article on configuring authentication against Active Directory for more information.

  • waptagent-ldap, This mode allows authentication with an LDAP server identified in wapt-get.ini. The WAPT agent will make a LDAP request to verify authentication and groups.

    You may be interested in looking up this article describing the settings for WAPT Self-Service and Waptservice Authentification for more options.


For the system authentication under GNU/Linux to work correctly, be sure to correctly configure your pam authentication and your nsswitch.conf. The id username command must return the list of the groups the user is member of.

Video demonstration

Synchronizing WAPT inventories to GLPI


New in version 2.0: Enterprise

Working principle

WAPT Enterprise offers synchronization between the inventories of your hosts and Glpi ITSM Software.

The method automatically synchronizes changes on your IT infrastructure with the Glpi server.

Installing the required dependencies

In order to receive inventories on your Glpi server, you’ll need the FusionInventory plugin on your Glpi server.

After installing FusionInventory, you will have an endpoint on your WAPT server to send the inventories to (…/glpi/plugins/fusioninventory/).


You can open the window to configure Glpi with Tools > Manage Wapt to Glpi.

WAPT console showing the Glpi configuration in WAPT

WAPT console showing the Glpi configuration in WAPT

Properties in Glpi Server Properties add the required parameters in the waptserver.ini configuration file.

glpi_server_endpoint = glpi.mydomain.lan/glpi/plugins/fusioninventory/
glpi_server_user = user
glpi_server_pass = password
glpi_server_pause_timeout = 20,15
glpi_inventory_update_delay = 4
glpi_inventory_update_range = 25
  • glpi_server_endpoint: url to FusionInventory plugin where to upload inventories on the glpi server;

  • glpi_server_user, glpi_server_pass: Glpi server credentials;

  • glpi_server_pause_timeout = A,B: pause uploading for A seconds when server takes more than B seconds to respond;

  • glpi_inventory_update_range: every how many uploads do you want the database to be updated, if you stop the upload it will restart at last update;

  • glpi_inventory_update_delay = C: The upload is triggered automatically every C hours if not already running;

Using WAPT to send inventory updates to Glpi

As you can see on the configuration window you can fill in the settings, trigger or stop an upload right from the WAPT console:

  • when you fill in Glpi Server Properties, the configuration is registered on the WAPT server when you click Save;

  • you can retrieve properties already registered on the WAPT server by clicking on Reset (the password is not loaded);

  • the Endpoint field is the Glpi server url to send the inventories to the glpi_server_endpoint;

  • you can trigger an upload without waiting for the scheduled task by clicking Upload;

  • you can stop the upload at any time by clicking Cancel;


The upload status is updated every 15s, you can follow the progress with the status bar.

If you have many hosts, the upload may take a long time. To avoid this, when the upload is triggered, only inventories that have changed are uploaded:

  • with Force upload every inventory is uploaded, ignoring already uploaded data.

Advanced use of the Glpi plugin

To display advanced properties, select the Advanced button.

WAPT console showing the Glpi advanced configuration in WAPT

WAPT console showing the Glpi advanced configuration in WAPT

  • The scheduled task runs every Cron every… hours only if the Endpoint is entered. You can disable the scheduled task by leaving the Endpoint empty. ~> glpi_inventory_update_delay.


If you want to disable automatic upload, you have to Save a blank Endpoint.

  • you can trigger pauses (Pause…) when the server response time is too long (over…). ~> glpi_server_pause_timeout;

  • Update db… sets the database synchronization frequency during upload. ~> glpi_inventory_update_range