Interactive Troubleshooter

Published: Sep 7, 2026

Updated: Sep 7, 2026

Interactive: SCCM Client Not Reporting: Heartbeat Fix

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

An interactive root-cause diagnostic tree to resolve SCCM (MECM) client communication failures, missing heartbeat discovery data records, and CCMExec agent stalls.

Full Diagnostic Tree & Step-by-Step Overview

What specific symptom or client status error appears when investigating the non-reporting SCCM device?

The SMS Agent Host (CCMExec) service is stopped, crashing, or stuck stopping on the target client machine.
Client is active in Windows, but Heartbeat Discovery data records (DDR) fail to reach the site server database.
Client certificate validation errors, PKI trust drops, or HTTP/HTTPS communication failures with management point.
Corrupted WMI repository or missing Configuration Manager client root namespaces (`root\ccm`).

What behavior does the SMS Agent Host (CCMExec) service exhibit when inspected in services.msc?

Service fails to start with error 1053 or crashes immediately upon initialization due to missing DLLs.
Service hangs in 'Stopping' state and cannot be terminated via standard service management snap-ins.
Service runs normally, but CCM client logs indicate persistent task execution failures and thread locks.

Repair Corrupted Client Binaries and Restart SMS Agent Host

Solution:

Root Cause: Corrupted SCCM Client Binaries Preventing CCMExec Startup

When SCCM client installation files or critical DLLs within C:\Windows\CCM become corrupted due to unexpected reboots or disk errors, the SMS Agent Host (CCMExec) service fails to initialize, stopping all reporting and heartbeat cycles.

Step-by-Step Fix:

1Stop Dependent Services:

Open PowerShell as Administrator and run:

powershell
     Stop-Service CcmExec -Force -ErrorAction SilentlyContinue

2Run Client Repair via CCMSetup:

Trigger a local client repair using the installation source from your site server:

powershell
     C:\Windows\ccmsetup\ccmsetup.exe /repair

3Verify Service Startup:

Set startup type to Automatic and start the service:

powershell
     Set-Service CcmExec -StartupType Automatic
     Start-Service CcmExec

Force Terminate Hung CCMExec Service Process via Task Manager

Solution:

Root Cause: Hung SMS Agent Host Process Lock on System Threads

Sometimes CCMExec.exe hangs indefinitely in a stopping state because a child thread is waiting for an unresponsive network or WMI query response, blocking all service control manager commands.

Step-by-Step Fix:

1Identify Process ID (PID) of Hung Service:

Open an administrative command prompt and run:

cmd
     sc queryex ccmexec

2Kill Process Forcefully:

Terminate the stuck process using its PID:

cmd
     taskkill /f /pid <PID_NUMBER>

3Restart Service:

Start the service cleanly: net start ccmexec.

Clean CCM Cache and Reset Local Client Task Schedules

Solution:

Root Cause: Corrupted Client Cache or Stale Scheduled Client Actions

Accumulated corrupted cache files or stuck client action schedules can lock the CCMExec agent execution queue, preventing heartbeat discovery and inventory cycles from executing.

Step-by-Step Fix:

1Clear CCM Cache via PowerShell:

Stop the client service and clear cache folders:

powershell
     Stop-Service CcmExec
     Remove-Item -Path "C:\Windows\ccm\cache\*" -Recurse -Force -ErrorAction SilentlyContinue

2Recreate Client Scheduled Tasks:

Re-register SCCM client scheduled tasks by running:

powershell
     C:\Windows\CCM\CCMRepair.exe

3Start Service:

Start the SMS Agent Host service: Start-Service CcmExec.

What specific symptom or log error occurs when checking Heartbeat Discovery Data Records (DDR)?

Heartbeat discovery cycle is missing from Configuration Manager Control Panel applet actions list.
InventoryAgent.log or Discovery.log shows scheduling errors or serialization failures when generating DDR files.
DDR files reach the site server inbox (`inboxes\auth\ddrs.box`), but are rejected to the bad files folder.

