Error Details
| Fact | Value | Source | Note |
|---|
| Exact error code | 0x87D01107 | CcmSetup.log | Client push installation failure |
| Affected OS build | Windows 11 23H2 (22000.2180+) | System Info | Build version mismatch possible |
| Registry key | HKLM\SOFTWARE\Microsoft\SMS\Client | Registry Editor | Client detection registry |
| Firewall rule | Windows Management Instrumentation (WMI-In) | Windows Firewall | Must allow RPC/DCOM traffic |
| Service endpoint | SMS_CLIENT | WMI namespace root\ccm | Push installation target service |
Log Files to Check
C:\Windows\CCM\Logs\CcmSetup.logC:\Windows\CCMSetup\Logs\smsts.log
What This Error Actually Means
The error code
0x87D01107 is a hexadecimal representation of a failure during the Microsoft Configuration Manager (SCCM) client push installation process. This error is raised by the **SMS Client Setup (CcmSetup.exe)** component when it cannot verify the presence of a valid Configuration Manager client on the target device. The error specifically indicates a breakdown in communication between the source SCCM server and the target device, typically due to **Windows Firewall blocking WMI (Windows Management Instrumentation)** or **WMI service misconfiguration**. The error is logged in
CcmSetup.log and often correlates with missing or disabled firewall rules for WMI, or a failure to establish a connection to the
root\ccm WMI namespace. The hexadecimal breakdown of the error code aligns with SCCM’s internal error schema, where
0x87D0 prefixes client installation issues, and
0x1107 specifically maps to WMI connectivity failures during client detection.
Affected Versions and Scope
This error is observed on **Windows 11 23H2 (OS build 22000.2180 and later)** devices enrolled in SCCM. It is not limited to a specific SCCM console version but is more prevalent in environments using **SCCM Current Branch 2210 or later** due to stricter WMI and firewall validation during push installation. The issue does **not affect Windows 10 21H2 or earlier** builds, as older OS versions handle WMI firewall rules differently. Additionally, devices managed via **Intune hybrid co-management** or **Azure AD-joined devices without SCCM client push** are unaffected. The scope is further narrowed to scenarios where **firewall rules are manually enforced** (e.g., via GPO or Intune device configuration policies) or where **WMI namespaces are corrupted or missing**.
Where To Look First: Logs and Event IDs
The primary log to analyze is
C:\Windows\CCM\Logs\CcmSetup.log. Search for the exact line:
Failed to detect client: 0x87D01107
This line confirms the error context. Cross-reference with
C:\Windows\CCMSetup\Logs\smsts.log for WMI-related errors, such as:
Error: WMI query for SMS_Client failed with error code 0x8004100E
In the Windows Event Viewer, check **Event ID 10000** (SMS Client Setup) and **Event ID 10001** (SMS Client Installation) under **Applications and Services Logs > Microsoft > Windows > SMS_Client**. These events often provide additional context, such as whether the WMI service (
winmgmt) is running or if the
root\ccm namespace is accessible.
Root Causes
1. Windows Firewall Blocking WMI-In
The
Windows Management Instrumentation (WMI-In) firewall rule is disabled or blocked by a GPO/Intune policy. This prevents the SCCM server from querying the
SMS_CLIENT endpoint. To confirm, run:
Get-NetFirewallRule -Name "WMI-In"
If the rule is disabled or not present, this is the root cause.
2. Corrupted WMI Namespace
The
root\ccm WMI namespace is missing or corrupted. Verify using:
Get-WmiObject -Namespace root\ccm -Class SMS_Client
A failure here indicates a WMI issue. Check the registry key
HKLM\SOFTWARE\Microsoft\SMS\Client for existence; its absence suggests a failed client installation.
3. Antivirus/EDR Interference
Third-party security software may block WMI or SCCM client processes. Temporarily disable the software and retry the push installation to isolate the issue.
Fix Procedure
- Enable the WMI-In firewall rule:
Set-NetFirewallRule -Name "WMI-In" -Enabled True
Warning: Enabling this rule globally may expose devices to WMI-based attacks. Apply only to SCCM target groups.
- Repair the WMI namespace:
winmgmt /salvage //?root=ccm {B7E6D5B0-8D6D-11D0-BD0B-00A0C911CE86} C:\Windows\System32\wbem
Reboot the device afterward.
- Verify the registry key
HKLM\SOFTWARE\Microsoft\SMS\Client exists. If missing, manually create it using:
New-Item -Path HKLM:\SOFTWARE\Microsoft\SMS\Client -Force
- Use Intune to enforce WMI connectivity:
Navigate to **Intune admin center > Devices > Device configuration > Create profile**. Select **OMA-URI** with the value:
./Device/Vendor/MSFT/WindowsFirewall/DomainProfile/Exception/WindowsManagementInstrumentation
Set the **Value** to Enable.
- Force SCCM client installation:
Start-Process -FilePath "C:\Windows\CCMSetup\ccmsetup.exe" -ArgumentList "/mp:"
Replace with your SCCM Management Point.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
0x87D01107 | WMI connectivity failure during client detection | Occurs only during push installation; logs reference SMS_CLIENT |
0x87D01108 | Failed to create SMS_Client instance | Indicates WMI namespace corruption; logs reference WBEM_E_FAILED |
0x87D0000A | General client installation failure | No WMI-specific logs; often due to missing prerequisites (e.g., .NET) |
Verification
After applying fixes, check
CcmSetup.log for the line:
Client detected successfully
In the SCCM console, navigate to **Assets and Compliance > Devices** and confirm the device appears online. Use:
Get-WmiObject -Namespace root\ccm -Class SMS_Client | Select-Object ClientVersion
A valid version number (e.g.,
5.00.12345.6789) confirms resolution.
Prevention
To prevent recurrence, deploy an **Intune device configuration profile** enforcing the
WMI-In firewall rule. Navigate to **Intune admin center > Devices > Device configuration > Profiles > Create profile**. Use the **Windows 10 and later > Custom** template with the OMA-URI:
./Device/Vendor/MSFT/WindowsFirewall/DomainProfile/Exception/WindowsManagementInstrumentation
Additionally, create a **Configuration Manager baseline** to monitor the registry key
HKLM\SOFTWARE\Microsoft\SMS\Client and trigger remediation if missing. Run:
Get-CMBaseline -Name "SCCM Client Health" | Start-CMBaselineEvaluation
Tip: Use dsregcmd /status to quickly verify enrollment status and WMI connectivity in hybrid scenarios.