Enhancement Request: Allow Inventory policy events to be kept longer and not purged based on Cleanup Task Data settings
Currently, Inventory policy run events are included in the Cleanup Task Data setting, \Settings\Notification Server\Task Settings\Cleanup Task Data purge configuration. Since this is considered a task event, they will eventually be purged based on the setting ‘Maximum number of working database rows’ and ‘Maximum number of working database summary rows’. When Inventory events are purged, this can skew the Inventory policy UI that shows the number of resources in the ‘Applies To/Compliance’ header as well as the Status column succeeded/failed percentages.
When inventory events are purged, this affects the ‘Applies To/Compliance’ resource count since that value is based on the number of computers with an inventory event for that policy in the ‘Evt_Task_Instances’ table. If there is not an inventory event, the resource is not included in the total number of computers and percentages. Second, the Status column that shows percentages for Succeeded and Failed is also affected. When viewing the policy, the Status line can also include an empty section which indicates the number of resources in the Resources column that do not have an entry in the ‘Evt_Task_Instances’ table. For example, when changing the View dropdown from ‘Applied by’ to ‘Computers and users’, there can be computers listed that show 0 for Task Run and an empty state. This could be that it never ran the task or indeed ran the task but the event was purged.
This is currently being reviewed by Symantec Inc.
Imported Document ID: TECH227407
Subscribing will provide email updates when this Article is updated. Login is required.