Forum Discussion
Deleted
May 02, 2018OMS Update Management Solution - Not Configured Message
I have configured the Update Management solution in my OMS workspace. Everything seems to be working fine for most, but not all VMs I manage. When I navigate to the Automation Account > Update Ma...
- May 03, 2018Hi, Azure Update Managament is using the OMS agent to do the assessnent of the server. The actual patching happens via a feature called Hybrid Worker. The OMS Agent distributes the bits for Hybrid Worker and the server is automatically configured for Hybrid Worker by Update Management. In this case seems that your server cannot be configured as Hybrid Worker. This Hybrid Worker is also reffered as Update Worker when it is configured by Update Management. In case the same computer was previously connected to another workspace there is the possibility that some old configuration was left on the computer and blocking the new registration. This is because only one Update Worker is allowed. The article is located here: https://cloudadministrator.wordpress.com/2017/05/24/moving-update-worker-server-between-oms-workspaces/ Registered Update workers can be seen in Azure Automation -> Hybrid Worker Groups -> System Hybrid Worker Groups. There you should all the servers that are onboarded to Update Management and they should report every 30 minutes. Keep in mind that you cannot reigster Update Worker manually. If you perform the manual operation you are registering Hybrid Worker that is used to run your own custom runbooks on a server. Let us know if you see any other errors. Also sometimes the server might be assessed before it is registered as Update Worker.
Aug 30, 2019
HiPatrickF11 Unfortunately the only thing I could think of is those registry keys but you have cleaned them already. Another thing you can do is check in the logs if there is some hint what is going on. You can check Operations Manager even log. Best is to stop the agent, clear the cache, start it and see what is being generated as warnings and errors. Other thing you can check is Operations table (I think that was the name) if there are any records there. Sometimes for some problems with the agent or specific solution data is written in that table to show what is the problem.
I hope this will help you!
PatrickF11
Aug 30, 2019Steel Contributor
Stanislav_Zhelyazkov Thank you for your answer.
Luckily things were resolved by themselves about 48h after my posting.
Azure.... 😄
- bwdurFeb 27, 2020Copper Contributor
PatrickF11 I'm having the same issues. Your servers just started working correctly on their own?
- PatrickF11Mar 09, 2020Steel ContributorYes, everyhting worked as expected about 48h afterwards.
- bwdurMar 09, 2020Copper Contributor
PatrickF11 thanks for the response. Turns out after contacting their support they actually had a DNS issue that was preventing new servers from enrolling in the update platform. After around 3-4 days for me they finally started working as expected.