Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..
226 views

Aging off uninstalled software question....

We uninstalled the HP SA (Server Automation) agents four days ago from all our servers and theinstalled software CIs still show up in the inventory scans from last night.  How long will it be before they age off ?

 

0 Likes
4 Replies
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Aging off uninstalled software question....

It will depend on several factors:

  • Is Aging enabled for the UCMDB server?
  • Is the Inventory Discovery adapter configured to delete or mark for deletion Installed Software CIs?
  • Was the software previously discovered by the probe and was the latest scan processed by the exact same probe so as to be noticed as missing?
  • What is the configured Actual Deletion Period for Installed Software CI type?

For example:

Aging is enabled in UCMDB. The Inventory Discovery by Scanner adapter is configured to Mark for Deletion and Enable Automatic Deletion is enabled and set for on Success. The scan file was processed by the exact same probe server and it was previously discovered by that probe. The Actual Deletion Period for Installed Software is set to 40 days.

 

Then, the Installed Software will be deleted in 20 days after it has been flagged as Is Candidate for Deletion.

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Aging off uninstalled software question....

Aging is on

Automatic Deletion is enabled

Installed Software and Windows Service are both set to Auto Delete

The HP SA Agent and it's WIndows Service are still listed as CIs related to the node 

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Aging off uninstalled software question....


@Ken Strauss_2 wrote:

Aging is on

Automatic Deletion is enabled

Installed Software and Windows Service are both set to Auto Delete

The HP SA Agent and it's WIndows Service are still listed as CIs related to the node 


I would then use the Inventory Tools viewer application to open the latest scan file for the server and verify that the application is no longer recognized. The other factor is whether the probe server actually noticed that it was installed previously and sent it to the UCMDB server as a missing CI. This is harder to troubleshoot.

  1. Review the probe log titled probeMgr-result-processing.log
  2. Look for lines similar to the below but for the server's IP address
    <2016-01-11 08:32:08,761> [INFO ] [JobExecuterWorker-74:Inventory_Discovery_by_Scanner_10.10.10.10] (ObjectsRedundantStatistics.java:85) - Result redundant filter (same bulk) done for trigger CI: 130ea952ce2c8118659c84459e5bc4b0 -  Total Objects number: 114-->114 ( nt:1->1 file_system_export:3->3 membership:15->15 cpu:1->1 hardware_board:1->1 winosuser:1->1 inventory_scanner:1->1 disk_device:2->2 interface:7->7 containment:4->4 dependency:1->1 ip_address:2->2 memory_unit:2->2 logical_volume:1->1 installed_software:71->71 file_system:1->1  )
  3.  Note that in my example above installed_software is 71->71 which indicates that previous cached count and current count are the same. In other words, no changes.
  4. The next line for that IP shows what objects are actually to be sent based on previous execution. Only 15 objects out of 114 and 0 for installed_software.
    <2016-01-11 08:32:08,839> [INFO ] [JobExecuterWorker-74:Inventory_Discovery_by_Scanner_10.10.10.10] (ObjectsRedundantStatistics.java:85) - Result redundant filter (previous executions) done for trigger CI: 130ea952ce2c8118659c84459e5bc4b0 -  Total Objects number: 114-->15 ( nt:1->0 file_system_export:3->0 membership:15->0 cpu:1->0 hardware_board:1->0 winosuser:1->1 inventory_scanner:1->1 disk_device:2->0 interface:7->7 containment:4->3 dependency:1->0 ip_address:2->1 memory_unit:2->0 logical_volume:1->1 installed_software:71->0 file_system:1->1  )
  5. The next line is not clear about which objects were sent for deletion but only shows the quantity of objects to be deleted. The line is referenced by the UCMDB ID rather then by the IP address as done above.
    <2016-01-11 08:32:49,073> [INFO ] [AutomaticDeletionQueueMonitor] (AutomaticDeletionHandler.java:194) - Automatic Deletion: [4] CIs were detected as aged and will be removed from CMDB for job [Inventory_Discovery_by_Scanner] and trigger [130ea952ce2c8118659c84459e5bc4b0] that ran on [1452499576255]
    
    <2016-01-11 08:32:49,073> [INFO ] [AutomaticDeletionQueueMonitor] (AutomaticDeletionHandler.java:204) - Automatic Deletion: Sending a total of 4 Object(s)/Link(s) Deletion for Job Inventory_Discovery_by_Scanner on destination: 130ea952ce2c8118659c84459e5bc4b0

It can sometimes be difficult to troubleshoot why the automatic deletion of objects did not work for a job. Particularity since it is based on the information first being in a previous execution on the probe and then being identified as not in the current scan. Might be easier to just delete the CI objects by hand.

Please let me know if this information was helpful to you.

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Aging off uninstalled software question....

Looks like the real issue is that the original Zone-based Inventory activity referenced an "Inventory Discovery by Scanner" job with a 14 day interval.  Even though the main Activity schedule is daily they seem to be ignoring that and only running every 14 days.    Looks like the only way to change that is to completely rebuild all the Inventory Activities from scratch as I have not been successful in changing the setting in the existing jobs.  

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.