Why are Microsoft Endpoint Configuration Manager (SCCM) machines missing in vScope?

To be able to match a machine with itself from various data sources, vScope needs a unique identifier. Machines from Microsoft Endpoint Configuration Manager (MECM) only show up in the All Machines table and get a properties page if vScope can find a BIOS serial number. The MECM agent needs to be installed and active on the machine for this value to be available.

Where is vScope looking for this in the MECM (SCCM) SQL database?

For an All Machines entry in vScope:
SELECT * FROM [" + databaseName + "].[dbo].[v_R_System]
SELECT * FROM [" + databaseName + "].[dbo].[v_GS_PC_BIOS], with a value in SerialNumber0

These two results from the database are matched using the ResourceID that’s available in both tables.

Got more questions or need help?

Don’t hesitate to reach out to our support at https://www.vscope.net/support/.