Azure Update does not reboot

Wai Lam 0

Have a Azure maintenance configuration for a few Windows VMs (2019/22), and have it set to require a reboot for patches. Some VM's don't reboot after the patches finish, while most do. This week it was 2 VMs (out of 8) that didn't reboot. I waited about 30 mins+ since the completion of the patch finishing before signing into it to manually do it. Does anyone have any idea how to fix this or what the cause could be? Sconfig is set to manual and patch orchestration is correctly applied in Azure (as others under the same plan reboot fine). I tried looking Azure logs, but cant find anything in them that's been helpful.

1 answer

JimmySalian-2011 41,916 Reputation points

2023-05-21T11:24:37.25+00:00

Hi,

Can you check the event logs on the VMs and is it a schedule update process using Azure Update Automation?Check some of the troubleshooting steps over here and if that does not help try contacting MS Support - https://learn.microsoft.com/en-us/azure/automation/troubleshoot/update-management

https://twitter.com/azuresupport

==

Please Accept the answer if the information helped you. This will help us and others in the community as well.
Please sign in to rate this answer.
Wai Lam 0 Reputation points

2023-05-21T21:53:33.9233333+00:00

Hi,

I do not use the Update Automation, I use the Azure Update Management Center. I don't have trouble patching at all, as it shows under History (in Azure Update Management Center) that patches are installed. For those patches to be applied, it needs a reboot, so I enforce a reboot within the maintenance configuration (which originally triggered the update). There are 8 VMs under this maintenance configuration, and 2 of them this week didn't reboot after patching (been a reoccurring problem, but unsure if its been these same servers). Azure agent logs is quite verbose and I haven't been able to effectively filter through them for a helpful answer. I also checked the GPO settings and they don't have any Windows Update related policies enabled under Computer Configuration>Administrative Template>Windows Component>Windows Update.

I haven't been able to find any help documentation on this.

AnuragSingh-MSFT 19,686 Reputation points

2023-05-23T06:44:09.4266667+00:00

Wai Lam, one of the options why reboot might not have been done is due to time requirements of reboot. During an update deployment, it checks for maintenance window utilization at multiple steps. Ten minutes of the maintenance window is reserved for reboot at any point. Before getting a list of missing updates or downloading/installing any update (except Windows service pack updates), it checks to verify if there are 15 minutes + 10 minutes for reboot (that is, 25 mins left in the maintenance window). For Windows service pack updates, we check for 20 minutes + 10 minutes for reboot (that is, 30 minutes). If the deployment doesn't have the sufficient left, it skips the scan/download/install of updates. The deployment run then checks if a reboot is needed and if there is ten minutes left in the maintenance window. If there is, the deployment triggers a reboot, otherwise the reboot is skipped.

For more details, please see Patch run failed with Maintenance window exceeded property showing true even if time remained

If the reason for missed reboot is still not sure, I would advise reaching out to Azure Support to get assistance 1:1, which will require examining the schedule configuration, review of logs and backend logs (if required)

Hope this helps.

Wai Lam 0 Reputation points

2023-05-23T23:56:01.48+00:00

Hi AnuragSingh-MSFT,

Thanks for the clarification about the time window. The machines in questions finished patching within 20 minutes. The maintenance window was for 2 hours in total. I waited about 40 mins after patching before I decided to manually reboot it (so it had 1 hour left in the maintenance window, even though patching was all done). Azure support plans are paid, and wanted to see if there was maybe something obvious I was missing before shelling out for one. Seems I will have to get one, and reach out to support to get this resolved.
Sign in to comment