CMG Connection Point Status Disconnected | SCCM | ConfigMgr

Updated: Nov 13

Issue:


SCCM Cloud Management Gateway Connection Point status shows as disconnected after new Cloud Management Gateway configuration in SCCM / Configuration Manager.


The following error logged in CMG connection point log SMS_CLOUD_PROXYCONNECTOR.log file.


ERROR: Failed to build HttpV2 connection 711c3af4-a0a8-44bd-a8dd-01572a7b276c with server xxxCMG.CLOUDAPP.NET:443. Exception: System.Net.WebException: The remote name could not be resolved: 'xxxcmg.cloudapp.net'~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.HttpConnectionV2.SendInternal(HttpMethod method, String path, String payload, Int32& statusCode, Byte[]& responsePayload)~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.HttpConnectionV2.SendInternal(HttpMethod method, String path, Byte[] payload)~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.HttpConnectionV2.Online()~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.ConnectionBase.Start()~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.ConnectionManager.MaintainConnections()




Cause:


The above logs show that remote name was not resolved. This was happening as Microsoft has changed the way CMG service name / Deployment name registered with Azure.


Starting ConfigMgr version 2010, if you'll deploy the CMG to a virtual machine scale set, the deployment name is different. With a virtual machine scale set, the service name uses the cloudapp.azure.com domain along with the region. For example, GraniteFalls.EastUS.CloudApp.Azure.Com for a deployment in the East US Azure region.


In the above setup, the service name Prefix.Cloudapp.net was used which will not longer work with Virtual Machine Scale Set CMG deployment.