Home › Microsoft Configuration Manager › 0x87D00668

Microsoft Configuration Manager · 0x87D00668 · SCCM / Configuration Manager

SCCM Client Error 0x87D00668: MP Communication Failure

MP communication failure due to IIS issues or network/firewall blocks; fix by verifying SMS_MP web app health and testing connectivity.

Error Details

FactValueSourceNote
Exact error stringMP_E_MISSING_MP_CONNECTIVITY_AT_WMICcmMessaging.log-> PolicyAgent.log
Affected build rangeSCCM / Configuration ManagerConfiguration Manager console
Registry key involvedHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\Client\SiteCodeRegistry Editor-> OMA-URI
Relevant service/endpoint URLhttp://mp.example.com/sms_mp/.sms_aut?mplistIIS Manager
Log line signature0x87D00668 or 'Mp communication error'CcmMessaging.log-> PolicyAgent.log

Log Files to Check

What This Error Actually Means

The error code MP_E_MISSING_MP_CONNECTIVITY_AT_WMI (0x87D00668) is raised by the Microsoft Configuration Manager client when it cannot establish a connection to its assigned Management Point (MP). The component responsible for this communication is the CCM Messaging service, which handles all interactions between clients and servers in the SCCM hierarchy. This error specifically indicates that the client failed to communicate with the MP using WMI (Windows Management Instrumentation), which is crucial for retrieving policies, delivering status messages, and other essential functions.

Affected Versions and Scope

This issue affects all builds of Microsoft Configuration Manager, including both on-premises deployments and cloud-based implementations. The error does not occur in environments where the SCCM client has been replaced by alternative management tools such as Intune or Endpoint Manager for Windows Autopilot devices. However, it is particularly relevant to organizations that rely heavily on SCCM for device management across their network.

Where To Look First: Logs and Event IDs

To diagnose this issue, you should first examine the following log files: In these logs, search for the exact error string MP_E_MISSING_MP_CONNECTIVITY_AT_WMI or 'Mp communication error'. Additionally, you can look for Event IDs 107 and 208 in the Windows event log to get more details about connectivity issues between clients and management points.

Root Causes

This section will detail several distinct causes of this issue:

IIS Health Endpoint Not Responding

When the IIS health endpoint on the Management Point server is not responding, it indicates that either IIS itself has stopped or there are issues with the SMS_MP web application. To identify if this is the cause, you can use PowerShell to test connectivity from a client machine:
Invoke-WebRequest http://mp.example.com/sms_mp/.sms_aut?mplist -UseBasicParsing
If the endpoint does not respond, it's likely that IIS or the SMS_MP application needs attention.

Network Path or Firewall Blocking Communication

Another common cause is network configuration issues such as firewalls blocking TCP ports 80/443/10123 between clients and MPs. Ensure that these ports are open on both sides of the connection, and check for any rules in your firewall that might be preventing communication.

MP Certificate Expired

If the Management Point is configured to use HTTPS (which requires a valid SSL certificate), an expired or invalid certificate can prevent clients from establishing secure connections. Verify the status of the MP's SSL certificate through IIS Manager and ensure it remains current.

Determining Between Causes

To distinguish between these causes, start by checking if the endpoint is reachable using the PowerShell command mentioned above. If connectivity issues persist despite a valid certificate and open ports, investigate further into IIS configuration or application health.

Fix Procedure

Follow these steps to resolve the issue:
  1. Verify IIS Status: On the Management Point server, use iisreset /status to check if IIS is running. If it's not, restart IIS using iisreset.
  2. Test Connectivity from Client:
    Invoke-WebRequest http://mp.example.com/sms_mp/.sms_aut?mplist -UseBasicParsing
    This will help confirm whether the issue lies with network connectivity.
  3. Trigger Policy Retrieval on Client:
    wmic /namespace:\\root\ccm path SMS_Client CALL TriggerSchedule '{00000000-0000-0000-0000-000000000021}'
    This forces the client to attempt policy retrieval, which can help diagnose whether the issue is with the MP or the client configuration.
  4. Reinstall Client if Site Code Mismatch: If the client's assigned site code does not match that of its Management Point, you may need to reinstall the SCCM client. Use ccmsetup.exe /mp:mp.example.com SMSSITECODE=ABC, replacing mp.example.com with your MP's address and ABC with the correct site code.
Be cautious when reinstalling clients, as this can disrupt ongoing operations or cause data loss if not done correctly.

Error Code Variants

Error CodeDescription
0x87D00669MP_E_MISSING_MP_CONNECTIVITY_AT_HTTP - indicates HTTP connectivity issues between client and MP.
0x87D0066AMP_E_MISSING_MP_CONNECTIVITY_AT_WMI_HTTP - a combination of WMI and HTTP failures.
0x87D0066BMP_E_MISSING_MP_CONNECTIVITY_AT_WMI_HTTPS - similar to 0x87D0066A but specifically for HTTPS connections.

Verification

To verify that the issue has been resolved, look for successful policy retrieval attempts in C:\Windows\CCM\Logs\CcmMessaging.log. Additionally, use PowerShell to check if the client is communicating properly:
Get-WinEvent -LogName 'Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin' | Where-Object {$_.Id -eq 107}
This command will help you identify any new events indicating successful communication between clients and MPs.

Prevention

To prevent recurrence of this issue, ensure that regular maintenance tasks are performed on Management Points. This includes monitoring IIS status, renewing SSL certificates before they expire, and maintaining accurate network configurations to allow necessary traffic through firewalls. Additionally, implement a baseline configuration for SCCM clients that ensures correct site codes and management point addresses.
A useful shortcut is to use the Get-WinEvent cmdlet with specific filters to quickly identify problematic events related to MP connectivity issues.
This comprehensive guide should help system administrators effectively diagnose and resolve errors related to missing Management Point connectivity in Microsoft Configuration Manager.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.