Showing posts with label MEMCM. Show all posts
Showing posts with label MEMCM. Show all posts

Sunday, 28 November 2021

Convert CMG to virtual machine scale set

Starting in Configuration Manager version 2010, organizations with a Cloud Solution Provider (CSP) subscription could deploy the CMG with a virtual machine scale set (VMSS) in Azure. Starting in version 2107, all organizations can deploy a CMG with a virtual machine scale set. There is no longer a dependency on the subscription type. However, my favourite feature of Configuration Manager 2107 is that, if you have an existing CMG deployed with the classic cloud service, you can convert the CMG to use a virtual machine scale set. I did that conversion in my lab and it worked a treat.

Of course there are some rules:

  • You can change some settings when you convert to VMSS, for example size of VM, CRL check.
  • You cannot change other settings when you convert to VMSS, for example, Azure subscription, Azure AD app, Region, Resource group.
  • The CMG service name will change from cloudapp.net to yourregion.cloudapp.azure.com. You will have to re-configure the CNAME record.
  • If you don't change the CMG public name then you don't have to re-install the CMG Connection Point.

In the Configuration Manager console, navigate to the Administration workspace > Cloud Services, and select the Cloud Management Gateway node.


Select the classic CMG instance whose Status must be Ready. In the ribbon (or right click), select Convert. This action opens the Convert CMG wizard.


On the General page, select Next. As we said earlier, you can't change any of these settings.


On the Settings page, note the new Deployment name with the suffix for the virtual machine scale set (in my case that is GerryHCMG.westeurope.cloudapp.azure.com).

Make other configuration changes as needed. Then select Next and complete the wizard.


Click Next to finish the wizard and convert the CMG.


Monitor the conversion process in the CloudMgr.log file, the same way as a new deployment.

You will see the new Azure resources. See the Virtual Machine Set and Key Vault, for example. We didn't have these with the classic CMG implementation.

I hope this helps. Until next time....

Sunday, 26 September 2021

Upgrading ConfigMgr site to 2107 - console error

I encountered this weird console error this week while upgrading a ConfigMgr site to version 2107. The site was working perfectly.


The prerequisite check had passed with one warning. "Configuration Manager requires at least .NET version 4.6.2, but recommends the latest version 4.8. A later version of Configuration Manager will require .NET version 4.8". 

This was just a warning for now so I continued with the upgrade and chose "Ignore any prerequisite check warnings and install and install this upgrade regardless of missing requirements".


I navigated through the wizard until I got to this screen. We always have to accept the license terms, right?


However, no matter what I tried, I couldn't check that box. I kept getting the dreaded "Microsoft.ConfigurationManagement has stopped working" error. "A problem caused the program to stop working correctly.  Windows will close the program and notify you if a solution is available."

The only options were to close the program or click Debug.


Debug wasn't very helpful and complained about an unhandled .Net exception. Clicking OK just closed the console.

I'd like to say that I solved a complicated .Net issue in order to upgrade the site 😉😉. However the workaround was pretty straightforward. I had been running the upgrade wizard directly on the primary site server. Switching to a remote console did the trick.


I was able to check the offending box to accept the license terms.......


.....and continue with the wizard to upgrade the site.

I hope this helps someone else who encounters this issue.

Until next time....