Microsoft has released KB30833053 hotfix for SCCM version 2409. This hotfix resolves the issue where the new cloud management gateways (CMGs) fail to install after updating to Configuration Manager version 2409.
KB30833053 is the first hotfix released for ConfigMgr version 2409 and it is available for all the customers globally. Installing this update doesn’t require a computer restart or a site reset after installation.
This update is available in the Updates and Servicing node of the Configuration Manager console for version 2409 environments. The hotfix KB30833053 contains only site server upgrades. There is no client update or console update required after installing this hotfix. So the version numbers for console and client will remain the same.
Issues fixed in KB30833053
After updating to version 2409, new cloud management gateways (CMGs) failed to install. The following errors were logged in the CloudMgr.log file (referenced from MS hotfix documentation):
ERROR: Exception occurred for service <ServiceName> : System.AggregateException: One or more errors occurred.
Azure.RequestFailedException: At least one resource deployment operation failed. ErrorCode: DeploymentFailed~~~~Service request succeeded.
Response content and headers are not included to avoid logging sensitive data.
The Azure activity logs for Virtual Machine Scale Sets or the resource group included the following error information about CMG.
"statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"VMExtensionProvisioningError\",\"target\":\"0\",\"message\":\"VM has reported a failure when processing extension 'InstallCMG' (publisher 'Microsoft.Compute' and type 'CustomScriptExtension'). Error message: 'Command execution finished, but failed because it returned a non-zero exit code of: '1''. More information on troubleshooting is available at https://aka.ms/VMExtensionCSEWindowsTroubleshoot. \"}]}}"
The Microsoft ConfigMgr team has worked on these issues and released the KB30833053 update for customers who are experiencing CMG installation failures. If you are experiencing the issues listed above in your setup, then this hotfix is for you.
You may skip installing this update if you aren’t using CMG in your setup. From my past experiences, the issues covered in this hotfix will be included in the next update for 2409.
Installing Hotfix KB30833053 for Configuration Manager 2409
Launch the Configuration Manager console on the server. Navigate to Administration\Overview\Updates and Servicing. Right-click Configuration Manager 2409 Hotfix KB30833053 and select Install Update Pack.

It is highly recommended that you run a prerequisite check for this update on your production server before installing it. For lab environments, you can enable the option “Ignore any prerequisite check warnings and install the update.” Click Next.

Accept the license terms for installing the hotfix update KB30833053.

Close the Configuration Manager updates wizard. The KB30833053 update installation begins now.

Monitoring the Hotfix Installation
The hotfix KB30833053 update required a total of just 10 minutes to install on the 2409 server, and there were no errors encountered at any point in the installation process.
Remember that this hotfix is a very tiny update and there won’t be an SCCM site reset occurring after the installation of the hotfix. You don’t have to restart your server after the installation of this update.
To verify if the KB30833053 update is installed, open the console and go to Administration > Updates and Servicing. If the State column for the hotfix shows Installed, it means the update installation is completed.

Updating Secondary Sites with KB30833053 Hotfix
After you install the KB30833053 update on a primary site, pre-existing secondary sites must be manually updated.
To update a secondary site in the Configuration Manager console, select Administration > Site Configuration > Sites > Recover Secondary Site, and then select the secondary site.

Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:
select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
- If the value 1 is returned, the site is up-to-date, with all the hotfixes applied on its parent primary site.
- If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.
Still Need Help?
If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.