![]() ![]() Once you click Convert, you will be presented with the wizard which allows you to make changes to the CMG. If the feature to create a Virtual Machine Scale Set CMG is enabled, the CMG has a configuration that is not supported, or there is something wrong with the CMG that is keeping it out of the Ready state, skip down to the “What if Your CMG can’t be Converted” section of this post. You can do that from the Updates and Servicing > Features node within the MECM console. If the Convert option does not appear, verify that the Cloud management gateway with Azure VM scale set feature is enabled. As long as your Classic CMG’s Service Name does not have a “” suffix and the CMG is in a Ready state, you will see the Convert option in the context menu when you right click the CMG in the MECM console. ![]() ![]() Now comes the fun part – converting the CMG. If not all of the necessary providers have been registered, follow these steps from Microsoft to configure them before proceeding. Once there, click on the Resource Providers option within the Settings menu to verify that all four of these Resource Providers are registered. To ensure these have been registered in your Azure environment, go to the Azure portal, open the Subscriptions page, and select the subscription in which your CMG is deployed. If they are not already registered, they need to be registered before converting your Classic CMG. Hop down to the “What if the CMG can’t be Converted?” section below for more information.īeyond that, there are four Azure Resource Providers which need to be registered within the subscription where you have your CMG running. If yours was not, though, then you will be unable to convert your CMG. Most organizations will have configured their own domain suffix in the Service Name during the initial CMG deployment and thus will be fully able to convert their Classic CMG to a new CMG. CMG Prerequisites for Conversionīefore you convert your existing Classic CMG, you need to make sure that you have the proper prerequisites in place.įirst, the big obstacle – in order for a Classic CMG to be eligible for conversion, it needs to have been originally configured with a Service Name using a custom domain suffix (most likely your organizational domain suffix) rather than using the default “” suffix. So, it is time to start getting those CMGs updated to the latest and greatest technology. If you do have a Classic CMG in your environment today, you have a limited amount of time to upgrade it before it stops working – any Cloud Service (Classic) resources, including Classic CMGs, will no longer function after August 31, 2024. The only remaining option for building a CMG is the Virtual Machine Scale Set, so if you haven’t deployed a CMG yet and are on Current Branch version 2203 or newer, then you can move forward with your CMG deployment without concern for migration from legacy Classic resources. It is important to note that, as of Current Branch version 2203 of MECM, the option to create a CMG using Cloud Service (Classic) has been removed. Critical Dates for Microsoft’s CMG Transition ![]() This post intends to provide further information about the timeline for migrating legacy Classic CMGs and walk through the process for using the Convert wizard to convert to a Virtual Machine Scale Set CMG. Aside from those scenarios, the Convert wizard provides an easy tool to convert a Classic CMG to a Virtual Machine Scale Set CMG. There are some caveats, however – if you are planning on changing the Azure AD App used to manage the CMG, or you want to move the CMG to a new Azure environment, Subscription, Region, or Resource Group, a new CMG will need to be created instead of converting the legacy CMG. The Convert wizard has very few requirements and is very adept at creating a Virtual Machine Scale Set and migrating an existing Classic CMG to a Virtual Machine Scale Set. To assist with this transition, a new feature has been provided, known simply as Convert. Now, nearly a year later, Microsoft has announced the timeline for the end of Classic CMG support, while also providing a path for customers to migrate from Classic CMGs to Virtual Machine Scale Set-based CMGs. No longer was there a requirement to use any Classic resources, though the legacy Classic CMGs were still supported. Starting in Microsoft Endpoint Configuration Manager 2107, Microsoft introduced the ability to deploy a CMG using Azure Resource Manager resources, specifically through the usage of a Virtual Machine Scale Set. Since then, Microsoft has been further deprecating the Classic Azure Service Manager resources in favor of the improved Azure Resource Manager resource model, so it was only a matter of time until CMGs based in the Classic model would need to be upgraded or replaced. When Microsoft introduced the Cloud Management Gateway (CMG) for Microsoft Endpoint Configuration Manager (MECM), there was only one supported deployment method – to use Cloud Service (Classic) resource. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |