Upon scheduling an update deployment, message "....virtual machine being configured....", persists forever, no updates actually scheduled
Message "The components for the 'Update management' solution have been enabled, and now this virtual machine is being configured. Please be patient, as this can sometimes take up to 15 minutes." persists
Thank you for your feedback. We have released a deployment to address this issue. Please let us know if you have additional comments or questions.
Ryan Thomas commented
This is still occurring for some of my machines. The documentation describes 2 possible issues. Neither of which apply to me.
This error can be caused by the following reasons:
Communication back to the Automation Account is being blocked.
The VM being onboarded may have come from a cloned machine that wasn't sysprepped with the Microsoft Monitoring Agent installed.
Visit, Network planning to learn about which addresses and ports need to be allowed for Update Management to work.
If using a cloned image, sysprep the image first and install the MMA agent after the fact.
I have port 443 open for ANY and I can see the "UpdateState:Needed" messages in Workspace Logs.
I am receiving this issue for one of my machines.
In fact a dozen of my machines got totally disconnected from Update Management, we nearly failed our security audit, if this was not picked up. MS what is going on?
Can I just check whether you are using the Service Tags for the Network security groups as I think that this could be causing many issues. I Denied "internet" access for some of my machines and that stops Backups from working so am looking into whether this could be the same issue.
I have the same issue on one VM out of four that I enabled the other three are working.
I also have the message not going away for one of my machines. It worked on the other 7, but on this one the message persists.
Jose Angel Rivera commented
This is not working yet, at least for me.
It keeps showing the message "The components for the 'Update Management' solution have been enabled, and now this virtual machine is being configured. Please be patient, as this can sometimes take up to 15 minutes".
Still not working for me. Allows me to schedule update but never goes through and also never appears within Scheduled update deployments.
When I navigate back to the VM I get the message 'The components for the 'Update Management' solution have been enabled, and now this virtual machine is being configured. Please be patient, as this can sometimes take up to 15 minutes.'
Hey Mike, you should definitely not be hitting it that frequently. Here's the list of troubleshooting steps: https://docs.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker#troubleshooting If it's happening on every computer, maybe you have a network security rule thats blocking outbound access to *.azure-automation.net on port 443 ?
Mike Binnix commented
I first attempted to use this option when it was first released. It's a great idea. In practice it's just about unusable.
VMs I first provisioned with this feature months ago show a nice summary of pending updates. The controls to schedule an update persist for 10 - 15 seconds. Then this message replaces the controls to schedule.
"The components for the 'Update management' solution have been enabled, and now this virtual machine is being configured. Please be patient, as this can sometimes take up to 15 minutes."
Every maching, every time. I can recreate it 100% of the time I attempt to use the "Update Management" blade for windows VMs. This is true in both windows 2012 and windows 2016 vms. Sizes range from B1 to E4. All the same behavior.
It's frustrating to see such a trail comments below on this exact issue, and your response is "we're working on it, if you have a problem send us details.". Given the ease of recreating the problem, you should need us to tell you how to recreate it and we certainly can't tell you how to fix it.
Please let us know when we can count on this as a reliable feature or admit it won't be so we can make other arrangements.
Littley Daniel commented
I have been having same issue and troubleshooting it all of today. Now I find this is a major issue. Microsoft have encouraged us to use this over setting up DSC to manage updates, product clearly not ready due to its limitations and now this issue.
Please can Microsoft provide formal update to what is happening with this issue and when we can expect it working in the future?
Palle Helenius commented
What is going on with this? If it's not even posible to activate it, it's should not even be in preview.
Getting the same error as everyone else..blue banner saying
The components for the 'Update management' solution have been enabled, and now this virtual machine is being configured. Been like that for a good two months. I've done the basic - rebooted the server. Can we please get a status update on this issue? I appreciate that you are working on a fix but is there any ETA?
Mike Binnix commented
It's been more than 3 months since the original post brought this up, and 2 months since "Automation Team" achnowleged it. When can we expect an update?
Matt Feeney commented
We experiencing the same issue, either a blue banner "The components for the 'Update management' solution have been enabled, and now this virtual machine is being configured. Please be patient, as this can sometimes take up to 15 minutes." or no banner and reports that there are no update required. But one of our VMs has Windows Updates Enabled and reports its missing a number of updates.
Hi, Any update on this?
Is this still broken? It certainly appears to be across numerous different azure subscriptions for us
Wesley Haakman commented
Any update on this?
Dave Patterson commented
I have noticed that if I refresh the browser screen, the links under the '15 minute' banner are accessible, but only for a few seconds, so I have to click quickly to access them. Once i do that, they do work and I am able to patch servers and deploy KB packages.
Dave Patterson commented
Same issue for the last few weeks.
Karl Nicholson commented
Same for me. Its been three hours so far.....