Improve computer models management between Fusion Inventory, GLPI and automatic provisionning tools
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 relase 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 default, model based values. This used to work fine until the lastest update (21) in FusionInventory. 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.
- 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!
Customer support service by UserEcho
Yes this is a change that we have introduced in agent 2.3.21.
This was a volontary change, as commercial model is what is needed by user and manufacturer's technical support.
The change was announced here : http://fusioninventory.org/2017/08/01/fusioninventory-agent-2.3.21.html , I think you missed it ^^
Could you please first open a suggestion on fi's suggestion site here : http://fusioninventory.userecho.com/ ?
Starting with GLPI 9.2, we've introduced a "Product number field, linked to a computer model". We may try to fill this field with the technical value.
This is exactly what we are trying to do with our MDT. Please notify us when your code is ready for sharing,
I could send you my bash script but the design is tightly linked to our architecture (and there are still a few bugs). Not sure it will work for you.
My plan once it works is to rewrite it more nicely in PHP and maybe make it a plugin, but I need to learn a lot about GLPI to to that.... and I don't have that much spare time.
If you want to learn how to create a plugin, you can read our documentation here:
Thanks for this pointer, it is exactly what I need to start.
The plugin is now available on github. The name is glpi2mdt. It should appear soon on the GLPI plugins website.
Please let me know it is works for you. It is only in the early stages of development but is works. I know need feedback to know where to go first in future enhancements.