Oct 3, 2022 · Choose the certificate type. Globally unique name. Issue the certificate. Create a DNS CNAME alias. Next steps. Applies to: Configuration Manager (current branch) The first step when you set up a cloud management gateway (CMG) is to get the server authentication certificate. The CMG creates an HTTPS service to which internet-based clients ... Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: Successfully queued event on HTTP/HTTPS failure for server 'CMG.CENTRALUS.CLOUDAPP.AZURE.COM'. Go to Monitoring / Cloud Management. Natiguate to the bottom of the Dashboard, in the Cloud Management Gateway Statistics section. From there you can validate that there’s some client communicating and their authentication methods. If there’s anything wrong, the next step is to use the Cloud Management Gateway Connection Analyser.I have set up Configuration Manager by the book. I had to integrate it with an existing WSUS and SQL Server. I have not been able to successfully push the agent to the three workstations that I tried. Oddly, one workstation installed a little better than the other one, but neither is fully...Apr 10, 2019 · Failed to get ConfigMgr token with Azure AD token. Status code is '403' and status description is 'CMGConnector_Un-authorizedrequest'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: 'Un-authorizedrequest'. Failed to get ConfigMgr token with Azure AD token. Status code is '401' and status description is 'CMGConnector_Unauthorized'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: 'Unauthorized'.Clients failed to connect to CMG MP in the cloud, Site is configured to E-http Client are AAD hybrid. Thanks LocationServices.log: MapNLMCostDataToCCMCost() returning Cost 0x1 LocationServices 27/06/2021 09:28:14 2088 (0x0828)Nov 9, 2022 · Error: 0x87d00231 ClientIDManagerStartup 08/11/2022 5:49:12 PM 5540 (0x15A4) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 08/11/2022 5:49:12 PM 5540 (0x15A4) [RegTask] - Sleeping for 60 seconds ... Note: Non-Microsoft link, just for the reference. Uncheck the check box of Clients check the CRL for site systems from Site Properties. Reinstalled client with /NoCRLCheck CCMHOSTNAME=InternetFQDN with SMSSite code switches. If the response is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our ...Jun 27, 2021 · Hi, I have installed in our environment SCCM CMG and the client is unable to receive software updates. This is what I see in WUAHandler.log: Its a WSUS Update Source type ({A4BF5916-DF74-44C1-BF58-68AE14A43278}), adding it. … Failed to get ConfigMgr token with Azure AD token. Status code is '401' and status description is 'CMGConnector_Unauthorized'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: 'Unauthorized'.Good afternoon Everyone! So my SCCM client will not install nor adequately communicate with any systems that did not already have the client installed prior to my MP failing. Luckily I fixed my MP, but I can only communicate with clients that were previously installed. And it communicates... Connect to the CMG service to see if it's running. Failed to connect to the CMG service. Unexpected response status code is NameResolutionFailure. For more information, see SmsAdminUI.log. Check configuration settings of the CMG service is up to date. Configuration version of the CMG service should be 5. Failed to get CMG service metadata.It works fine by changing the "UserCost" value as '0', after that CM client installation gets worked.The CMG connection analyzer tool fails when testing the CMG channel for a management point that uses a replica database. Errors resembling the following are recorded in the CCM_STS.log Return code: 500, Description: Failed to get info from DB, System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'fn_GetUserResourceMapping'.To Resolve: Change the registry key value (DisableRenegoOnClient) from 1 to 0 and restart the CCMExec service. reg add "hklm\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL" -v DisableRenegoOnClient /t REG_DWORD /d 0 /f. powershell -executionpolicy bypass -command restart-service ccmexec. PS.Oct 28, 2022 · In the Configuration Manager console, go to Administration > Site Configuration > Servers and Site System Roles, and then select <SiteSystemName> in the right pane. In the bottom pane, right-click Software Update Point and then click Properties. On the General tab, specify or verify the WSUS configuration port numbers. May 19, 2020 · Failed to get ConfigMgr token with Azure AD token. Status code is '401' and status description is 'CMGConnector_Unauthorized'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. Yes, the clients have a trusted root to the internal PKI used for CMG. Thank you, I have installed the CMG connection point. The MP is installed using E-HTTP. In this case the CMG connection won't require a client authentication certificate. Is this correct ?In the SCCM CB console, choose Administration. 2. In the Administration workspace, expand Site Configuration, choose Sites, and then choose the primary site server. 3. Right-click on the Primary site server, choose Properties and choose the Client Computer Communication tab.Feb 6, 2020 · Logged. #1. February 06, 2020, 08:03:52 AM. 0x87D00669 = Not able to get software updates content locations at this time. This means the client can't find the update in the DP's. Please make sure your package is distributed and boundaries set up. Failed to get ConfigMgr token with Azure AD token. Status code is '401' and status description is 'CMGConnector_Unauthorized'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: 'Unauthorized'. Nov 27, 2017 · but the client did not get it !!! what could be the issue? in ClientIDManagerStartup.log [RegTask] - Client is not registered. Sending registration request for GUID:0F401FC7-A72A-468C-8949-D07C22A761D0 ... ClientIDManagerStartup 11/20/2017 3:58:31 PM 2888 (0x0B48) RegTask: Failed to send registration request message. Connect to the CMG service to see if it's running. Failed to connect to the CMG service. Unexpected response status code is NameResolutionFailure. For more information, see SmsAdminUI.log. Check configuration settings of the CMG service is up to date. Configuration version of the CMG service should be 5. Failed to get CMG service metadata.Hi, I have configured a CMG and deployed to PKI certificate to Client for authentication. However still clients not get registered through CMG. Please help. Location Service ...Unfortunately, 0x87d00231 is a fairly generic error message that pretty much just means “something went wrong”. If you Google it, you will see a variety of solutions ranging from reinstalling the client to checking your PKI environment is functioning correctly or checking the health of your Management Point (s).MCSE Cloud Platform and Infrastructure. MCSE: Mobility. MCSE: Data Management and Analytics. MCSE Productivity. Find technical communities in your area. MSDN Forums. Security Bulletins & Advisories. Microsoft Community Forums.You are right regarding the security concerns but actually it's a POC server and after that we will replicate to a production environment. And regarding the certificate the CRLis listed on the server and client certificate as below screenshots.Sep 27, 2020 · CMG Connection point. CMG status is ready and connection point is in Connected status. On the client machine--> Control panel--> Configuration Manager-->Network tab shows the Internet-based MP FQDN correctly which is the CMG. Assigned the new MP site system to the boundary group and confirmed that the client is able to identify the available MPs. You would have to examine a combination of various logs to get an idea what was happening (CLientIDManagerStartup.log on the client, IIS logs, mpcontrol.log and MP_ClientRegistration.log on the MP). 0x80072efe = "The connection with the server was terminated abnormally". This basically equates to something somewhere outside of ConfigMgr's ...In the SCCM CB console, choose Administration. 2. In the Administration workspace, expand Site Configuration, choose Sites, and then choose the primary site server. 3. Right-click on the Primary site server, choose Properties and choose the Client Computer Communication tab.Error: 0x87d00231 ClientIDManagerStartup 11/20/2017 3:58:37 PM 2888 (0x0B48) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 11/20/2017 3:58:37 PM 2888 (0x0B48)Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: Successfully queued event on HTTP/HTTPS failure for server 'CMG.CENTRALUS.CLOUDAPP.AZURE.COM'.The first thing we checked here is the port 443 connectivity from this test machine to the CMG public IP using the port query UI tool. Port connectivity was fine, and it was listening for port 443 without any issue. After hours of troubleshooting, we identified that the PKI infrastructure has multiple CAs.Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: Successfully queued event on HTTP/HTTPS failure for server 'CMG.CENTRALUS.CLOUDAPP.AZURE.COM'.Failed to get ConfigMgr token with Azure AD token. Status code is '403' and status description is 'CMGConnector_Un-authorizedrequest'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: 'Un-authorizedrequest'.We decided to tackle the errors in SMS_CloudConnector.log that indicated the connector role was unable to connect on port 10140, even though according to the documentation that port (and the rest of the range, 10124-10156) were only required if running more than one VM instance for the CMG. This required a firewall change to allow the ...RegTask: Failed to refresh site code. Error: 0x8000ffff ClientIDManagerStartup 23/08/2021 14:39:42 14956 (0x3A6C) Sleeping for 289 seconds before refreshing location services. ClientIDManagerStartup 23/08/2021 14:39:43 14956 (0x3A6C) LocationService.Log - Security settings update detected, restarting CcmExec.Error: 0x87d00231 ClientIDManagerStartup 11/20/2017 3:58:37 PM 2888 (0x0B48) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 11/20/2017 3:58:37 PM 2888 (0x0B48)Post to https:///ccm_system/request failed with 0x87d00231. LOCATIONSERVICES: Unable to retrieve AD site membership When I run the connection analyzer it's failing on a couple of steps: Failed to connect to the CMG service. Unexpected response status code is NameResolutionFailure. For more information, Configuration version of the CMG service should be 1. Failed to get CMG service metadata.The Clients use internal PKI certs and CMG uses a public wildcard cert. When I put one of the Clients on the Internet and tried to get an app installed, the attempt failed, as well, the Client went grey in SCCM console. I checked the Client settings and found it knows about CMG, but cannot connect to it. in ccmMessaging.log I saw:RegTask: Failed to refresh site code. Error: 0x8000ffff ClientIDManagerStartup 23/08/2021 14:39:42 14956 (0x3A6C) Sleeping for 289 seconds before refreshing location services. ClientIDManagerStartup 23/08/2021 14:39:43 14956 (0x3A6C) LocationService.Log - Security settings update detected, restarting CcmExec.Hi, I have configured a CMG and deployed to PKI certificate to Client for authentication. However still clients not get registered through CMG. Please help. Location Service ...Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: Successfully queued event on HTTP/HTTPS failure for server 'CMG.CENTRALUS.CLOUDAPP.AZURE.COM'. Hi, I have installed in our environment SCCM CMG and the client is unable to receive software updates. This is what I see in WUAHandler.log: Its a WSUS Update Source type ({A4BF5916-DF74-44C1-BF58-68AE14A43278}), adding it. …Jan 4, 2017 · You are right regarding the security concerns but actually it's a POC server and after that we will replicate to a production environment. And regarding the certificate the CRLis listed on the server and client certificate as below screenshots. Error: 0x87d00231 ClientIDManagerStartup 11/20/2017 3:58:37 PM 2888 (0x0B48) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 11/20/2017 3:58:37 PM 2888 (0x0B48)You are right regarding the security concerns but actually it's a POC server and after that we will replicate to a production environment. And regarding the certificate the CRLis listed on the server and client certificate as below screenshots.Jul 20, 2018 · Failed to get ConfigMgr token with Azure AD token. Status code is ‘503’ and status description is ‘CMGConnector_ServiceUnavailable’. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: ‘ServiceUnavailable’. We had the wrong root cert in our CMG properties which is why the client didn’t register properly with PKI once that was replaced and the client restarted, it registered fine. Reply Justin Chalfant on August 8, 2021 at 11:01 AMNov 1, 2022 · After upgrading from SCCM 2203 to 2207, the upgrade failed, we were getting an error, failed to update key vault, bad request. so in an effort to work around the problem, we decided we could try to tear out the existing CMG and reimplement using all new names and to a new resource group, However, the new cmg fails to deploy with the same exact ... Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: Successfully queued event on HTTP/HTTPS failure for server 'CMG.CENTRALUS.CLOUDAPP.AZURE.COM'.RegTask: Failed to send registration request message. Error: 0x87d00231 ClientIDManagerStartup 5/18/2016 12:20:21 PM 456 (0x01C8) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 5/18/2016 12:20:21 PM 456 (0x01C8) [RegTask] – Sleeping for 960 seconds …May 19, 2020 · Failed to get ConfigMgr token with Azure AD token. Status code is '401' and status description is 'CMGConnector_Unauthorized'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. May 23, 2020 · I’m paranoid. We recently upgraded our site to ConfigMgr 2002, first fast ring, then the hotfix. We also installed a Cloud Management Gateway, re-worked our Boundary Groups to handle VPN better, added a second Management Point and generally made a butt-load of changes to our environment to help our remote clients have access to content more easily. It works fine by changing the "UserCost" value as '0', after that CM client installation gets worked.Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcutsPosts about 0x87d00231 written by Leldance40k. I am torn between two lines of thought. It’s down to the “No CRL checking” option being set on the Config Manager site server; whilst this may bypass some CRL “stuff”, it’s needed for to get other things going. In the Site Properties under client communications the option 'Check CRL' was checked. In our environment the CRL is not published. This setting caused the authentication to fail as it is unable to retrieve the CRL information. After unchecking that option and reinstalling the SCCM agent from the primary site, the authentication is now working.Since we are using Internal PKI cert on CMG, I have exported the Root certificate and imported into DMZ server, Installation went fine and client was able to communicate well after the installation. It received all policies and able to push software updates/apps. You would have to examine a combination of various logs to get an idea what was happening (CLientIDManagerStartup.log on the client, IIS logs, mpcontrol.log and MP_ClientRegistration.log on the MP). 0x80072efe = "The connection with the server was terminated abnormally". This basically equates to something somewhere outside of ConfigMgr's ...Clients failed to connect to CMG MP in the cloud, Site is configured to E-http Client are AAD hybrid. Thanks LocationServices.log: MapNLMCostDataToCCMCost() returning Cost 0x1 LocationServices 27/06/2021 09:28:14 2088 (0x0828)After the process of installing the workgroup clients in the internal network is completed and the clients go to the Internet, they are unable to communicate the cmg. I think the root problem is that they were unable to register to the internal MP-HTTPS server during the task and get the token. PKI cert for cmg issued from our internal CA. One of our stations fails to connect to SCCM, the log errors are: RegTask: Failed to send registration request message. Error: 0x87d00231. RegTask: Failed to send registration request. Error: 0x87d00231. If this is related then the MP is set to HTTP.Connect to the CMG service to see if it's running. Failed to connect to the CMG service. Unexpected response status code is NameResolutionFailure. For more information, see SmsAdminUI.log. Check configuration settings of the CMG service is up to date. Configuration version of the CMG service should be 5. Failed to get CMG service metadata.You are right regarding the security concerns but actually it's a POC server and after that we will replicate to a production environment. And regarding the certificate the CRLis listed on the server and client certificate as below screenshots.My lab recently started playing up when I noticed clients weren’t receiving any new policies. TDLR (it’s not even that long!): a while ago I moved my SUP/WSUS off host from the site server that also hosted a MP.Oct 3, 2022 · Choose the certificate type. Globally unique name. Issue the certificate. Create a DNS CNAME alias. Next steps. Applies to: Configuration Manager (current branch) The first step when you set up a cloud management gateway (CMG) is to get the server authentication certificate. The CMG creates an HTTPS service to which internet-based clients ... In the Site Properties under client communications the option 'Check CRL' was checked. In our environment the CRL is not published. This setting caused the authentication to fail as it is unable to retrieve the CRL information. After unchecking that option and reinstalling the SCCM agent from the primary site, the authentication is now working.You would have to examine a combination of various logs to get an idea what was happening (CLientIDManagerStartup.log on the client, IIS logs, mpcontrol.log and MP_ClientRegistration.log on the MP). 0x80072efe = "The connection with the server was terminated abnormally". This basically equates to something somewhere outside of ConfigMgr's ...Jun 27, 2021 · Hi, I have installed in our environment SCCM CMG and the client is unable to receive software updates. This is what I see in WUAHandler.log: Its a WSUS Update Source type ({A4BF5916-DF74-44C1-BF58-68AE14A43278}), adding it. … Error: 0x87d00231" Reinstall the agent seems to solve the issue when we try on one of the client but just thought checking up what could be the possible issue. Its will be hard on patch compliance if user lost connection to CMG due to this issue. We currently on MECM version 2010 and using PKI cert for CMG communication. Appreciate all the input!Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: Successfully queued event on HTTP/HTTPS failure for server 'CMG.CENTRALUS.CLOUDAPP.AZURE.COM'.Oct 27, 2018 · Expert-led, virtual classes. Microsoft Virtual Academy. Free Windows Server 2012 courses. Microsoft Official Courses On-Demand. MCSE Cloud Platform and Infrastructure. MCSE: Mobility. MCSE: Data Management and Analytics. MCSE Productivity. Find technical communities in your area. Unfortunately, 0x87d00231 is a fairly generic error message that pretty much just means “something went wrong”. If you Google it, you will see a variety of solutions ranging from reinstalling the client to checking your PKI environment is functioning correctly or checking the health of your Management Point (s).Sounds like you need to reconfigure it to use HTTPS. We've resolved this, apparently it was becuase we needed to use /mp: https://SCCMServer.FQDN for an install parameter. We were missing the "https://" previously.Unfortunately, 0x87d00231 is a fairly generic error message that pretty much just means “something went wrong”. If you Google it, you will see a variety of solutions ranging from reinstalling the client to checking your PKI environment is functioning correctly or checking the health of your Management Point (s).by MrOarsome Issue with CMG and clients authenticating via Hybrid Azure AD: Failed to send registration request message. Error: 0x87d00231 I have gone through the steps of setting up a CMG with with SCCM CB 1906 and all seems to be behaving. However, when my test clients seem to be unable to connect to the CMG service.Jun 21, 2020 · we do have the cmg configured as a distribution point. CMG distro was up and working prior to the upgrade, however this would be the first time a client upgrade would have happened over cmg. we now have around 20 devices with a client, however I believe these were likely devices that came back on the intranet and got the client while onsite. Yes, the clients have a trusted root to the internal PKI used for CMG. Thank you, I have installed the CMG connection point. The MP is installed using E-HTTP. In this case the CMG connection won't require a client authentication certificate. Is this correct ?Sounds like you need to reconfigure it to use HTTPS. We've resolved this, apparently it was becuase we needed to use /mp: https://SCCMServer.FQDN for an install parameter. We were missing the "https://" previously.Morning, I'm pushing out client to some of our DMZ servers. Client installation finished successfully as far as I can see from ccmsetup.log file. Investigating further, I noticed I kept getting the following in ClientIDManagerStartup.log: RegTask: Failed to send registration request message. Error: 0x87d00231.Client verifies the CMG server authentication certificate: PKI certificate: Client requires the root CA of the CMG certificate in its local store. Third-party certificate: Clients automatically validate a certificate with its root CA published on the internet. CMG, CMG connection point, and management point validate Azure AD and CCM tokens.Mar 16, 2016 · To Resolve: Change the registry key value (DisableRenegoOnClient) from 1 to 0 and restart the CCMExec service. reg add "hklm\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL" -v DisableRenegoOnClient /t REG_DWORD /d 0 /f. powershell -executionpolicy bypass -command restart-service ccmexec. PS. Apr 2, 2020 · Hi, for info, there is an order. We recently had issues with some our servers in the DMZ, most used the token, however we had a couple that already had certs on them using their FQDN which wouldn’t register in the console. When running the CMG validation checker All checks are successful except the last one and it reports the following error: Succeed to get ConfigMgr token with Azure AD token. Failed to refresh MP location. Status code is ‘500’ and status description is ‘CMGConnector_InternalServerError’. A possible reason for this failure is the CMG ...Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: Successfully queued event on HTTP/HTTPS failure for server 'CMG.CENTRALUS.CLOUDAPP.AZURE.COM'.Connect to the CMG service to see if it's running. Failed to connect to the CMG service. Unexpected response status code is NameResolutionFailure. For more information, see SmsAdminUI.log. Check configuration settings of the CMG service is up to date. Configuration version of the CMG service should be 5. Failed to get CMG service metadata.marking this as solved as it seems like i am stuck with PKI for the time being :( it's a pain because it stops the SCCM client registering quickly enough after a task sequence and I get loads of PCs without hardware inventory because IT shut them down and shipped them out to someone before the client registered, or before it ran hardware inventory.Choose the certificate type. Globally unique name. Issue the certificate. Create a DNS CNAME alias. Next steps. Applies to: Configuration Manager (current branch) The first step when you set up a cloud management gateway (CMG) is to get the server authentication certificate. The CMG creates an HTTPS service to which internet-based clients ...
Mar 19, 2018 · ClientIDManagerStartup 3/16/2018 9:13:33 AM 7968 (0x1F20) CCM Identity is in sync with Identity stores ClientIDManagerStartup 3/16/2018 9:13:33 AM 7968 (0x1F20) Begin searching client certificates based on Certificate Issuers ClientIDManagerStartup 3/16/2018 9:13:33 AM 7968 (0x1F20) Certificate Issuer 1 [CN=Entrust Root Certification Authority ... . 1900
Jun 22, 2017 · We decided to tackle the errors in SMS_CloudConnector.log that indicated the connector role was unable to connect on port 10140, even though according to the documentation that port (and the rest of the range, 10124-10156) were only required if running more than one VM instance for the CMG. This required a firewall change to allow the ... It works fine by changing the "UserCost" value as '0', after that CM client installation gets worked.Nov 1, 2022 · After upgrading from SCCM 2203 to 2207, the upgrade failed, we were getting an error, failed to update key vault, bad request. so in an effort to work around the problem, we decided we could try to tear out the existing CMG and reimplement using all new names and to a new resource group, However, the new cmg fails to deploy with the same exact ... Note: Non-Microsoft link, just for the reference. Uncheck the check box of Clients check the CRL for site systems from Site Properties. Reinstalled client with /NoCRLCheck CCMHOSTNAME=InternetFQDN with SMSSite code switches. If the response is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our ...You would have to examine a combination of various logs to get an idea what was happening (CLientIDManagerStartup.log on the client, IIS logs, mpcontrol.log and MP_ClientRegistration.log on the MP). 0x80072efe = "The connection with the server was terminated abnormally". This basically equates to something somewhere outside of ConfigMgr's ...One of our stations fails to connect to SCCM, the log errors are: RegTask: Failed to send registration request message. Error: 0x87d00231. RegTask: Failed to send registration request. Error: 0x87d00231. If this is related then the MP is set to HTTP.To Resolve: Change the registry key value (DisableRenegoOnClient) from 1 to 0 and restart the CCMExec service. reg add "hklm\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL" -v DisableRenegoOnClient /t REG_DWORD /d 0 /f. powershell -executionpolicy bypass -command restart-service ccmexec. PS.Feb 2, 2021, 2:30 AM Hi all, We have SCCM 2002 , after the CMG implementation , when we force the client to internet , sccm client not reporting to SCCM site server, with below error , any suggestion pls Failed to get CMG metadata 0x87d00227 Failed to get management points from XXXXX. Error 0x87d00227 Not Monitored Sign in to follow 0 commentsIt works fine by changing the "UserCost" value as '0', after that CM client installation gets worked.The CMG connection analyzer tool fails when testing the CMG channel for a management point that uses a replica database. Errors resembling the following are recorded in the CCM_STS.log Return code: 500, Description: Failed to get info from DB, System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'fn_GetUserResourceMapping'. After the process of installing the workgroup clients in the internal network is completed and the clients go to the Internet, they are unable to communicate the cmg. I think the root problem is that they were unable to register to the internal MP-HTTPS server during the task and get the token. PKI cert for cmg issued from our internal CA. Nov 9, 2022 · Error: 0x87d00231 ClientIDManagerStartup 08/11/2022 5:49:12 PM 5540 (0x15A4) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 08/11/2022 5:49:12 PM 5540 (0x15A4) [RegTask] - Sleeping for 60 seconds ... marking this as solved as it seems like i am stuck with PKI for the time being :( it's a pain because it stops the SCCM client registering quickly enough after a task sequence and I get loads of PCs without hardware inventory because IT shut them down and shipped them out to someone before the client registered, or before it ran hardware inventory.Only this laptop have issue in installing SCCM client. What are the other ways to make SCCM communcation with MP.Jan 4, 2017 · You are right regarding the security concerns but actually it's a POC server and after that we will replicate to a production environment. And regarding the certificate the CRLis listed on the server and client certificate as below screenshots. .