Manually Trigger Heartbeat Discovery Cycle via PowerShell and Control Panel

Solution:

Root Cause: Disabled Heartbeat Discovery Schedule or Stale Agent Actions

If the Heartbeat Discovery schedule has been modified in the SCCM console or local client policy registration is broken, the client fails to automatically generate and send Discovery Data Records (DDR) to the Management Point.

Step-by-Step Fix:

1Trigger via Configuration Manager Control Panel Applet:

Open control panel on the client workstation, open Configuration Manager, go to the Actions tab.

Select Discovery Data Collection Cycle and click Run Now.

2Trigger via PowerShell:

Force the action programmatically using PowerShell GUID triggers:

powershell
     Invoke-WmiMethod -Namespace root\ccm -Class SMS_Client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000003}"

3Verify Log Output:

Check C:\Windows\CCM\Logs\InventoryAgent.log to confirm DDR generation and transmission.

Fix Inventory Agent and Schedule Lockouts in CCM Client Registry

Solution:

Root Cause: Registry Corruption in Client Schedule Identifiers

Corrupted registry keys under HKLM\SOFTWARE\Microsoft\CCM\CcmExec or missing schedule GUIDs prevent client agents from registering polling schedules for heartbeats and hardware inventory.

Step-by-Step Fix:

1Inspect Client Schedule Registry:

Open regedit and navigate to HKLM\SOFTWARE\Microsoft\CCM\Schedule.

2Reset Schedule Keys:

Recreate or reset missing schedule keys or reinstall the client agent to rebuild registry hives.

3Run Policy Retrieval Cycle:

Force policy download: Invoke-WmiMethod -Namespace root\ccm -Class SMS_Client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000021}".

Troubleshoot Site Server Inbox Bad Files for Rejected DDRs

Solution:

Root Cause: Site Server Inbox Rejection Due to Client ID Duplication or Database Lock

When Discovery Data Records (DDR) reach the site server inbox (C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddrs.box), they can be rejected to the Bad folder if a client GUID collision occurs or SQL Server experiences locking during processing.

Step-by-Step Fix:

1Inspect Site Server Inbox Logs:

Open ddm.log on the primary site server to view reasons for DDR rejection.

2Resolve Client GUID Collisions:

If multiple clients share identical GUIDs (often caused by improper master VM imaging without sysprep), use the New-CMSite or client GUID reset scripts to regenerate unique client IDs.

3Check SQL Server Health:

Ensure site server database maintenance and indexes are healthy.

What certificate or network communication error appears in `ClientLocation.log` or `LocationServices.log`?

Certificate validation failure, expired PKI client cert, or inability to establish HTTPS connection with MP.
Client cannot resolve Management Point FQDN via DNS or communications blocked by Windows Firewall.
Boundary group misconfiguration places client on an unassigned subnet lacking an assigned management point.

Renew or Fix SCCM Client PKI Certificates and Self-Signed Store

Solution:

Root Cause: Expired or Invalid Client PKI Certificate / Self-Signed Store Mismatch

When SCCM clients rely on HTTPS communication, an expired, revoked, or untrusted client authentication certificate prevents the client from authenticating against the Management Point, halting all reporting and heartbeat transmissions.

Step-by-Step Fix:

1Inspect Client Certificates:

Open certlm.msc on the local client machine, navigate to Personal > Certificates, and check SCCM client certificate validity.

2Re-issue or Select Certificate:

Configure client certificate selection criteria in the Configuration Manager control panel applet under the Communication or Security tab.

3Force Certificate Renewal:

Restart CcmExec service to prompt automatic client certificate re-registration with the site server Management Point.

Verify Management Point DNS Resolution and Firewall Port Rules

Solution:

Root Cause: DNS Resolution Failure or Blocked TCP Ports 80/443 to Management Point

If the client cannot resolve the Management Point's FQDN via DNS or if corporate firewalls block TCP port 80 (HTTP) or port 443 (HTTPS), communication fails, leaving the client stranded without an active reporting endpoint.

