Enrichment rule for software, that is no longer installed

[AMensching]

Hello,

I'm trying to create an enrichment rule for the deletion of "Installed Software" Cis, but I wasn't not successful.
The enrichment rule should delete any "Installed Software" CI on a computer, that does not have the same "LastDiscoveredTime" as the computer.
I need the enrichment rule for the "Inventory Discovery by Manual Scanner" job, because the Auto-Delete function doesn't work correctly for that job.

Has anyone created a similar enrichment rule and what should I pay attention to?
Any help is welcome .... 🙂

Regards

Achim

[Alan Rojas Vargas]

Hello

Regarding the ER it is out of my scope apologies, but for the aging mechanism let me suggest you to open a ticket with support to check if there is a fix, 

Best Regards

[AMensching]

I have already opened a support ticket, but the support can not help me (at least that's what the support told me)

[JohnCI]

The main problem is why the Inventory adapter doesn't delete the installedSW which is no longer reported.

I would suspect that the probe cache isn't properly performing or we don't send the old cmdbIDs to the probe.

Would be interesting if it will work on a freshly deployed probe with only a few IP defined on it. Install some SW on the node, do discovery, uninstall that SW and redo discovery. If it works as designed then we have a maintenance issue on the old probes. If not then we will have to debug the auto-deletion mechanism.

As a short term solution, a cleanup script can be adapted from the adapter Remove Expired ExecutionEnvironment links.

[AMensching]

Hello Bogdan,

thanks for your post.

The "Inventory Discovery by Manual Scanner" job doesn't support the removal by design.That's the result from Micro Focus support and from several other customers too. There are some articles in the knowledge base as well.

I created an Idea Exchange (https://community.microfocus.com/t5/CMS-Idea-Exchange/Enhance-Inventory-Discovery-by-Manual-Scanner-delete/idi-p/2703478) to support the removal of affected CIs (e.g. Installed Software).

Unitl there is no OOTB solution, I need an enrichment rule, but I'm not able to create it. I made a few tries.

The support does not want to help me, because they say that would be a job of Professional Services. This is a pity.

Regards
Achim

[JohnCI]

If autodeletion is not supported then why do we have the options to delete certain CITs?

What documents for this know issue did you receive?

[JohnCI]

Also, in the adapter source code we have the result mechanism declared

<resultMechanism isEnabled="true">
<autoDeleteCITs isEnabled="true">
<candidateForDeletionCIT>cpu</candidateForDeletionCIT>
<CIT>dir</CIT>
<CIT>display_monitor</CIT>
<CIT>file_system</CIT>
<CIT>installed_software</CIT>
<CIT>osuser</CIT>
<candidateForDeletionCIT>running_software</candidateForDeletionCIT>
<candidateForDeletionCIT>usage</candidateForDeletionCIT>
<CIT>windows_service</CIT>
</autoDeleteCITs>
<automaticTouch isEnabled="true" />
</resultMechanism>

[AMensching · Accepted solution]

Hello Bogdan,

I think you refer to a different discovery job. I'm writing about the "Inventory Discovery by Manual Scanner" and you about the "Inventory Discovery by Scanner".
Thats a difference.
Here are some links about the issue:
https://softwaresupport.softwaregrp.com/doc/KM01744875
https://softwaresupport.softwaregrp.com/doc/KM03476130
https://softwaresupport.softwaregrp.com/doc/KM03485464
https://community.microfocus.com/t5/CMS-Discovery-CMDB-User/Inventory-Discovery-by-Manual-Scanner-deletes-CI-s/m-p/2688572#M19996
Regards
Achim

[JohnCI]

You are right. Manual scanner doesn't have the autodeletion mechanism.
Maybe a pseudo-discovery job like Remove old ExecutionEnvironment Links can handle such discrepancies but it has to be written from scratch.