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.
Solution:
Option 1: Keep the Service name same as Deployment name.
Examples:
Service Name: Prefix.Region.CloudApp.Azure.Com
e;g: techuisitivecmg.EastUS.CloudApp.Azure.com
Deployment Name: Prefix.Region.CloudApp.Azure.Com
e:g: techuisitivecmg.EastUS.CloudApp.Azure.com
Option 2: Another option is to use your own domain address for CMG service name and create DNS CNMAE to route the traffic to CMG deployment name. Microsoft recommend this method.
Example:
Service Name: techuisitivecmg.techuisitive.com
Deployment name: techuisitivecmg.EastUS.CloudApp.Azure.com
DNS CNAME: Create a DNS CNAME in public DNS (Your DNS registrar) to route the request coming for Service name address to CMG Deployment address.
The Configuration Manager client policy includes the CMG service name, The client resolves the service name via the CNAME alias to the deployment name.
The CNAME for above example will be:
HostName : techuisitivecmg
Value: techuisitivecmg.EastUS.CloudApp.Azure.com
Related Posts:
- SCCM Application Deployment Failed with Error 0x87d01106 | ConfigMgr
- SCCM Client Installation Failed With Error Code 0x87d00215
- PXE-E99: Unexpected network error – SCCM OSD
- Configuration Manager OSD task sequence fails with error code 0x80004005
- MECM OSD Task Sequence Failed with Error 0x80072EE7
- SCCM Client Push Installation Failed with Error 0x800706ba
- Failed to Add Update Source for WUAgent of type (2) and id ({ID). Error = 0x80004005
- SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8
- ccmsetup failed with error code 0x87d00227
- Fix Application Deployment error 0x87d00213 in ConfigMgr
- CMG Connection Point Status Disconnected | SCCM | ConfigMgr
- CMG Setup – Subscription ID drop down not populating
- CMG Setup – Error when granting Contributor permission to the Azure AD app
- Failed to connect with DP – Error Code 0x8004100e | ConfigMgr | SCCM
- SCCM Client Installation Failed with error 0x87d0027e
- ConfigMgr OSD – PXE Troubleshooting
- SCCM WSUS sync error – Sync Failed – WSUS server not configured
- SCCM Software Distribution Troubleshooting
Subscribe to Techuisitive Newsletter
Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.
