Missing primary user values for clients
Problem: Primary User values are empty in vScope for SCCM/MECM clients.
Goal: Confirm the data exists and that the SCCM probe can read it.
Step-by-step checks
Section titled “Step-by-step checks”-
Check the table with the vScope credential
SELECT TOP 5 * FROM [CM_<site>].[dbo].[v_UsersPrimaryMachines];Expected: rows with Primary User data. If empty or permission denied, continue.
-
Check with a higher-privilege account
Run the same query with an elevated SQL login.- If data appears only with the elevated account, the vScope credential lacks rights → grant
db_datareaderon the site DB (see Grant db_datareader for SCCM site database). - If still empty, go to step 3.
- If data appears only with the elevated account, the vScope credential lacks rights → grant
-
Verify SCCM configuration (User-Device Affinity)
Ensure user-device affinity is enabled and populated in SCCM sov_UsersPrimaryMachinescontains data. Microsoft guide: https://learn.microsoft.com/mem/configmgr/apps/deploy-use/link-users-and-devices-with-user-device-affinity -
Target the right site DB
Point the connector to a Primary Site DB (CM_<site>), not just the CAS, since primary sites often hold more complete client data. -
Rerun SCCM discovery in vScope
After adjustments, rerun the SCCM discovery and re-check Tables/Properties for Primary User values.
Related
Section titled “Related”- SCCM SQL connector setup: /datasources/system-center-configuration-manager/
- SCCM permission helper: Grant db_datareader for SCCM site database