Offline feedback update for Microsoft Configuration Manager versions 2409, 2503, and 2509

Applies to: Configuration Manager (current branch, versions 2409, 2503, and 2509)

Prerequisites

To apply this hotfix, you must be using Configuration Manager, versions 2409 (with Update rollup 30385346) versions 2503 (with Update rollup 32851084 installed) and 2509.

2409: Update rollup for Microsoft Configuration Manager version 2409

2503: Update rollup for Microsoft Configuration Manager version 2503

Summary of Changes

To improve security and reliability, feedback for ConfigMgr Manager will require authentication. Starting 26 June 2026, Feedback will no longer accept unauthenticated requests.

With this change, there is a known issue that the standalone tool UploadOfflineFeedback.exe won't work, this will be fixed in next release, but you can still use other embedded UX to send feedback from Product feedback - Configuration Manager | Microsoft Learn or Feedback Hub to send feedback.

Restart information

This update doesn't initiate a site reset after installation.

Update replacement information

This update doesn't replace any previously released update.

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.