Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Currently we manage about 100 clients and everything looks fine except the SMS Agent on
. This time while installing the SCCM, he used a new site code and noticed that SCCM client agents were not discovering the site code. So looking in locationservices.log on my laptop, I am seeing "Failed in WinHttpSendRequest API, ErrorCode = 0x2ee2" and also "Failed to send management point list Location Request Message to Sccmserver.FQDN". I recently helped an IT guy fix an issue where the SCCM client agent could not discover the site code. This key is located under HKLM\SOFTWARE\Microsoft\SMS\Mobile Client. Name: 'SERVER1.domain.local' HTTPS: 'N' ForestTrust: 'N'
Failed to send management point list Location Request Message tocontoso.com LocationServices 9/25/2018 9:40:41 PM 1380 (0x0564) 4 assigned MP errors in the last 10 minutes, threshold is 5. A quick ipconfig check showed that a Mobile Broadband adapter was present in the device and it had an IP address and was connected. The only error in MPcontrol.log is "Call to HttpSendRequestSync failed for port 443 with status code 401, text: Unauthorized". Ant migration tool--FAILED TO SEND REQUEST. I am sure those are correct. It used to be that I give it a finishing task sequence that syspreps our AV solution and runs the Prepare ConfigMgr Client for Capture. Failed to get DP locations as the expected version from MP. In this post I will cover about SCCM client site code discovery unsuccessful. I have also checked the mpcert and mplist on the Windows 7 clients and they appear Ok. In other words the SCCM client site code discovery was unsuccessful. Failed in WinHttpSendRequest API, ErrorCode = 0x2f8f Successfully queued event on HTTP/HTTPS failure for server MACHINENAME Failed to send management point list Location Request Message to MACHINENAME The locationservices.log sprung the first clue. I changed the value of GPRequestedSiteAssigmentCode key from USA to new site code. Failed to create or open file mapping for CcmFrameworkServer\CcmIsapi. Successfully sent location services on HTTP failure switching to success message for MP 'BBK-SCCM-PRI.bbk2310.com'. Are you referring to extending the AD schema and making the permissions change on the container? Failed in WinHttpSendRequest API, ErrorCode = 0x2f8f I guess your experience working with SCCM helped narrow down the logs that were required for troubleshooting. Strange "failed to send" errors in LocationServices.log Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. Im wondering why the sequence couldnt properly prepare itself to be cloned, needing additional powershell to remove certificates, and why it will no longer pick up the site automatically? (LogOut/ Every day the ccmeval task runs succesfully, no warnings or errors. SOLVED - SCCM Agent shown as "Client NO" in console from untrusted ProcessID = 11476; Querying MPHealthCheckIntervalInSeconds registry value returned a status of 2. We have one primary site running SCCM 2012 SP1 with two Management Points and four Distribution Points anda few thousand clients are on their way to get managed! If I start the Configuration Manager Service Manager and query the SMS_MP_Control_Manager, it shows that it is stopped, when I start it, i get the above error immediately in the event log.. The strange thing was that the software updates were successfully applying to new devices but always failing on rebuilds. I have checked the client ccmsetup logs and found the certificate he chose and it's a self-signed certificate instead of the Signed by CA Certificate.I have solved the issue by deleting the self-signed certificate and the client was installed successfully. LocationServices 11/2/2022 9:35:32 AM 9512 (0x2528)Refreshed Root Site Code from AD LocationServices 11/2/2022 9:35:32 AM 9512 (0x2528)Attempting to refresh TRK from AD LocationServices 11/2/2022 9:35:32 AM 9512 (0x2528)Refreshed TRK from AD LocationServices 11/2/2022 9:35:32 AM 9512 (0x2528)Raising event:instance of CCM_CcmHttp_Status{DateTime = "20221102163532.513000+000";HostName = "SCCM1.OurDomain.net";HRESULT = "0x00000000";ProcessID = 8736;StatusCode = 0;ThreadID = 9512;};LocationServices 11/2/2022 9:35:32 AM 9512 (0x2528)Status Agent hasn't been initialized yet. Post to http://BBK-SCCM-PRI.bbk2310.com/ccm_system_windowsauth/request failed with 0x8000000a. But a few minutes later the errors are back in LocationServices.log. Successfully queued event on HTTP/HTTPS failure for server 'SiteServer.Domain.local'. [CCMHTTP] : WINHTTP_CALLBACK_STATUS_FLAG_CERT_REV_FAILED is set Failed to check url HTTPS://VRPSCCMMS03.ad/CCM_Client/ccmsetup.cab. The installation went fine but checking the client properties showed something like this. WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID. Instance of CCM_SourceUpdateClientConfig doesn't exist in WMI. Issue has been solved by uninstalling and re-installing the MP. The client on my MP has previously worked, but from time to time, stops talking to itself. The description for Event ID ( 63 ) in Source ( WinMgmt ) could not be found. Worker thread [software Metering Processor Usage (Site)] halting execution. It may not display this or other websites correctly. ]LOG]!>