chrisj76
Member
- Messages
- 20
- Reaction score
- 0
- Points
- 1
Configuration Manager (current branch, version 2309)
Background
Microsoft send an email saying workloads are running on images that have be deprecated and we needed to upgrade.
After much research there was nothing about upgrading CMG Image for 2309 as all the hotfix where for 2403 and above so was left with using the vmss rolling-upgrade via Azure option.
As due to some limiting system requirements we could not upgrade yet to a new version.
After the upgrade was completed the provision failed.
Failed to start virtual machine scale set
Failed to start virtual machine scale set 'x'. Error: VM has reported a failure when processing extension 'Microsoft.Powershell.DSC' (publisher 'Microsoft.Powershell' and type 'DSC'). Error message: 'The DSC Extension failed to install: Error downloading https://x.blob.core.windows.net/stageartifacts/dsc/cmgdsc.zip after 2 attempts: . More information about the failure can be found in the logs located under 'C:\WindowsAzure\Logs\Plugins\Microsoft.Powershell.DSC\2.83.5' on the VM. To retry install, please remove the extension from the VM first. '. More information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot.
What we have found it the token it is trying to use to access the blob storage Expiry [Tue, 09 Apr 2024 12:33:41 GMT] when we did the around the time we upgrade to 2309.
We are trying to reach out to Microsoft Support for help.
Would have been helpful for Microsoft not to send the about email and if we had seen this in the FAQ for CMG before hand
Look to see if anyone has some suggestions.
Options we are considering.
1. Deploy a 2nd VM Instance for the CMG. Then once the SQL Server has been upgraded (which is holding back the upgrade to the 2409) we upgrade to 2409 deploy the hotfix to see if that fixes the VMSS and then go back to 1 VM instance for the CMG.
2. Delete the CMG - the issue we are worried about are not been able to get the same service name again, Internet-based clients can't communicate with a removed CMG.
3. Deploy a Temp CMG wait for all 24 hours for the Internet-based clients to refresh the policy then delete the current CMG and recreate. Again worried about are not been able to get the same service name again.
Background
Microsoft send an email saying workloads are running on images that have be deprecated and we needed to upgrade.
After much research there was nothing about upgrading CMG Image for 2309 as all the hotfix where for 2403 and above so was left with using the vmss rolling-upgrade via Azure option.
As due to some limiting system requirements we could not upgrade yet to a new version.
After the upgrade was completed the provision failed.
Failed to start virtual machine scale set
Failed to start virtual machine scale set 'x'. Error: VM has reported a failure when processing extension 'Microsoft.Powershell.DSC' (publisher 'Microsoft.Powershell' and type 'DSC'). Error message: 'The DSC Extension failed to install: Error downloading https://x.blob.core.windows.net/stageartifacts/dsc/cmgdsc.zip after 2 attempts: . More information about the failure can be found in the logs located under 'C:\WindowsAzure\Logs\Plugins\Microsoft.Powershell.DSC\2.83.5' on the VM. To retry install, please remove the extension from the VM first. '. More information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot.
What we have found it the token it is trying to use to access the blob storage Expiry [Tue, 09 Apr 2024 12:33:41 GMT] when we did the around the time we upgrade to 2309.
We are trying to reach out to Microsoft Support for help.
Would have been helpful for Microsoft not to send the about email and if we had seen this in the FAQ for CMG before hand
CMG FAQ - Configuration Manager
Use this article to answer frequently asked questions about the cloud management gateway (CMG).
learn.microsoft.com
Do I need to update the Virtual machine if the image is deprecated?
No. The CMG VM's are deployed using template and IIS are configured, this will be broken if you manually update the VM's. Product group will fix the issue through update or the current branch releases.Look to see if anyone has some suggestions.
Options we are considering.
1. Deploy a 2nd VM Instance for the CMG. Then once the SQL Server has been upgraded (which is holding back the upgrade to the 2409) we upgrade to 2409 deploy the hotfix to see if that fixes the VMSS and then go back to 1 VM instance for the CMG.
2. Delete the CMG - the issue we are worried about are not been able to get the same service name again, Internet-based clients can't communicate with a removed CMG.
3. Deploy a Temp CMG wait for all 24 hours for the Internet-based clients to refresh the policy then delete the current CMG and recreate. Again worried about are not been able to get the same service name again.
