SCCM 2403 KB28204160 Hotfix Update Rollup

A new hotfix rollup KB28204160 for SCCM version 2403 has been released to address issues with CMG content downloads, collection management and policy processing delays, and SMS agent host service crashes.

Customers who installed the globally available 2403 release and those who opted in via a PowerShell script to the early update ring deployment are offered with the KB28204160 update. The fixes included in this hotfix will be part of the SCCM 2309 release.

The KB28204160 update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using the globally available build of version 2403. After the update is installed, a site reset will be started, but you do not need to restart your computer.

This guide covers the fixes included in the hotfix KB28204160 and describes the process for installing this update in SCCM 2403 environments.

Hotfixes included with KB28204160 update

The KB 28204160 hotfix includes the following previously released updates:

• KB 28290310: CMG update for Microsoft Configuration Manager version 2403
• KB 28458746: Software update management client fix for Microsoft Configuration Manager version 2403
• KB 29166583: Management point security update for Microsoft Configuration Manager version 2403

Take a list of all the hotfixes and updates released for Configuration Manager.

Issues that are fixed hotfix KB28204160

Installing the KB28204160 hotfix resolves the following issues for your Configuration Manager 2403.

• The SMS Agent Host service (ccmexec.exe) terminates unexpectedly when downloading content from a cloud-based source.
• Collection management and policy processing might take longer than expected. The following message is recorded in the policypv.log file: ~++++ProcessPolicyChanges: Waiting for exec spProcessPolicyChanges 1 to complete.
• A timing issue can still cause a double reboot to break a task sequence despite setting the SMSTSWaitForSecondReboot variable.
• Temporary files used on management points and cloud management gateway (CMG) systems are now precompiled and signed to prevent false positives from security or code integrity scanners.
• The content download from a cloud management gateway to a client can fail after updating to Configuration Manager current branch, version 2403. This is more common when BranchCache is enabled and boundary groups are used. Errors resembling the following are recorded in the DataTransferService.log file: GetDirectoryList_HTTP Error sending DAV request. HTTP code 500, status ‘Internal Server Error‘.

These fixes are based on the notes for Microsoft hotfix 28204160.

Installing SCCM 2403 KB28204160 Hotfix Update Rollup

• Launch the Configuration Manager console on the server.
• Navigate to Administration\Overview\Updates and Servicing.
• Select Configuration Manager 2403 Hotfix Rollup KB28204160 update and in the top ribbon, select Install Update Pack.

The hotfix includes the updates for the site server, clients, and console. For prerequisite warnings, you can enable the option “Ignore any prerequisite check warnings and install the update” on your production server running version 2403. Click Next.

Choose the client update option and select Next.

Accept the license terms for installing the KB28204160 update and click Next.

On the Completion page, click Close.

While the hotfix is being installed, you can monitor its installation by reviewing the cmupdate.log file. Additionally, Monitoring Workspace in the Configuration Manager console allows you to track the progress of a hotfix installation.

In my lab, the hotfix KB28204160 completed its installation in 25 minutes and I did not encounter any errors during the installation. The KB28204160 hotfix updates the Configuration Manager console to version 5.2403.1171.2400 and the client version to 5.0.9128.1030. You can auto-upgrade the client agents to the latest version.

Install KB28204160 on Secondary Sites

After you’ve installed the hotfix rollup update KB28204160 on a primary site, pre-existing secondary sites must be manually updated. Read more about secondary site installation in SCCM to get an idea of how to install secondary sites in SCCM.

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.