This forum is used to centralized feature requests and ideas for Fusioninventory, an opensource inventory and software deployment tool.

Fusioninventory for GLPI is a specialized plugin for GLPI.

Fusioninventory agent is a multi-platform agent to collect platforms inventory and helps to push and centralize them on a GLPI server.



+16
Started

Inventory databases

Walid Nouh 1 year ago • updated by Kaitlyn Smerd 7 months ago 1

Perform database inventory (MySQL/MariaDB, Oracle, Postgresql, etc)

+14

fusioninventory agent and plugin SMART info disk

adamcios 12 months ago • updated by Karol Briegmann 12 months ago 3

is any possible to get by agent all info from hdd S.M.A.R.T. and with

compare with drivedb.h ( smartmontools drive database file). Info from

fast smart hdd test should be sent to glpi and put to disk info. This

info should be stored last 3 or more test and compare potential

indicators of imminent electromechanical failure.

When something wrong will starts with disk (potential failure) for

instance Reallocated Sectors Count or Read Error Rate grow then

technician should be inform that something wrong aproach. Even fusion in glpi can autocreate ticket with information problem with disk komp etc....






+13

Can wakeup computer from glpi inventory page

Vallee Romain 1 year ago 0

wakeup pc from glpi inventory page instead create task ...

+9
Under review

Easier way to support more SNMP devices or improve their information retrieval

Óscar Beiro - TICgal 8 months ago • updated by fusioninventory 4 months ago 5

AFAIK, if your snmp devices is not supported, or correctly detected you have to report it in Github and maybe someone would add it.


It would be great to use some kind of templates. where running an SNMPWalk you could identify the right OID, and ask fusioninventory agent to retrieve them for this particular model.


A central repository where the community could share their templates, would be great.


Right now, I'm thinking about printers, which I can get total printed pages easily, but not BW, and color, because fusion always return 0 in all of this fields.

It could be used for every other device, though.

+7

Return Windows 10 version

bjouana 7 months ago 0

Return the version of Windows 10 running on the computer (1511,1607 or 1703)

+6
Planned

Reduce the waste of resources of FusionInventory-Agent

Tomás Abad 5 months ago • updated by Guillaume Rousse 4 months ago 3

   Before FusionInventory-Agent v2.3.18 the tasks that the agent executed and its order were hard-code defined: first the task Inventory, afterwards the task Deploy, afterwards the task NetDiscovery, and so on (sorry, this probably isn't the real order); the only way to modify that was installing or not the tasks or making use of --no-task option, that was all. But FusionInvenotry-Agent v2.3.18 changed this behaviour.


   FusionInventory-Agent v2.3.18 introduced the new --tasks option with which it was possible not only to indicate which tasks to run but, also, in what order. But not only that, it allowed to run a task more than one time.


   The --tasks option allows to do interesting things. Regarding to deploy packages, for example, it now allows to maintain an inventory more faithful to reality since it isn't necessary to wait for the agent refresh the inventory data so that deployed packages appear in FusionInventory for GLPI.


   Now it's enough to set tasks=Inventory,Deploy,Inventory,... (don't forget the last three dots; it means exactly "and the other tasks") to be sure than a) FusionInventory for GLPI going to have got an up to date information before to try an hipothetical or possible Deploy task execution and b) FusionInventory for GLPI going to have got an up to date information after that hipothetical or possible Deploy task execution.


   The new --tasks option introduces the advantage of modify the task schedules behaviour of the FusionInventory-Agent but it also introduces a side effect not so desirable. The side effect is an inefficient task execution and waste of resources. This is an example.


   Set the --tasks option to Inventory,Deploy,Inventory,... (that is our configuration for more than fifteen thousand computers) is a good choice whether you have planned deploy packages because with it it's possible to maintain an inventory more faithful to reality. And yes, this is true, but you pay a high price in consumption of CPU, time and bandwidth, and not only in the side of the client. Why?. It's very simple. Most of time, the FusionInventory-Agent will not have to do any Deploy task so it will run two consecutive Inventory tasks with practically the same result; and that is a waste of resources.


   But also it's possible to set the --tasks option to esoteric configurations like this: Inventory,Inventory,Inventory,.... And yes, I know this is a stupidity, but this stupidity may be possible.


   I have thought about this problem during some time and I think that there could be a simple solution for both problems (that really are the same): keep track of what has been the last executed task and skip the execution of the next one whether it is of the same kind.


   That is all. Regards,

