Hotfix rollup KB30385346 released for CM2409 – fixes CMG issues amongst others…

[anyweb]

Introduction

Last month I posted about my CMG (Cloud Management Gateway) going AWOL (absent without leave) and staying broken, this was in response to a tweet from Panu, and I documented the sorry story here. I tried many things including the hotfix that was available at the time of posting, but nothing helped. My CMG remained broken and stayed in a state of disconnected. I had planned on removing it entirely and recreating the CMG but time got the better of me.

Today however I got a notification from Linkedin that someone had responded to one of my posts about that problem so I took a look.

Steven mentioned a hotfix rollup (HFRU) and it was a new one.

https://learn.microsoft.com/en-us/mem/configmgr/hotfix/2409/30385346

The issues fixed with this hotfix rollup are pasted from that article below, with the important CMG bits highlighted in bold italic:

Issues that are fixed

• Internet based clients using the alternate content provider are unable to download content from a cloud management gateway or cloud distribution point.

• Deployment or auto upgrade of cloud management gateways can fail due to an incorrect content download link.

• Internet based clients 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.
  Console

• [CCMHTTP] ERROR INFO: StatusCode=500 StatusText=CMGConnector_InternalServerError
  

• The Configuration Manager console displays an exception when you check the properties of a Machine Orchestration Group (MOG). Membership of the MOG can’t be modified; it must be deleted and recreated. The exception happens when the only computer added to a MOG doesn’t have the Configuration Manager client installed.

• 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.

• If a maintenance window is configured with Offset (days) value, it will fail to run on clients if the run date happens on the next month. Errors similar to the following are recorded in the UpdatesDeployment.log file.
  Console

• Failed to populate Servicewindow instance {GUID}, error 0x80070057
  

• 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 dbo.Logs table contains the following error.
  Console

• "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) ."
  

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

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

This gave me some hope so I powered up that lab and took a look. As you can see the hotfix rollup is ready to install.

Note: Yes I’m aware one of my app secrets is about to expire, that’s not part of this blog post or problem so I’ll ignore it for now.

Before installing the hotfix rollup however I checked on the status of my CMG. And to my great surprise after weeks (a month even) of being broken and disconnected it was now………. connected.

Uh… what ?

Ok, that’s weird. I ran the connection analyzer as well just for giggles, and for the first time in a long time it passed with flying colours.

As the server log files have unfortunately rolled over, I cannot see ‘when’ it self-fixed itself or whether that was on the backend (the CMG in Azure) or on the CM server itself. Just as a reminder, my now working CMG is in this state without me doing anything further after my original blog post, so it self fixed itself after many weeks of being broken.

Installing the hotfix rollup

To wrap things up, I decided I’ll install the hotfix rollup, to see what if anything it can do.

And after some time it was done, however as you can see I still have 2 Configuration Manager 2409’s listed (one was the early ring upgrade).

Well that’s it for this blog post, thanks Steven for the heads up on the hotfix rollup, however it didn’t resolve my issue, which seemed to solve itself prior to the rollup.