I wrote a blog post to highlight the process of creating a Cloud Management Gateway with virtual machine scale set but what if you are already running a classic cloud CMG?
Well from ConfigMgr 2107 you can convert to virtual machine scale set. You’ll need to register Microsoft.KeyVault, Microsoft.Compute and Microsoft.Network beforehand. Info on where to do that is in that previous post.
Note that when you convert the CMG you can change the following settings:
- VM size
- VM instances
- Verify CRL
- Require TLS
- Serve content
You cannot change the following settings:
- Azure environment
- Azure AD app
- Resource group
Converting to Virtual Machine Scale Set
To convert the CMG, right click your cloud management gateway in the ConfigMgr console and choose Convert.
The Convert Cloud Management Wizard will appear. Click Next as you can’t alter anything here.
On the Settings page you can change the specific configuration as highlighted in the list previously. I’m going to stick with the defaults here. Click through the wizard to completion.
Keep an eye on the CloudMgr log file for details of the conversion.
You will notice that the CMG Deployment Model now reports as Virtual machine scale set.
When the deployment completes the CMG will be in a ready state but the connector will be Disconnected.
If you take a look at the SMS_CLOUD_PROXYCONNECTOR log file, you’ll see an issue with connection the CMG.
At this stage, you’ll need to make a CNAME record change.
As per the previous blog post:
Now we need to map to the region your CMG will be deployed to plus cloudapp.azure.com. You’ll be given some details on this when you run through the CMG wizard, but as an example I will need to map – memcmggateway.sccmsolutions.co.uk to memcmggateway.eastus.cloudapp.azure.com with my external DNS provider as a CNAME record.
With the external CNAME record updated accordingly, the connection was made.
A quick check with the Connection Analyzer confirms all is good.
For some more tips on modifying a CMG instance, take a look at the official MS docs here.