Step-by-Step Fix:

1Test Network Connectivity to Management Point:

Open PowerShell and test port reachability:

powershell
     Test-NetConnection -ComputerName your-mp.domain.com -Port 443

2Verify DNS Resolution:

Run nslookup your-mp.domain.com to confirm correct IP resolution.

3Check Windows Firewall:

Ensure outbound HTTP/HTTPS traffic is allowed through Windows Firewall or local security software.

Correct Boundary Group Subnet Mappings on Site Server

Solution:

Root Cause: Client IP Subnet Missing from SCCM Boundary Groups

If a client's IP address or Active Directory site is not included in any configured SCCM Boundary Group, the client cannot locate a valid Site System or Management Point, resulting in unmanaged status and no reporting.

Step-by-Step Fix:

1Identify Client IP Subnet:

Run ipconfig on the client to determine its IP address and subnet mask.

2Update Boundary Groups in SCCM Console:

Open the Configuration Manager Console > Administration > Hierarchy Configuration > Boundary Groups.

Add the client's IP subnet or AD site to the appropriate boundary group linked to your primary site.

3Force Client Location Update:

Run policy refresh on the client to re-evaluate boundaries.

What WMI repository or namespace error is identified during client diagnostics?

WMI repository corruption (`root\ccm` namespace missing or inaccessible via wbemtest).
WMI service (`winmgmt`) hangs or crashes when querying Configuration Manager classes.
Complete operating system WMI inconsistency requiring full repository repair and client reinstallation.

Rebuild CCM WMI Namespace and Repair Client Components

Solution:

Root Cause: Corrupted `root\ccm` WMI Namespace Repository

The Configuration Manager client stores its operational configuration, policies, and inventory schedules inside the local root\ccm WMI namespace. If this namespace becomes corrupted, the client agent cannot read or write states, causing reporting failures.

Step-by-Step Fix:

1Stop Client Service:

Run Stop-Service CcmExec -Force in PowerShell.

2Recreate WMI Namespace:

Re-register CCM WMI provider MOF files:

powershell
     cd C:\Windows\CCM
     mofcomp.exe CCMExec.mof

3Restart Service and Re-evaluate:

Start the SMS Agent Host service: Start-Service CcmExec.

Repair Windows Management Instrumentation (WMI) Service

Solution:

Root Cause: Windows Management Instrumentation Service Unresponsive

If the underlying Windows Management Instrumentation (winmgmt) service is hung or experiences repository inconsistencies, all SCCM client agent queries fail, preventing inventory and heartbeat collection.

Step-by-Step Fix:

1Verify WMI Repository Consistency:

Open an administrative command prompt and run:

cmd
     winmgmt /verifyrepository

2Salvage Repository if Inconsistent:

If corruption is detected, run the salvage command:

cmd
     winmgmt /salvagerepository

3Restart Services:

Restart winmgmt and CcmExec services.

Perform Complete SCCM Client Clean Uninstallation and Reinstallation

Solution:

Root Cause: Irreparable Client Agent Corruption Requiring Clean Reinstallation

When multiple core subsystems (WMI classes, client certificates, and service binaries) are simultaneously corrupted, attempting piecemeal repairs is inefficient. A clean uninstallation followed by a fresh installation resolves deep-seated reporting blocks.

Step-by-Step Fix:

1Uninstall Existing Client:

Run the native client uninstallation utility from the client machine:

cmd
     C:\Windows\ccmsetup\ccmsetup.exe /uninstall

2Purge Leftover Files and Registry Keys:

Delete C:\Windows\CCM and clean up residual registry keys under HKLM\SOFTWARE\Microsoft\CCM.

3Reinstall Fresh Client:

Push a fresh client installation from your SCCM Site Server or manually install using the Microsoft Official Support Guide parameters:

cmd
     ccmsetup.exe SMSSITECODE=ABC

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Clipboard History Not Working Windows 11: Sync Service Tree

Subscribe to StepDiag

Embed Guide on Your Website