You are not logged in.
Hi,
is there a simple way to of grouping software automatically in the root entity in case of a multi-entity platform.
If we have lets say more than 500 entities and 5000 computers, which have the glpi agent installed. The computers are assign to the entity by a rule. So we are getting tons of Software for each entity. In sum we would have a list of 400000 software entries.
In the GLPI documentation is written "In multi-entity mode, the list of software can rapidly become long because of double entries (one software per entity). A better approach can consist in grouping identical software in the same entity (see tab Grouping below), then to make recursive the elements that can be made recursive.". At the end of the software documentation website, there is a manual process for merging the software in the root/mother entity.
Is it possible to perform this process automatically, since we would have to perform the thousands of times?
We tried to do this with a dictionary for software, where the criteria is
"Software > regular expression matches > /(.*)/"
and the Actions are
"Software > Assign the value from regular expression > #0 1234567890" and
"Entity > Assign > rootentity".
We have to rename the software, since the dictionary only works if the name changes. Afterwords we would use a second dictionary to assign the original name and get rid of " 1234567890".
So is there a better approach?
Regards,
Andreas
Offline
Hello, I have found a way to achieve this using the Entities menu. When clicking on a Entity in the Administration -> Entity. You see the information about an Entity and all of it tabs. Under the ''Asset'' tab, go to ''Software creation entity'' and choose your root Entity. There is no need for any dictionnary rules with this feature. Just make sure that you apply the root Entity under ''Software creation entity'' and repeat configuration manually for each Entity.
All softwares imported from the GLPI agent will fall under the root Entity with the recursive option activated. Software with the same name will share the same entry and simply add to the number of installations in the ''Software'' menu. Each computer of the child Entities will stay connected to the software in the root Entity, thus providing all information on installed software.
P.S. You may need to delete all of yout current software and let the agent reimport them if you do have get this result.
P.S ..! Also, if by any mean your turn on ''Model for automatic entity transfer on inventories'' and set a transfer model, that will transfert all computers to the Entity of the software when software is added. This would result in all your computer being transfered to the root Entity, which I highly doubt is the result you would want. To reverse this setting, the only way that worked for me was to delete the transfert model in the transfer rule. Tread carefully ..!
source from the official documentation (administration/entities.html):
Assets
This tab allows to configure the different dates present in administrative and financial information and some other entity-level asset options. The possible automatic actions are:
filling when item gets a particular status;
filling by copying another date;
no automatic filling
The option Software creation entity allows to redirect software creation to another entity at a higher level in the hierarchy. This functionality applies on all software of the entity; if redirection must be defined only for some software, the software dictionary must be used.
../../_images/configtransfer.png
Model for automatic entity transfer on inventories GLPI also allows to transfer a computer in another entity if one of the criteria used for the assignment to an entity is modified. If the option Model for the automatic transfer of computers in another entity indicates an existing model, then each time a computer is updated from the inventory tool, the entity assignment rules engine will be replayed. If the resulting entity is different from the current entity, the computer will be transferred to the new entity.
Note
This configuration option is not present if you have only one entity in your instance.
Offline