Coordinator is unable to connect to SQL using a gMSA account after applying Microsoft patches KB5022289\KB5022286 (4370034)

If you have configured Change Auditor to use a gMSA account for the connection to the SQL server, the Coordinator may fail to connect to SQL and the Coordinator service will stop after applying Microsoft patches. The Coordinator is unable to connect to SQL using a gMSA account after applying Microsoft patches KB5022289\KB5022286 to the Coordinator server. Errors similar to the following may be logged in the Coordinator logs:

2023-01-24 05:35:38.221 [24][DEBUG][Quest.Sys.Impersonator+LogonUserDataCache.AcquireValueOf(0)] LogonUserEx() - gMSA account detected: <gMSAAccountName>$
2023-01-24 05:35:38.221 [24][DEBUG][Quest.Sys.Impersonator+LogonUserDataCache.AcquireValueOf(0)] LogonUserEx() failed, error: 1367
2023-01-24 05:35:38.221 [24][ERROR][ChangeAuditor.Coordinator.Service.Initialize(0)] Database initialization not successful on <CADBName>.

A logon request contained an invalid logon type value
2023-01-24 05:35:38.221 [24][DEBUG][ChangeAuditor.Coordinator.Service.Initialize(0)] System.ComponentModel.Win32Exception (0x80004005): A logon request contained an invalid logon type value
2023-01-24 05:35:38.221 [24][INFO][ChangeAuditor.Service.Service.OnStop(0)] **** Service Stop
2023-01-24 05:35:38.221 [24][INFO][Quest.ChangeAuditor.WebServices.EventWebhookService.OnServiceStopping(0)] Service stopping
2023-01-24 05:35:38.221 [24][INFO][ChangeAuditor.Service.Service.CurrentDomainUnhandledException(0)] Unhandled exception caught in Service
2023-01-24 05:35:38.221 [24][ERROR][ChangeAuditor.Service.Service.CurrentDomainUnhandledException(0)] Object reference not set to an instance of an object.

In addition, if you are using a gMSA account with Foreign Forest agents, the agents will not be able to authenticate to the Coordinator after applying KB5022289\KB5022286 to the agent machines. When the agent cannot connect to the Coordinator it will shutdown.