There is no direct migration path for this. You simply implement a new VMSS-based CMG that sits side by side with the old/existing CMG. Clients will learn about the new CMG as they connect to the site (on-prem or via the CMG) and will begin to randomly pick between the two. Once you are comfortable that all clients have connected and thus learned about the new CMG, you can decommission the old CMG. Clients will then only be able to use the CMG (if they attempt to connect to the old one, this will fail and they will then use the new one) and will learn that the old CMG no longer exists and will stop attempting to connect to it.
Migrating SCCM CMG from Cloud Service Classic to VMSS on another Azure subscription
I want to migrate my Cloud Management Gateway from Cloud Service Classic to Virtual Machine Scale Sets (VMSS) on another Azure subscription. However, I cannot find a suitable solution online.
Can someone provide the best way to do this? Do I need to delete my current CMG and set up a new one as VMSS?
Thank you.
- @Jason Sandys I know you are the expert here, please can you assist :) ?
2 answers
Sort by: Most helpful
-
Jason Sandys 31,286 Reputation points Microsoft Employee
2024-04-26T18:36:44.63+00:00 -
Adam McKnight 0 Reputation points
2024-08-22T12:28:34.6966667+00:00 Sorry but he is wrong. You have to be a certain version per MS. 2107 I think is the last version that could have 2 CMG's on the same system. My SCCM Env is on 2303 and does not support duel CMG's. I spent and entire year planning around this assumption to only get on a call for 2 hours and then told I was not able to due to the version of SCCM I'm on. Also just so you know 2309 is that last version that will support classic. MS at this time has no solution other than deleting the Classic CMG and rebuilding and Virtual Set CMG. I have over 8 Terabytes of data on my CMG without any steps being supplied to move the data. Only option I can see it to redeploy all of my applications to the new CMG. Microsoft should check the facts before telling people the wrong information.
Thanks
Adam