SCCM CMG - Classic to Virtual scale set

Mohd Atif Husain 120

Dear Team,

We have a situation where CMG is running on Classic deployment method and customer is asking to convert it to Virtual scale set method.

Things to keep in mind is, MS says if your service name is cloudapp.net you cannot convert it and here in this case the Service name is not cloudapp.net but deployment name is cloudapp.net. So, question is would that effect the convert procedure? Basically, deployment name and service name are different.

Please suggest a best way to migrate the CMG.

1 answer

XinGuo-MSFT 14,851 Reputation points

2024-05-06T08:43:28.3533333+00:00

Hi,

Based on my understanding, if Service name is not cloudapp.net, you can convert it to a virtual machine scale set.

https://learn.microsoft.com/en-us/mem/configmgr/core/clients/manage/cmg/modify-cloud-management-gateway#update-or-create-a-dns-cname

If your CMG's service name is in the cloudapp.net domain, you can't convert it to a virtual machine scale set. For example, you issued a server authentication certificate from your internal PKI with a common name of GraniteFalls.cloudapp.net. Since Microsoft owns the cloudapp.net domain, you can't create a DNS CNAME to map this service name to the new deployment name in the cloudapp.azure.com domain.

For example:

The CMG's service name is GraniteFalls.contoso.com.

For the deployment name:

Classic: GraniteFalls.cloudapp.net

Virtual machine scale set: GraniteFalls.EastUS.CloudApp.Azure.Com
Please sign in to rate this answer.
Mohd Atif Husain 120 Reputation points

2024-05-06T13:58:24.7266667+00:00

Hi XinGuo-MSFT Thanks for sharing the details. This helps.
Next query what we have is around having another CMG connection point on another primary child site.
Situation- We are going to decommission one of our primary sites under CAS and new primary site is already commissioned. Current CMG connection point is installed on existing primary site whose site code for example ABC and new primary site code is DEF so do we need to promote a new CMG connection point at new primary site DEF and install all roles like MP, DP , SUP or can we migrate the existing CMG connection point ?
Scenario 2, if in case we want to manage clients on both new and existing primary sites can we do simultaneously use 2 CMG connection points? Reason is at some point of time we will be migrating clients from existing to new primary and would still need clients on both sides to be managed over internet.
Please suggest.

XinGuo-MSFT 14,851 Reputation points

2024-05-07T09:10:41.8933333+00:00

Hi,

Scenario 1:

I recommend you promote the new CMG connection point at new primary site DEF and install all roles like MP, DP , SUP.

Scenario 2:

You can create multiple CMG services in Azure, and you can create multiple CMG connection points. Multiple CMG connection points provide load balancing of client traffic from the CMG to the on-premises roles.

Mohd Atif Husain 120 Reputation points

2024-05-07T09:20:13.3133333+00:00

Hi XinGuo-MSFT, thanks for clarifying on scenario 1 and agree with you.

For Scenario 2, since the devices which are migrated to DEF site and since now will have DEF site code not ABC then in that case it should connect to new CMG connection point created at DEF site. Correct?

Rest other devices which are still at ABC, will be getting policies from CMG connection point at ABC.

XinGuo-MSFT 14,851 Reputation points

2024-05-15T09:37:19.4+00:00

For Scenario 2, before you deploy a new Virtual Machine Scale Set-based CMG, though, your existing Classic CMG must be decommissioned – you cannot deploy a Virtual Machine Scale Set CMG if you already have a Cloud Service (Classic) CMG in your subscription.
Sign in to comment

Share via

SCCM CMG - Classic to Virtual scale set

1 answer