SOLVED CMG state stuck in "Stopping"

[SomeSCCMGuy]

I recently upgraded SCCM from 2303 to 2403 and then applied the hotfix rollup. Since upgrade, the CMG service status shows "Stopping" and had been stuck there for a week. I've tried numerous things from online but nothing has worked. I've checked certs, refreshed tokens, rebooted SCCM and CMG VMSS several times, removed and reloaded the Cloud Distribution Point role. Only thing I can possibly find from logs is maybe a cert/token issue somewhere. Basically, SCCM reports being in one state while CMG says another. I'm afraid the only option is build a new CMG. I can post logs if needed...

One of the errors from analyzer: "Current service state is 'Stopping', cannot stop service."
Another message: State of the CMG service is '5'

Appreciate any help.

 

[SomeSCCMGuy]

I recently upgraded SCCM from 2303 to 2403 and then applied the hotfix rollup. Since upgrade, the CMG service status shows "Stopping" and had been stuck there for a week. I've tried numerous things from online but nothing has worked. I've checked certs, refreshed tokens, rebooted SCCM and CMG VMSS several times, removed and reloaded the Cloud Distribution Point role. Only thing I can possibly find from logs is maybe a cert/token issue somewhere. Basically, SCCM reports being in one state while CMG says another. I'm afraid the only option is build a new CMG. I can post logs if needed...

One of the errors from analyzer: "Current service state is 'Stopping', cannot stop service."
Another message: State of the CMG service is '5'

Appreciate any help.

Well, I had a support tech jump in and help us out on this and today we found that when upgrading from 2303 to 2403, the .NET prerequisite just presents a warning and is not required to move forward. However, it is a requirement for 2403. The prereq checker allowed the upgrade to continue. We found a MS article that explains this and the fix is to install .NET 4.8 on the site server(s). Once this was installed and server rebooted, CMG begin communicating with SCCM again and began updating.