KB30385346 Hotfix Rollup for SCCM 2409

Microsoft has released the KB30385346 hotfix rollup for SCCM 2409. This update resolves about 9 issues, mostly related to CMG content downloads, ccmexec crashing, hardware inventory stuck, and the ConfigMgr console terminating unexpectedly.

After the release of Configuration Manager version 2409, Microsoft released the first hotfix, KB30833053, which addressed the issues related to new CMG installations. KB30385346 is a second hotfix rollup update for version 2409 that supersedes the previously released KB30833053.

If you have not installed any hotfixes for version 2409 yet and see both KB 30833053 and KB 30385346 appear in the console, apply the KB30385346 hotfix. That is because the KB30385346 update includes all the fixes included in hotfix KB30833053.

Most importantly, the update rollup KB 30385346 is an important update containing several fixes, and it should be available for all the customers globally. Take a look at all the hotfixes and OOB updates released for the ConfigMgr CB versions.

Issues fixed in KB30385346

As per the Microsoft article, the following issues are resolved in the KB 30385346 hotfix:

1. Clients using the alternate content provider on the Internet are unable to download content from a cloud management gateway or cloud distribution point.

2. An incorrect content download link can cause deployment or upgrade of cloud management gateways to fail due to an incorrect content download link.

3. Clients using the Internet can fail to communicate with a management point. The failure happens if the SMS Agent Host service (ccmexec.exe) on the management point terminates unexpectedly. Errors similar to the following are recorded in the LocationServices.log file on the clients. The LocationServices.log contains the error: [CCMHTTP] ERROR INFO: StatusCode=500 StatusText=CMGConnector_InternalServerError.

4. The Configuration Manager console displays an exception when you check the properties of a Machine Orchestration Group (MOG). The members of the MOG cannot be changed; they must be deleted and recreated.

5. Hardware inventory collection on a client gets stuck in a loop if the SMS_Processor WMI class is enabled, and the processor has more than 128 logical processors per core.

6. If a maintenance window is configured with an Offset (days) value, it will fail to run on clients if the run date is next month. The error logged in the UpdatesDeployment.log file is Failed to populate Servicewindow instance {GUID}, error 0x80070057.

7. The spCleanupSideTable stored procedure fails to run and generates exceptions on Configuration Manager sites using SQL Server 2019 when recent SQL cumulative updates are applied. The following errors are logged in dbo.Logs.

"ERROR 6522, Level 16, State 1, Procedure spCleanupSideTable, Line 0, Message: A .NET Framework error occurred during execution of user-defined routine or aggregate "spCleanupSideTable": System.FormatException: Input string was not in a correct format. System.FormatException: at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt64(String value, NumberStyles options, NumberFormatInfo numfmt) at Microsoft.SystemsManagementServer.SQLCLR.ChangeTracking.CleanupSideTable(String tableToClean, SqlInt64& rowsDeleted) ."

8. Multiple URLs are updated to handle a back-end change to the content delivery network used for downloading Configuration Manager components and updates.

9. The Configuration Manager console can terminate unexpectedly if a dialog contains the search field.

Install KB30385346 Hotfix Rollup for SCCM 2409

Launch the Configuration Manager console on the server. Navigate to Administration\Overview\Updates and Servicing. Right-click Configuration Manager 2409 Hotfix Update Rollup (KB30385346) 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.

Choose the client update option and select Next.

Accept the license terms for installing the hotfix rollup KB30385346. Click Next.

Review the hotfix configurations on the Summary page and click Next. Close the Configuration Manager updates wizard. The KB30385346 rollup installation begins now.

Monitoring the Hotfix KB30385346 Installation

While the hotfix installation is in progress, you can navigate to Monitoring\Overview\Updates and Servicing Status to see the detailed installation status for the update. If the hotfix fails to install, this section will show you the exact step where the update failed. Another way to track the hotfix installation is by reviewing the cmupdate.log file.

The hotfix KB30385346 update required a total of 15 minutes to install on the 2409 server, and there were no errors encountered at any point in the installation process. You don’t have to restart your server after the installation of this update.

Console Upgrade

The KB30385346 hotfix rollup upgrades the Configuration Manager console to version 5.2409.1183.1400. To upgrade the console, click on Install the new console version and complete the upgrade procedure.

Tip: During the console upgrade, review the console admin upgrade log files in case you encounter any errors.

To verify if the KB30385346 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.

Please note that when you install the KB30385346 hotfix, the KB30833053 hotfix disappears from the console.

Upgrading Clients

Installing the KB30385346 hotfix updates the client agent version to 5.0.9132.1023. You must upgrade the client agents to the latest version. For more help on upgrading the clients, refer to the guide SCCM client upgrade options.

Updating KB30385346 on Secondary Sites

After you’ve installed the hotfix rollup update KB30385346 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.