System Center Configuration Manager (SCCM)
Objective: Connect SCCM/MECM via SQL so vScope can read assets from the CM_<site> database.
Prerequisites
Section titled “Prerequisites”- Access to SCCM server
- vScope has network access to SCCM SQL; default port 1433 (named instances may use dynamic ports).
- Credential with at least
db_datareader. See: Grant db_datareader for SCCM site database - SCCM inventory is running on clients (for fresh data).
Steps to connect
Section titled “Steps to connect”-
Create SQL login in the SCCM Database
- Server Roles:
public - User Mapping: check the site DB (e.g.,
CM_ABC) → Database role:db_datareader - Ensure login is enabled/active.
- For more details: Grant db_datareader for SCCM site database.
- Server Roles:
-
Note connection details
- Server, SQL login credentials and port (if other than default).
-
Add data source in vScope
- Go to Discovery > Credential > + Credential > SCCM.
- Enter username, password, the IP/hostname of the SCCM server and port (default port: 1433).
- Select any customizations, e.g., what assets, SQL authentication etc.
- Test connection and save.
-
Run discovery
- Start SCCM discovery in vScope.
-
Verification
- Open Tables,
All Machinesand filter by “Found By = SCCM” confirm rows appear.
- Open Tables,
Hardware inventory (optional)
Section titled “Hardware inventory (optional)”For richer data (serials, patch info, hardware), ensure that the following classes are enabled in SCCM Hardware Inventory:
- Computer System Product(
Win32_ComputerSystemProduct) - Operating System (
Win32_OperatingSystem) - Process (
Win32_Process) - Patching (
Win32_QuickFixEngineering) - DiskDrives(
Win32_DiskDrives) - DiskPartition(
Win32_DiskPartition)
After changing inventory settings in SCCM, run a Hardware Inventory cycle on clients, then rerun SCCM discovery in vScope.
Troubleshooting
Section titled “Troubleshooting”“System Not Supported” (Sites table not found)
- Verify the login has
db_datareaderon the site DB and can read[dbo].[Sites]. - Ensure you are pointing to the correct DB (
CM_<site>) and port/instance. - Quick check:
SELECT name FROM sys.databases WHERE CASE WHEN state_desc = 'ONLINE' THEN OBJECT_ID(QUOTENAME(name) + '.[dbo].[Sites]', 'U') END IS NOT NULL;
See: Grant db_datareader for SCCM site database
Connection fails
- Wrong port/instance or firewall blocks 1433/dynamic port.
- Test with
sqlcmd -S server[,port] -d CM_<site> -U <user> -P <pass>.
Data seems stale/outdated
- Confirm SCCM hardware inventory cycles are running on clients.
- Rerun discovery in vScope after inventory completes. See Hardware Inventory
Missing tags
- Fetch any tags from the available view using Tags from Discovery.
- Ensure to rerun discovery in vScope tags have been added.
Missing Primary User for Clients See: Missing Primary User values for clients in vScope
Related Articles
Section titled “Related Articles”- How to create
db_datareader: Grant db_datareader for SCCM site database.