Once the device token works, the request is sent to internal MP via CMG to get a CCM token. Client must get a CCM token successfully before accessing internal resources. CCM_STS.log available on the Management Point enabled for CMG traffic is a good place to know if CCM token was issued successfully. ProcessRequest - Start CCM_STSPress J to jump to the feed. Press question mark to learn the rest of the keyboard shortcutsUnfortunately, 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).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 ...Oct 28, 2022 · This article describes an issue in which content can't be downloaded from a cloud management gateway (CMG) that functions as a cloud distribution point (DP), and you receive an WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID error message. Original product version: Configuration Manager (current branch) Original KB number: 4495265 Symptoms 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. … 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'.MDM Session: Failed to get AAD Token for sync session User Token: (The parameter is incorrect.) Device Token: (Incorrect function.). Long story short, I kept removing Device Configuration profiles I had assigned to the device, and the policy causing the issue was to upgrade Pro to Enterprise using an MAK key using the “Edition upgrade” policy. Hi All, I uncheck the check box from Site Properties which disable CRL check. I reinstalled client with SMSMP and /NoCRLCheck switches and Client is now appearing in the Console as Active.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!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 ...Feb 2, 2021 · 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. In here your CMG certificate chain should include the correct certificate chain. as you can see in the illustration, the issuer of this certificate can’t be found, and as such our trust is broken. To fix the issue, copy and import your missing root certificate(s) to the Azure cloud management gateway server. Jul 22, 2019 · 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. Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.CMG stopped servicing clients overnight Between 10pm and 11pm last night it appears our CMG stopped servicing 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: 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 ... Jun 27, 2021 · 1st and foremost you're absolutely welcome. 2nd, if all you need for the time being is an image in wim format than forget about combining ConfigMgr and MDT. You honestly don't need to combine them at this point. SCCM is your deployment and management tool. MDT is the imaging tool. Hell, you don't... 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. …Sep 30, 2020 · 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). Post to https:///ccm_system/request failed with 0x87d00231. LOCATIONSERVICES: Unable to retrieve AD site membershipFeb 2, 2021 · 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. Sep 17, 2020 · We have a customer that has a functional ConfigMgr (CB 2006) environment with a newly configured CMG and Co-Management enabled. All of the CMG related settings and EHTTP settings are enabled. Machines that are Hybrid-AD joined and already have the ConfigMgr client are able to communicate and download software from the CMG. 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. Dec 10, 2013 · Hi All, I uncheck the check box from Site Properties which disable CRL check. I reinstalled client with SMSMP and /NoCRLCheck switches and Client is now appearing in the Console as Active. 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'.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.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)Apr 30, 2020 · Today I wanted to share with you a series of short videos that offer tips on how to address and mitigate common issues you might encounter when setting up the cloud management gateway (CMG) as part of your Configuration Manager environment. Before we begin, a quick reminder that the Microsoft Endpoint Manager admin center can be accessed ... 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... 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 commentsHi All, I uncheck the check box from Site Properties which disable CRL check. I reinstalled client with SMSMP and /NoCRLCheck switches and Client is now appearing in the Console as Active.Sep 17, 2020 · We have a customer that has a functional ConfigMgr (CB 2006) environment with a newly configured CMG and Co-Management enabled. All of the CMG related settings and EHTTP settings are enabled. Machines that are Hybrid-AD joined and already have the ConfigMgr client are able to communicate and download software from the CMG. 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 ...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.CMG stopped servicing clients overnight Between 10pm and 11pm last night it appears our CMG stopped servicing 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: ClientLocation 19/08/2020 17:39:37 2624 (0x0A40) Raising pending event: instance of CCM_CcmHttp_Status { DateTime = "20200819163937.494000+000"; HostName = "cmg.cmg.net"; HRESULT = "0x80072f8f"; ProcessID = 444; StatusCode = 8; ThreadID = 2624; }; ClientLocation 19/08/2020 17:39:37 2624 (0x0A40) Failed in WinHttpSendRequest API, ErrorCode ...Jan 15, 2021 · Specify a name and select Cloud Management, click Next. In this step, the Azure Administrator will be required to create the web app and native client app. Click on Browse for the Web app. Click on Create. Click the Sign in and provide Azure administrator credentials. Default names do just fine. Jul 15, 2019 · Once the device token works, the request is sent to internal MP via CMG to get a CCM token. Client must get a CCM token successfully before accessing internal resources. CCM_STS.log available on the Management Point enabled for CMG traffic is a good place to know if CCM token was issued successfully. ProcessRequest - Start CCM_STS 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 ...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 ...Mar 7, 2019 · 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. Feb 1, 2021 · 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... 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. 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'.Jul 22, 2019 · 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. 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. SCCM 1806 onwards, you have a new in-console utility called CMG connection analyzer. This utility is for real-time verification to help CMG-related troubleshooting. The SCCM in-console utility checks the current status of the service and the communication channel through the CMG connection point to any management points that allow CMG traffic.Client Authentication and Authorization. There are three choices here for systems connecting from the Internet. As implied by the name, this provides authentication or authorization of the client systems by the CMG and the site. These are more or less documented at Certificates for the cloud management gateway – – Client authentication ...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 ...Post to https:///ccm_system/request failed with 0x87d00231. LOCATIONSERVICES: Unable to retrieve AD site membership Failed to verify that the given file is a valid installation package. 782-2146893560: 2148073736: 0×80090108: Failed to access all the provided program locations. This program will not retry. 783-2146893562: 2148073734: 0×80090106: Failed to verify the executable file is valid or to construct the associated command line. 784-2146893564: ...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 ... 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.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'.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 ...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'.Jul 21, 2023 · 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: After upgrading SCCM to the latest version, the OSD stopped working completely. The smsts.log revealed the error: "Sending with Winhttp failed 80072f8f." I'llSince 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. 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.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. 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’.Below are the result from the CA. [Green] CMG in ready state. [Red] Connect to the CMG service to see if it's running. [Red] Check configuration setting of the CMG service is up to date. [Yellow] Check connection status of CMG connection points. [Green] Check CMG enabled site systems roles. [Red] testing the CMG channel for management point.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. …Today I wanted to share with you a series of short videos that offer tips on how to address and mitigate common issues you might encounter when setting up the cloud management gateway (CMG) as part of your Configuration Manager environment. Before we begin, a quick reminder that the Microsoft Endpoint Manager admin center can be accessed ...Cloud Management Gateway - client side problems. SOLVED It seems like it solved itself or by me rebooting the primary site server and/or the CMG. CMG is set up in our CM 1910 env by using a public wildcard certificate. That is all green in the console, as well as the CMG connection point. We are using Enhanced HTTP and hope to use AAD identity ...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.I have set up a cloud management gateway in my MECM Environment. PKI Infrastructure is also in place, and it is working as expected. The MECM clients function fine when communicating with the local MP (on-premises MP); however, clients cannot discover a…Post to https:///ccm_system/request failed with 0x87d00231. LOCATIONSERVICES: Unable to retrieve AD site membershipPost to https:///ccm_system/request failed with 0x87d00231. LOCATIONSERVICES: Unable to retrieve AD site membership Post to https:///ccm_system/request failed with 0x87d00231. LOCATIONSERVICES: Unable to retrieve AD site membershipWhen 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 ...After upgrading SCCM to the latest version, the OSD stopped working completely. The smsts.log revealed the error: "Sending with Winhttp failed 80072f8f." I'llERROR: TaskManager: Task [AnalyticsCollectionTask: Service MyServicecmg] has failed. Exception Microsoft.WindowsAzure.Storage.StorageException, The remote server returned an error: (404) Not Found.. We have attempted to delete and recreate the CMG multiple times but come across the same issue.May 18, 2022 · SCCM 1806 onwards, you have a new in-console utility called CMG connection analyzer. This utility is for real-time verification to help CMG-related troubleshooting. The SCCM in-console utility checks the current status of the service and the communication channel through the CMG connection point to any management points that allow CMG traffic. 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'. 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.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'.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 ?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.Cloud Management Gateway - client side problems. SOLVED It seems like it solved itself or by me rebooting the primary site server and/or the CMG. CMG is set up in our CM 1910 env by using a public wildcard certificate. That is all green in the console, as well as the CMG connection point. We are using Enhanced HTTP and hope to use AAD identity ...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. May 18, 2022 · SCCM 1806 onwards, you have a new in-console utility called CMG connection analyzer. This utility is for real-time verification to help CMG-related troubleshooting. The SCCM in-console utility checks the current status of the service and the communication channel through the CMG connection point to any management points that allow CMG traffic. 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.[ccmsetup] Failed to get MDM_ConfigSetting instance, 0x80041010_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.Oct 3, 2022 · 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. 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’.
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... . Rancher
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.SCCM 1806 onwards, you have a new in-console utility called CMG connection analyzer. This utility is for real-time verification to help CMG-related troubleshooting. The SCCM in-console utility checks the current status of the service and the communication channel through the CMG connection point to any management points that allow CMG traffic.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 ... Below are the result from the CA. [Green] CMG in ready state. [Red] Connect to the CMG service to see if it's running. [Red] Check configuration setting of the CMG service is up to date. [Yellow] Check connection status of CMG connection points. [Green] Check CMG enabled site systems roles. [Red] testing the CMG channel for management point.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’. Feb 3, 2021 · CMG-<cloud_service_name>-ProxyService_IN_0-CMGSetup.log: Records details about the second phase of the cloud management gateway deployment (local deployment in Azure). CloudMgr.log : Records details about deploying the cloud management gateway service, ongoing service status, and use data associated with the service. Hi All, I uncheck the check box from Site Properties which disable CRL check. I reinstalled client with SMSMP and /NoCRLCheck switches and Client is now appearing in the Console as Active.Apr 30, 2020 · Today I wanted to share with you a series of short videos that offer tips on how to address and mitigate common issues you might encounter when setting up the cloud management gateway (CMG) as part of your Configuration Manager environment. Before we begin, a quick reminder that the Microsoft Endpoint Manager admin center can be accessed ... 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 ...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.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)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.Oct 28, 2022 · This article describes an issue in which content can't be downloaded from a cloud management gateway (CMG) that functions as a cloud distribution point (DP), and you receive an WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID error message. Original product version: Configuration Manager (current branch) Original KB number: 4495265 Symptoms However, I've hit a wall when switching the MP over to HTTPS. The clients still continue to use HTTP! For the record, the overall Client Security settings are still set to 'HTTP or HTTPS' (without Enhanced HTTP turned on). From CCMEVAL I can see that it clearly tries to use HTTP. Client is set to use HTTPS when available. The current state is 480..
