Can SCCM CMG support client which is migrated to another new site

Mohd Atif Husain 145

Dear Team,

Our current SCCM CMG classic supports clients which are managing from one of the primary site servers. However, we have a plan to migrate these clients to another new primary server with a different site code.

Query - Will our internet clients would still be able to connect to existing CMG and get the policies and content from the CMG connection Point? Please share your expertise here.

Rahul Jindal [MVP] 9,551 Reputation points MVP

2024-07-05T06:32:42.64+00:00

If the clients have already been moved to the new PRI, then the existing CMG is of no use. This is because the existing CMG will route the traffic to existing PRI site server which will fail as the clients would have moved to new site and will expect to call in for the same. You can probably setup a new cmg instance in the old PRI, let the clients learn about it and then move the new CMG instance to the new PRI with a new connection point. For this to work, you will need to import the client and server app manually. I haven’t tried this, but in theory it should work as for the clients the CMG instance remains the same.
Mohd Atif Husain 145 Reputation points

2024-07-05T07:02:40.1666667+00:00

Hi @Rahul Jindal [MVP]

Thanks for sharing your valuable thoughts.

We are trying to do in the same way, so we had created the new web app and native app manually in Azure and when trying to import into SCCM it is saying "Tenant already exists". Which looks like it is not allowing to create new apps since existing APPS are there and used by existing CMG Classic.

Plan is something like this, create new APPS with new CMG VMSS since classic is deprecated then migrate the clients from old to new PRI. Setting up the new CMG connection Point in new PRI site.

Please help in getting this understand.
Rahul Jindal [MVP] 9,551 Reputation points MVP

2024-07-05T07:21:56.6866667+00:00

Where will the new cmg instance be created? In my opinion it should be done in the existing PRI and later you point the instance client and server app in the cmg instance you create in new PRI. However, if this is a case of ConfigMgr site upgrade and as part of that, you are migrating to the new site, then you can also look at leveraging migration jobs to migrate objects from existing PRI to new and do a backup and restore. That should take care of moving CMG instance as well and will save you some time from performing a bunch of manual steps.
Mohd Atif Husain 145 Reputation points

2024-07-05T07:35:57.7266667+00:00

Thanks a lot again @Rahul Jindal [MVP]

Answer of query- Where will the new cmg instance be created? New CMG VMSS we are creating at CAS where existing CMG Classic is also created.

It is not part of Config Mgr. site upgrade however let me give you a brief idea about what we are doing.

Plan-In current SCCM hierarchy we have 1 CAS and 2 primary site which are running on EOL OS version. We have created a new PRI site under same hierarchy and now migrating the clients from existing to new PRI site under same hierarchy. As we know CMG Classic is also deprecated so we are trying to create new APPS with new CMG VMSS and later point once all clients are migrated to new PRI then we will create the new CMG connection point to point the migrated clients to new PRI.

Do you see any technical challenges in our plan?

Issue- We have created the new APPS in Azure already but when we are importing them it is saying Tenant already exists.

How can we use the new APPS for new CMG VMSS that's the challenge now?

Hope I am able to make you understand of current issue and plan.
Rahul Jindal [MVP] 9,551 Reputation points MVP

2024-07-05T07:40:32.7833333+00:00

Aah CAS changes a few things, but the clients will still need to be made aware of the new PRI and CMG instance. However, if your existing PRI has an OS that supports in place upgrade, then you can easily do that as in-place upgrade is the recommended way to upgrade the ConfigMgr site servers.
Mohd Atif Husain 145 Reputation points

2024-07-05T09:54:22.8966667+00:00

Hi @Rahul Jindal [MVP]

Thank you so much for your responses.

Do you think the above error we are getting due to existing web app and native client, and we cannot create new APPS for new CMG?

With respect to in-place upgrade- Let me tell you Sir we have completed the in-place OS upgrade for CAS and 1 primary site however second primary site which is supporting more than 20K clients is something had been more critical, so we had added new PRI site to migrate these clients this way.

Challange we are facing with creating new web and native app. Is there any best possible way to deal with this scenario? Any suggestions would be really appreciated.
Rahul Jindal [MVP] 9,551 Reputation points MVP

2024-07-05T10:37:08.0766667+00:00

How were the server and client apps created? When setting by CMG, you get asked whether to import the apps. Are you getting the error on importing the apps? Have you checked smsadmin ui log to get further details?
Mohd Atif Husain 145 Reputation points

2024-07-05T10:57:02.4+00:00

First, we had tried creating the server and client apps from SCCM Console using the Azure services node and it gives the error "Tenant already exists."

Then we have followed the manual method of creating these apps from Azure. Once we had done creating the new APPS. We visited the console again and this time we tried to import the created apps by putting all the details. Right after this, "Tenant already exists" message has come up.

Yes, did checked the smsadmin UI log and it has generated only one single error which we faced for Invalid secret key provided `but that also gone when we fix that issue. Only error which is continuously coming with both automatic and manual method of creating these APPS is Tenant already exists".

1 answer

XinGuo-MSFT 15,781 Reputation points

2024-07-04T01:40:39.0466667+00:00

Hi,

When you migrate clients to a new primary server with a different site code, you will indeed need to create a new Cloud Management Gateway (CMG) associated with the new site hierarchy. As the clients connect to the site (either on-premises or via the CMG), they will learn about the new CMG and will start to randomly select between the two.

Once you are confident that all clients have connected and thus learned about the new CMG, you can decommission the old CMG. From that point forward, clients will only be able to use the new CMG and will learn that the old CMG no longer exists, which will stop them from attempting to connect to it.

https://video2.skills-academy.com/en-us/mem/configmgr/core/clients/manage/cmg/plan-hierarchy-design#multiple-environments

This process ensures a smooth transition with minimal disruption to the clients. However, as always, it’s recommended to test this process with a small group of clients before implementing it across all clients. This way, you can identify and address any potential issues early on.

I hope this clarifies your query. If you have any more questions or need further clarification, feel free to ask! 😊
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

Can SCCM CMG support client which is migrated to another new site

1 answer