Troubleshooting Outdated or Missing Data in SCCM Hardware Inventory Reports

Explore Our MECM / SCCM Training →

Introduction

In this blog post, we’ll guide you through troubleshooting common issues with SCCM Hardware Inventory reporting outdated or missing data. By the end of this article, you’ll have the knowledge to analyze logs, customize MOF files, and tune inventory cycles for more accurate asset management.

Step 1: Trigger Hardware Inventory Cycle

Start by triggering a hardware inventory cycle from the Configuration Manager applet and check the InventoryAgent.log for collection completion.

Step 2: Review dataldr.log on the Site Server

On the site server, review the dataldr.log for any processing errors that may affect your hardware inventory data.

Step 3: Customize Hardware Inventory Classes

To collect detailed CPU and memory information accurately, customize Hardware Inventory Classes to include Win32_Processor (NumberOfCores, MaxClockSpeed) and Win32_PhysicalMemory (Capacity).

Step 4: Handle PowerShell Get-MgBetaDeviceManagementManagedDevices Issues

If you encounter zero or NULL values when using PowerShell’s Get-MgBetaDeviceManagementManagedDevices, consider using the Microsoft Graph beta endpoint with explicit property selection instead of relying on default returns.

Common WMI Class Issues

Here are some common WMI class issues affecting SCCM inventory:

– Incomplete or inaccurate Win32_ComputerSystem and Win32_OperatingSystem data
– Missing or inconsistent drive letters for fixed disks
– Outdated BIOS information

Conclusion

With these troubleshooting techniques, you can ensure your SCCM Hardware Inventory reports are accurate and up-to-date. For more in-depth training on SCCM, check out our Microsoft SCCM Training courses at ITP Training.

Explore Our MECM / SCCM Training →