Solved: Configuration Manager Client Installation Fails with error 0x87d0027e

Error:

[CCMHTTP] ERROR: URL=http://configmgrmp01.pj360i.com/ccm_system/request, Port=80, Options=1248, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE
Failed (0x87d0027e) to send location request to 'configmgrmp01.pj360i.com'. StatusCode 403, StatusText 'Forbidden'
GetDPLocations failed with error 0x87d0027e
Failed to get DP locations as the expected version from MP 'configmgrmp01.pj360i.com'. Error 0x87d0027e

This problem happens when Management Point is configured with HTTPS but the Configuration Manager client is installed using http installation properties. To resolve this, use https with a fully-qualified domain name (FQDN) in the /mp switch. In my situation, the server FQDN is configmgrmp01.pj360i.com, hence my client installation command is as follows:

C:\Windows\ccmsetup\ccmsetup.exe SMSSITECODE=PS1 /mp:https://configmgrmp01.pj360i.com

Verify both ccmsetup.log and clientmsi.log present in "C:\Windows\ccmsetup\Logs"

Create Configuration Manager Collection based on Heartbeat DDR

 We'll look at how to create a Device collection that will display clients who haven't reported back to Configuration Manager in 14 days based on the client Heartbeat DDR agent date.

To find configuration manager clients that aren't sending heartbeat DDR older than 14 days, copy the below query to create a device collection. You can also change the 14 days to any number of days based on your office's needs.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ResourceId not in (select ResourceID from SMS_R_System where AgentName in ("Heartbeat Discovery") and DATEDIFF(day,AgentTime,GetDate())<14)

How to Configure Client Status in Configuration Manager - How to find when ConfigMgr Client status change to Inactive

How to Configure Client Status in Configuration Manager?

How to find when ConfigMgr Client status change to Inactive?

Follow the below steps:

Open Microsoft Endpoint Configuration Manager console, click Monitoring.

In the Monitoring workspace, click Client Status, then, in the Home tab, in the Client Status group, click Client Status Settings.

In the Client Status Settings Properties dialog box, specify the following values to determine client activity:
If none of the conditions are met, the client will be updated as inactive. Change the default values as per your organization client settings requirements:

• Client policy requests during the following days (Default value is 7 days)
• Heartbeat discovery during the following days (Default value is 7 days)
• Hardware inventory during the following days (Default value is 7 days)
• Software inventory during the following days (Default value is 7 days)
• Status messages during the following days (Default value is 7 days)

Configuration Manager: How to force the machine to send DDR, Location Request, MP, and compliance report

To force any windows machine/computer's client agent to trigger sending DDR, Location Request, MP, and compliance report to Configuration Manager, please use the below command and run as administrator:

([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000012}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000024}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000111}'); [wmi]"ROOT\ccm\invagt:InventoryActionStatus.InventoryActionID='{00000000-0000-0000-0000-000000000003}'" | remove-wmiobject ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000003}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000021}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000022}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000040}') | out-null; "Eval. MachinePolicy"; [void]([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000113}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000108}'); "Update scan and evaluation" (New-Object -ComObject Microsoft.CCM.UpdatesStore).RefreshServerComplianceState()

Configuration Manager: Client Status and Categories

You might have came across below four client check categories during application or software update deployments - Unknown in Configuration Manager:

• Client check failed/Active
• Client check failed/Inactive
• Client check passed/Active
• Client check passed/Inactive

In this post, we'll see what these categories really implies. The distinction between Active and Inactive machines are an arbitrary date limit (by default, 7 days) for when it talked to Configuration Manager final. So the machines falls beneath "Client check passed/Inactive" implies the final commination with ConfigMgr, the client check was great, but haven't listened anything in at least 7 days.

Active implies the client has communicated with Configuration Manager since the limit. For case, in the event that the limit is set at the default of 7 days and a client communicated with the server 5 days prior, it would appear up as "Active" within the console.

You can change the limit in the Monitoring workspace by right clicking on Client Activity:

Client Status Settings window looks like below screenshot:

Client status update can be scheduled by right clicking on Client Activity:

Statistics of Click Status:

    Statistics dashboard in the client status will give you the detailed view of clients which are active/inactive:

Below are few examples of client check failures: