Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: Configuration Manager (current branch, versions 2409 and 2503)
Summary of KB35958849
An update is available to resolve the following issue for Configuration Manager customers using the cloud management gateway component.
- The Create or Update Public IP Address deployment maintenance task for a cloud management gateway (CMG) fails every 20 minutes. This issue happens if the subscription is created in a region with Availability Zones, and can also happen during a CMG upgrade.
Errors similar to the following are recorded in the CloudMgr.log file.
Resource Manager - Creating Public IP Address {CMG_Name} with deployment CreatePublicIPAddress{GUID}
ERROR: Exception occured for service {CMG_Name} : System.AggregateException: One or more errors occurred.
STATMSG: ID=9418...
STATMSG: ID=9401...
Update information for Microsoft Configuration Manager current branch
This update is available in the Updates and Servicing node of the Configuration Manager console for versions 2409 and 2503. Note that the changes are only applicable in environments using a cloud management gateway that have either of the following update rollups installed.
- KB 32851084: Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2409
- KB 32851084: Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2503
Restart information
This update doesn't require a computer restart or a site reset after installation.
Additional installation information
After you install this update on a primary site, preexisting 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. The primary site then reinstalls that secondary site by using the updated files. This reinstallation doesn't affect configurations and settings for the secondary site. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
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, all the fixes that are applied to the primary site aren't installed for the secondary site. You should use the Recover Secondary Site option to update the secondary site.
File information
File information is available in the following downloadable text files.
Release history
- December 3, 2025: Initial hotfix release