In FNMS you will see duplicate records for the device. Where the duplicate device have missing Hardware information, this is due to an issue with the WMI classes in the device. The agent couldn't run its query to get the WMI classes.
2020-12-29 04:07:08.190Z, pid 3524, thread 3964 (Inventory/Tracker/Hardware): WMI config file: C:\Program Files (x86)\ManageSoft\Tracker\wmitrack.ini
2020-12-29 04:07:08.190Z, pid 3524, thread 3964 (Inventory/Hardware/WMI/Query): Begin WMI class enumeration for 'Win32_ComputerSystem'
2020-12-29 04:07:08.190Z, pid 3524, thread 3964 (Error/Catalog/Fetch): Message s4m4112 from process catalog: Invalid class
2020-12-29 04:07:08.190Z, pid 3524, thread 3964 (Inventory/Hardware/WMI/Query): Failed to begin enumeration of the WMI class 'Win32_ComputerSystem': Invalid class (0x80041010)
2020-12-29 04:07:08.205Z, pid 3524, thread 3964 (Error/Catalog/Fetch): Message s4m4112 from process catalog: Invalid class
2020-12-29 04:07:08.205Z, pid 3524, thread 3964 (0,Error/Occurrence/Warning/371/2): Warning Occurrence (s371m2): Failed to enumerate the WMI class 'Win32_ComputerSystem': Invalid class (0x80041010)
2020-12-29 04:07:08.205Z, pid 3524, thread 3964 (Inventory/Tracker/Hardware/WMI/Class): WMI class tracked: Win32_ComputerSystem
This article to help further troubleshoot and fix the WMI class issue.
https://www.virtuallyboring.com/microsoft-wmi-invalid-class-error-0x80041010/
Also, you can also try using the WbemTest tool on the device to verify if they are able to query the WMI classes correctly -
https://docs.microsoft.com/en-us/mem/configmgr/develop/core/understand/introduction-to-wbemtest
Jan 11, 2021 07:16 PM