sodcalculator

10 Tech How-To

How to Check SCCM Client Push Status in Reports, SQL, and Logs

Guide 10-43492 · Updated · Step by step

This guide explains how to verify whether Configuration Manager (ConfigMgr/SCCM) successfully pushed and installed the client on target machines. You’ll learn to check the built-in reports, query the SQL database directly, and read the relevant log files when you need deeper detail. The methods below work for current mainstream versions of Configuration Manager (2012 and later, including Current Branch).

What You’ll Need

  • Access to the Configuration Manager console with at least the Read Analyst or similar read-only role for reports.
  • SQL Server permissions (e.g., sysadmin or db_datareader on the ConfigMgr database) if you plan to run SQL queries.
  • Local administrator rights on the site server or the client machines to read log files.
  • Basic familiarity with the ConfigMgr console and SQL Server Management Studio (SSMS).

Step-by-Step

Method 1: Using Built-In Reports

  1. Open the Configuration Manager console.
  2. Go to Monitoring > Reporting > Reports.
  3. In the search box, type Client Push or Client Deployment to filter the list. Look for reports like Client Push Installation Status or Client Deployment Status.
  4. Select the report and click Run in the ribbon.
  5. Enter the parameters if asked (e.g., collection name, date range, or site code).
  6. Review the output. The report typically shows each device with a status such as Success, Failed, In Progress, or Unknown. Click a device to see more details, including the last error code.

Method 2: Querying the SQL Database

  1. Open SQL Server Management Studio and connect to the site database (usually named CM_<SiteCode>).
  2. Run the following query to get the client push status for all discovered systems:
SELECT
    v_R_System.Netbios_Name0 AS ComputerName,
    v_GS_OPERATING_SYSTEM.Caption0 AS OS,
    v_ClientPushStatus.StateName,
    v_ClientPushStatus.LastErrorCode,
    v_ClientPushStatus.LastErrorTime,
    v_ClientPushStatus.LastStatusTime
FROM v_R_System
LEFT JOIN v_GS_OPERATING_SYSTEM ON v_R_System.ResourceID = v_GS_OPERATING_SYSTEM.ResourceID
LEFT JOIN v_ClientPushStatus ON v_R_System.ResourceID = v_ClientPushStatus.ResourceID
WHERE v_R_System.Client0 = 0 -- only non-client machines
ORDER BY v_R_System.Netbios_Name0;

This query shows machines that have not installed the client, along with the push status. To see all machines, remove the WHERE clause.

For more detail on the push attempt, run:

SELECT * FROM v_ClientPushStatus WHERE ResourceID = '<ResourceID>';

Replace <ResourceID> with the actual ID from the first query.

Method 3: Checking Log Files

  1. On the site server, navigate to %ProgramFiles%\Microsoft Configuration Manager\Logs.
  2. Open ccm.log (the client push installation log) with CMTrace or Notepad. This log records each push attempt, the target computer, and the result.
  3. Look for lines that include Successfully installed or Failed to install. Note the error code if present.
  4. On the client computer (if the client was partially installed), check C:\Windows\CCM\Logs for ccmsetup.log. This log shows the installation process on the client side and is crucial for diagnosing failures.

Common Mistakes

  • Using the wrong database name – Verify the site code; the database is usually CM_<SiteCode>.
  • Filtering too narrowly – The WHERE Client0 = 0 clause excludes machines that already have the client, which may hide successful pushes. Use it only when you want to see pending/failed pushes.
  • Ignoring the client version – A machine might show as “Client installed” but be an older version. Check the client version in the console to ensure it matches the expected version.
  • Reading logs without CMTrace – Logs are easier to read with CMTrace (Configuration Manager Trace Log Tool) because it highlights errors and can decode them. Notepad is fine but less efficient.

Tips

  • Use the Client Push Installation Wizard in the console to manually push to a single machine for testing, then immediately check the logs.
  • Set up the Client Status reporting in the console to get a dashboard view of client health, including push status.
  • For large environments, use SQL queries to export the list of failed machines to a CSV for further action.
  • Enable verbose logging for ccm.log by setting the site server’s logging level to Verbose in the Configuration Manager Service Manager.

Troubleshooting

If the push fails, the first step is to identify the error code. Look up the error code in the logs or in the report. Common errors include:

  • 0x80070005 (Access Denied) – The site server account doesn’t have admin rights on the target. Check the client push installation account permissions.
  • 0x800706BA (RPC Server Unavailable) – The target machine is unreachable or firewall blocks RPC. Test with ping and check Windows Firewall rules for File and Printer Sharing.
  • 0x8004100E (Invalid Namespace) – WMI issue on the target. Re-run wmimgmt.msc on the target to verify WMI is healthy.

If the error is not obvious, check the ccm.log on the site server for the exact step that failed, and the ccmsetup.log on the client for installation errors. Also verify that the client push installation account is correctly configured in Administration > Site Configuration > Sites > Client Installation Settings.

For persistent failures, consider using a different installation method (e.g., Group Policy or manual installation) as a workaround, and investigate the root cause separately.

Frequently Asked Questions

Why does the report show “Unknown” for some machines?

“Unknown” means the site has not received any status from the client push attempt. This can happen if the machine is offline, unreachable, or if the push was never initiated (e.g., the machine was not in the target collection at the time).

How do I find the site code for the SQL database name?

In the console, go to Administration > Site Configuration > Sites. The site code is shown in the Site Code column. The database name is CM_<SiteCode>.

Can I check client push status from the client itself?

Yes, but only after the client is installed. Look at C:\Windows\CCM\Logs\ccmsetup.log for the installation result. For push status before installation, you must check the site server logs or SQL.

What is the difference between v_ClientPushStatus and v_CH_ClientSummary?

v_ClientPushStatus contains the push attempt status for each resource. v_CH_ClientSummary is a summary view used in the console dashboard; it aggregates counts and may not have per-device details.

How often is the client push status updated in SQL?

Status updates are near real-time as the push process writes to the database. However, reports may cache data for a few minutes. If you need the latest, run the SQL query directly.

Why did the push succeed but the client is not active?

A successful push means the client software was installed. However, the client might be disabled, not assigned to a site, or have a communication issue. Check the client’s Configuration Manager control panel applet to see if it is active and assigned.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →