Running two CMGs at the same time

Question

Dear Team,

We have an existing CMG with classic method installed on CAS and serving the clients with 1 CMG connection point configured at one of the primary sites.

Plan - Since CMG classic deployment is deprecated and its support will end on 31st August 2024, we are planning to create another CMG with Virtual machine scale set deployment. Along with that another connection point at a new primary site in the hierarchy.

What could be the best approach or method to let the clients know to which CMG connection point they need to connect? In our case, for some time we want some clients to serve with existing CMG connection point and will be migrating phase wise these clients to report to new primary site. In that case, clients will be on older and new primary site as well as CMG. How to manage them from both the sides? Please suggest.

Answer 1

Hi,

Migrating SCCM agents to a new Cloud Management Gateway (CMG) involves a few steps:

• Create a New CMG: Deploy a new CMG as a Virtual Machine Scale Set with the new certificate.
• Wait for Policy Refresh: Wait for a couple of weeks to ensure all endpoints are aware of the new CMG.
• Remove the Old CMG: Once all clients are aware of the new CMG, you can remove the old CMG from the SCCM console.
• Migrate Objects: You must migrate the objects that are associated with the client.
• Reinstall or Reassign Clients: After migrating the objects, you must then reinstall or reassign the clients from the source hierarchy to the destination hierarchy.

Remember, it’s important to thoroughly test the new CMG in a controlled environment before starting the migration. This will help you identify and resolve any potential issues before they affect your production environment. Good luck with your migration! 😊

How To Convert Your Cloud Management Gateway to a Virtual Machine Scale Set

https://model-technology.com/blog/how-to-convert-your-cloud-management-gateway-to-a-virtual-machine-scale-set/