cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Summary

When the Windows operating system bootup time or install date details change (including from time zone changes) on a managed device, a new partial inventory NDI file is generated and uploaded by the next IBM PVU inventory scan event, despite no meaningful change affecting PVU license consumption in hardware configuration taking place.

Details

When an IBM PVU inventory scan is performed, the agent checks whether various hardware details in the inventory have changed. A partial inventory NDI file is generated and uploaded when a change is detected.

This issue results in a partial inventory NDI file being unnecessarily generated and uploaded when operating system bootup time or install date details change, despite there being no change in the computer's hardware configuration that has an impact on the calculation of PVU license consumption.

When this occurs, logging in the tracker.log file produced by the inventory gathering ndtrack process shows output indicating changes have been detected related to the Win32_OperatingSystem hardware item. For example:

[2/18/2022 5:44:15 AM (G, 0)] {13368} Searching for changes in hardware inventory...
[2/18/2022 5:44:15 AM (G, 0)] {13368} Previous hardware item 'Win32_OperatingSystem;Microsoft Windows 10 Enterprise|C:\windows|\Device\Harddisk0\Partition2;InstallDate;20211025T222132-0400' not found in latest inventory
[2/18/2022 5:44:15 AM (G, 0)] {13368} Previous hardware item 'Win32_OperatingSystem;Microsoft Windows 10 Enterprise|C:\WINDOWS|\Device\Harddisk0\Partition4;LastBootUpTime;20220218T083436-0400' not found in latest inventory
[...]
[2/18/2022 5:44:15 AM (G, 0)] {13368} Started generating inventory 'C:\ProgramData\ManageSoft Corp\ManageSoft\Tracker\Inventories\system on wkstn102.ndi'

This issue does not directly result in inaccurate data being reported, but may place additional unnecessarily load on server infrastructure to process the additional inventory NDI files.

Fix details

This issue has been fixed by adding the following properties to the default value for the HardwareChangesClassPropertyBlacklist preference: Win32_OperatingSystem.LastBootUpTime.InstallDate

Related information

See the following other known issues which have some similarities to this one:

Fix status

This issue has been fixed in the following FlexNet Manager Suite releases: 2021 R1.4 / Mar 2022 (Cloud), 2022 R1 (On Premises)

Other information

Affected components: Agent, Inventory, SAM for IBM

Master issue ID: IOJ-2247786

Also known as: FNML-75214

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Jun 12, 2022 03:51 AM
Updated by:
Knowledge base article header content