Packages added to a Software Product disappear after a day

book

Article ID: 171126

calendar_today

Updated On:

Products

Software Management Solution

Issue/Introduction

Packages added to a Software Product disappear after a day. The Software Product has no associated software components.

Cause

A fix for an issue where Application Metering files remained on a product even after the associated Software Component was removed caused this behavior.

Resolution

This is working as designed. The software packages and associated data is connected via the software components that are associated with the Software Product. To ensure the correct components are associated, review the parameters under Identify Inventory and correct or add as needed. Next, ensure that the detection check for the software release the package is assigned to runs on endpoints to detect and send inventory. This will ensure the components are properly assigned to the Product.

The following steps is one method of doing this:

  1. Name, Company, and Version of the Software Release must match the criteria in the Product (shown under Identify Inventory in the product).
  2. Open the Software Release in edit mode (right-click, Actions, Edit Software Resource).
  3. Go to the Rules tab.
  4. If there is already a rule, skip to the end.
  5. Choose criteria that will work for the Software in question. For example you can specify a registry key, a registry value, or a static file expression to do so. Good examples can be found in the following steps:
  6. For the Detection Rule example, we’ll use the Registry Key Value option since it is very dynamic in its uses.
  7. Launch the Editor for the Software Resource you wish to add the Rule to.
  8. Under the Rules tab, click the New button (yellow asterisk) next to the Detection Rule dropdown.
  9. Name the rule so it is easily recognizable. For example SQL Server 2008 Detection.
  10. Click the Add a new rule expression button (the blue plus +), move under the Standard Rule section, and click on Registry Key Value.
  11. Provide the Registry path. One way to ensure path reliability is to browse in the registry on a system that has the software installed, using the following steps:
    1. Go to Start > Run > Type regedit > Click OK.
    2. Browse in the Registry hives in the left pane to the Key you will be evaluating for the rule.
    3. Right-click on the key and choose Copy Key Name.
    4. Go back to the Rule setup and Paste in the copied key name. This will give you the proper path.
  12. Provide the Registry entry. This is the name of the value within the Key specified in the previous step.
  13. Provide the Value of the key.
  14. The Match criterion is defaulted to Entire String. To make this rule more dynamic, you can choose Substring to allow partial matches. For example if you want all versions of SQL matching 9.00, you can put 9.00 as the value and any version, such as 9.00.3042.00, will be considered a match.
  15. Click OK to add the criterion.
  16. Click OK to save the Rule. Note that you can have multiple detection points for a rule. This allows more granularity to ensure the target system correctly evaluates if the Software in question is installed or not.
  17. Now add all software releases you need detected to the Targeted Software Inventory policy (the one we used was the Adobe example, you can rename and use that one).

Please also see the Resolution seciton of the following KB, as it applies to this situation as well:

Components showing up in undefined list when a matching Product exists