+5

Discover stack switches

bacus99 6 months ago • updated by Walid Nouh 4 months ago 1

Add stacked switch discovery and inventory

+5
Under review

automatic rename of fusioninventory agent

narutobaka 11 months ago • updated by Skye Eve 7 months ago 2

Hi


(cf my post on fusioninventory forum here : http://forum.fusioninventory.org/viewtopic.php?id=3462)


Actually when you change computer's name, fusioninventory agent name don't change automatically.


You need to delete /var directory to do that.


It would be nice to implement this.


cordialy

+4
Under review

Update debian package

Óscar Beiro - TICgal 6 months ago • updated by fusioninventory 4 months ago 4

This request has two alternatives:


  1. Update Fusioninventory repository: http://debian.fusioninventory.org/ adding the new version
  2. Add a new package for Debian stretch which has been recently frozen. I guess this one is going to be harder to achieve.



+4

Network WMI inventory

fusioninventory 1 year ago • updated by David DURIEUX 1 year ago 5

Add a task to scan and inventory win32 platform in a network using WMI protocol

+3

Mail notification alert - New Import assets (Computers as principal)

thelordbat 2 months ago • updated by Óscar Beiro - TICgal 2 months ago 1

Basicaly create a mail notification when fusion inventory add a new asset. At the start will be nice to alert about new computers.


Thanks!

+3
Under review

Set a prearranged (and tidy) tasks execution plan

Tomás Abad 4 months ago • updated by fusioninventory 4 months ago 2

   With FusionInventory Agent v2.3.20 (and probably previous versions) it isn't possible to know the order in which the tasks of agent will be executed, basically because there isn't a prearranged tasks execution plan. Each time FusionInventory Agent (FIA) is executed it builds a different Planned tasks as it easily verifiable.


C:\>"%ProgramFiles%\FusionInventory-Agent\fusioninventory-agent.bat" --version
FusionInventory Agent (2.3.20)
Provided by Teclib
Installer built with Appveyor on Fri Jun  2 06:15:46 UTC 2017
C:\>"%ProgramFiles%\FusionInventory-Agent\fusioninventory-agent.bat" --config none --debug --local "%SystemRoot%\Temp" --force --logger File --logfile "%SystemRoot%\Temp\fusioninventory-agent-exec_1.log"
C:\>"%ProgramFiles%\FusionInventory-Agent\fusioninventory-agent.bat" --config none --debug --local "%SystemRoot%\Temp" --force --logger File --logfile "%SystemRoot%\Temp\fusioninventory-agent-exec_2.log"
C:\>"%ProgramFiles%\FusionInventory-Agent\fusioninventory-agent.bat" --config none --debug --local "%SystemRoot%\Temp" --force --logger File --logfile "%SystemRoot%\Temp\fusioninventory-agent-exec_3.log"
C:\>type "%SystemRoot%\Temp\fusioninventory-agent-exec_1.log"
[Mon Jul 10 12:52:22 2017][debug] FusionInventory Agent (2.3.20)
[Mon Jul 10 12:52:22 2017][debug] Configuration directory: C:\Archivos de programa\FusionInventory-Agent/etc
[Mon Jul 10 12:52:22 2017][debug] Data directory: C:\Archivos de programa\FusionInventory-Agent/share
[Mon Jul 10 12:52:22 2017][debug] Storage directory: C:\Archivos de programa\FusionInventory-Agent/var
[Mon Jul 10 12:52:22 2017][debug] Lib directory: C:\Archivos de programa\FusionInventory-Agent/perl/agent
[Mon Jul 10 12:52:22 2017][debug] [target local0] Next server contact planned for Mon Jul 10 13:30:32 2017
[Mon Jul 10 12:52:22 2017][debug] Available tasks:
[Mon Jul 10 12:52:22 2017][debug] - WakeOnLan: 2.2
[Mon Jul 10 12:52:22 2017][debug] - NetInventory: 2.2.2
[Mon Jul 10 12:52:22 2017][debug] - Inventory: 1.2
[Mon Jul 10 12:52:22 2017][debug] - NetDiscovery: 2.2.2
[Mon Jul 10 12:52:22 2017][debug] - ESX: 2.2.2
[Mon Jul 10 12:52:22 2017][debug] - Deploy: 2.3
[Mon Jul 10 12:52:22 2017][debug] - Collect: 2.4.0
[Mon Jul 10 12:52:22 2017][debug] Planned tasks:        <----------(*)
[Mon Jul 10 12:52:22 2017][debug] - WakeOnLan: 2.2
[Mon Jul 10 12:52:22 2017][debug] - NetInventory: 2.2.2
[Mon Jul 10 12:52:22 2017][debug] - Inventory: 1.2
[Mon Jul 10 12:52:22 2017][debug] - NetDiscovery: 2.2.2
[Mon Jul 10 12:52:22 2017][debug] - ESX: 2.2.2
[Mon Jul 10 12:52:22 2017][debug] - Deploy: 2.3
[Mon Jul 10 12:52:22 2017][debug] - Collect: 2.4.0
[Mon Jul 10 12:52:22 2017][info] Provided by Teclib
[Mon Jul 10 12:52:22 2017][info] Installer built with Appveyor on Fri Jun  2 06:15:46 UTC 2017
[...]
C:\>type "%SystemRoot%\Temp\fusioninventory-agent-exec_2.log"
[Mon Jul 10 12:56:21 2017][debug] FusionInventory Agent (2.3.20)
[Mon Jul 10 12:56:21 2017][debug] Configuration directory: C:\Archivos de programa\FusionInventory-Agent/etc
[Mon Jul 10 12:56:21 2017][debug] Data directory: C:\Archivos de programa\FusionInventory-Agent/share
[Mon Jul 10 12:56:21 2017][debug] Storage directory: C:\Archivos de programa\FusionInventory-Agent/var
[Mon Jul 10 12:56:21 2017][debug] Lib directory: C:\Archivos de programa\FusionInventory-Agent/perl/agent
[Mon Jul 10 12:56:21 2017][debug] [target local0] Next server contact planned for Mon Jul 10 13:28:14 2017
[Mon Jul 10 12:56:21 2017][debug] Available tasks:
[Mon Jul 10 12:56:21 2017][debug] - Deploy: 2.3
[Mon Jul 10 12:56:21 2017][debug] - ESX: 2.2.2
[Mon Jul 10 12:56:21 2017][debug] - Collect: 2.4.0
[Mon Jul 10 12:56:21 2017][debug] - WakeOnLan: 2.2
[Mon Jul 10 12:56:21 2017][debug] - NetDiscovery: 2.2.2
[Mon Jul 10 12:56:21 2017][debug] - NetInventory: 2.2.2
[Mon Jul 10 12:56:21 2017][debug] - Inventory: 1.2
[Mon Jul 10 12:56:21 2017][debug] Planned tasks:        <----------(*)
[Mon Jul 10 12:56:21 2017][debug] - Deploy: 2.3
[Mon Jul 10 12:56:21 2017][debug] - ESX: 2.2.2
[Mon Jul 10 12:56:21 2017][debug] - Collect: 2.4.0
[Mon Jul 10 12:56:21 2017][debug] - WakeOnLan: 2.2
[Mon Jul 10 12:56:21 2017][debug] - NetDiscovery: 2.2.2
[Mon Jul 10 12:56:21 2017][debug] - NetInventory: 2.2.2
[Mon Jul 10 12:56:21 2017][debug] - Inventory: 1.2
[Mon Jul 10 12:56:21 2017][info] Provided by Teclib
[Mon Jul 10 12:56:21 2017][info] Installer built with Appveyor on Fri Jun  2 06:15:46 UTC 2017
[...]
C:\>type "%SystemRoot%\Temp\fusioninventory-agent-exec_3.log"
[Mon Jul 10 12:58:02 2017][debug] FusionInventory Agent (2.3.20)
[Mon Jul 10 12:58:02 2017][debug] Configuration directory: C:\Archivos de programa\FusionInventory-Agent/etc
[Mon Jul 10 12:58:02 2017][debug] Data directory: C:\Archivos de programa\FusionInventory-Agent/share
[Mon Jul 10 12:58:02 2017][debug] Storage directory: C:\Archivos de programa\FusionInventory-Agent/var
[Mon Jul 10 12:58:02 2017][debug] Lib directory: C:\Archivos de programa\FusionInventory-Agent/perl/agent
[Mon Jul 10 12:58:02 2017][debug] [target local0] Next server contact planned for Mon Jul 10 13:37:23 2017
[Mon Jul 10 12:58:02 2017][debug] Available tasks:
[Mon Jul 10 12:58:02 2017][debug] - NetDiscovery: 2.2.2
[Mon Jul 10 12:58:02 2017][debug] - WakeOnLan: 2.2
[Mon Jul 10 12:58:02 2017][debug] - Inventory: 1.2
[Mon Jul 10 12:58:02 2017][debug] - ESX: 2.2.2
[Mon Jul 10 12:58:02 2017][debug] - Deploy: 2.3
[Mon Jul 10 12:58:02 2017][debug] - NetInventory: 2.2.2
[Mon Jul 10 12:58:02 2017][debug] - Collect: 2.4.0
[Mon Jul 10 12:58:02 2017][debug] Planned tasks:        <----------(*)
[Mon Jul 10 12:58:02 2017][debug] - NetDiscovery: 2.2.2
[Mon Jul 10 12:58:02 2017][debug] - WakeOnLan: 2.2
[Mon Jul 10 12:58:02 2017][debug] - Inventory: 1.2
[Mon Jul 10 12:58:02 2017][debug] - ESX: 2.2.2
[Mon Jul 10 12:58:02 2017][debug] - Deploy: 2.3
[Mon Jul 10 12:58:02 2017][debug] - NetInventory: 2.2.2
[Mon Jul 10 12:58:02 2017][debug] - Collect: 2.4.0
[Mon Jul 10 12:58:02 2017][info] Provided by Teclib
[Mon Jul 10 12:58:02 2017][info] Installer built with Appveyor on Fri Jun  2 06:15:46 UTC 2017
[...]

   This behaviour isn't an error in itself but it has got, or may to have, annoying side effects.


   The first one is that analyse the log file of FIA may be a chaotic task because that what you are looking for is before or after something most of the time, but rarely where you expect it.


   The second one is regarding FusionInventory for GLPI (FI4G) and is that a task of FI4G may have a strange behaviour depending of order the tasks of FIA are executed. For example, assuming that the elements of Network_A aren't in GLPI, a FI4G Network_A task with two jobs, Inventory_Network_A (NetInventory Module) and Discovery_Network_A (NetDiscovery Module), may make that GLPI have only knowledge of elements of Network_A (whether FIA NetInventory task is executed before NetDiscovery task) or that it have knowledge of elements of Network_A and their data (whether FIA NetInventory task is executed after NetDiscovery task) after the first execution of FI4G Network_A task.


   This second side effect could be corrected with the use of --tasks option but only whether all tasks are included; if '...' (three dots) are used with --tasks option, it's not possible to know the order of those tasks that aren't explicitly included.


   So, it could be good prearranged a tasks execution. This is my proposal.


  1. Inventory
  2. Collect
  3. Deploy
  4. WakeOnLan
  5. NetDiscovery
  6. NetInventory
  7. ESX

   First, all the tasks regarding local machine then the rest of tasks, always launching NetDiscovery before NetInventory.


   With --tasks=inventory,deploy,inventory,... the Planned tasks would be:



  1. Inventory
  2. Deploy
  3. Inventory
  4. Collect
  5. WakeOnLan
  6. NetDiscovery
  7. NetInventory
  8. ESX

Best regards.

+3
Started

Upgrade 7zip in Windows Agent from 15.14 to 16.04

tomasz157 6 months ago • updated by fusioninventory 2 weeks ago 1

7z.exe and 7z.dll included in Windows Agent installer are outdated.

+3
Completed

Inventory docker containers

Walid Nouh 1 year ago • updated by fusioninventory 9 months ago 3

Enhance the agent to inventory docker containers

+2

Improve UI for deployment audits

Walid Nouh 4 months ago 0

The process of creating an audit is not as simple as it seems.

It's mandatory to better explain how audit work : what is done when condition is met or not met.


Maybe describe the audit as a sentence, as it's displayed in the audits list

+2

patch management

finalbeta 4 months ago 0

System Patch management


  • Allow fusioninventory to list (packages/windows updates) that are available for update.
  • Allow fusioninventory to list installed updates
  • Allow fusioninventory to apply available patches
  • Apply policy to device to automate patch installation window (day, hour) + reboot at the end.

Allow fusioninventory to list system patches and select/apply them for installation. 

Allow fusioninventory to apply a policy to a system that schedules installation of patches (possibly allow a system reboot at the end) (for example, 

+2

Ability to choose how to wakeup an agent

Walid Nouh 5 months ago 0

It's would be to have an option to define how to wake an agent up:


1/ fqdn only

2/ fqdn + ip

3/ ip + fqdn

4/ ip only

+1

More information within ESX agent scan (OS, IP)

JTSD 3 months ago • updated 3 months ago 2

It would be very useful when agent could take OS kind and IP of a VM.

Based on information from an agent plugin should add visibly relation between VM and a Host - now there's possible to see only VMs runing on specific host, not particular Host name in properties of VM created in GLPI as a Computer.


+1

Improve computer models management between Fusion Inventory, GLPI and automatic provisionning tools

blaise.thauvin 3 months ago 0

Hi,


I have built out of GLPI, FusionInventory, CustomFields, Microsoft MDT (Deployment tool) and a home made database synchronisation tool something that is close to SCCM at very low cost.

I plan to release it as soon as it is clean enough to be shared.

Basically, I use the data from GLPI to feed the MDT database. This enable automatic OS deployment just pressing "F12" at boot (PXE boot to MDT). Our technicians just choose the OS version, the machine name, the additional applications (MS office, OpenOffice....) in GLPI and that's it.

In order to manager hardware specificities, I rely on the computer model to set some defaults, model based values.

This used to work fine until the latest update 2.3.21 which introducd commercial names instead of technical codes. A lot of machines where identified with a technical code for the model rather than a commercial name. This code is what MDT relies on to identify a model (plus, several models with slightly different hardware may often the same commercial name). The output on screen is much nicer (20C600JJFR is now ThinkPad Edge E540) but MDT is broken.


Therefore my suggestion is:

- Have GLPI manage both the commercial name and the technical code for computer models.

- Add one column to the glpi_computermodels table for code. Make this column indexed unique while names can be non unique. I hear there is a "product number field" in preparation in GLPI 9.2, maybe this is the right place.

- Show both code and name on computer description page.

- Adapt Fusion Inventory import code to store both informations.

Indeed, there will be an issue when two different versions of FI will report a different name for the same code. I guess the rule should be:

- If code and name reported are the same and conflict with an existing model where they differ, keep the one that differs as this is probably more up to date.

- If code and name reported are different, then update table. Last to talk wins!


In the mean time I would love to get an additional setting in the plugin which would let me choose wich code (MMODEL or SMODEL) I want to store in GLPI. Indeed this is open source software so I will probably do a dirty patch on the code to fix my problem, but I'd rather have a proper and maintained solution.


Thanks in advance.