Forum Discussion
Solved
OMS UPdate management not working at all
I got two seperate azure environments and I am trying to use oms update management (free tier). Both environments seem to be unable to patch any server they always fail with the most helpful error m...
Through a Microsoft support call we found out that the new problem is caused by a parameter error in a function call inside the oms patch script and an updated for a default printer driver from 2006 (on windows Server 2016).
At the moment when an update fails the script will try to add it to a failed list using this line of code:
AddUpdateToFailList GetUpdateKbID($update.KBArticleIDs) $update.Title $update.Identity.UpdateID $null "Install Failed" $baseException.HResult
The problem is that GetUpdateKbID and $update.KBArtcileIDs are treated as two seperate parameters.
By june the 15th a new version of the script should be rolled out to all azure datacenters.
The script contains a fixed function call.
AddUpdateToFailList $(GetUpdateKbID($update.KBArticleIDs)) $update.Title $update.Identity.UpdateID $null "Install Failed" $baseException.HResult
what update source are you trying to use, are you able to update the machine manually from the gui
I didn't have to configure any source in the updtae management solution. I am trying to update multiple windows Servers 2016 and one Windows Server 2016 which all can be updated manually from the GUI. Actually in my Visual Studio Subscription the machines actually update on every Startup. There is no WSUS Server in my deployment
so the clients are set to find updates automatically, when you log in after an update attempt does client show updates pending installation ?
i havent tested this the oms update, so currently i dont know much about it.
Yes the clients are set to find updates automatically and I even had them downloaded automatically on one machine the only thing that is missing is the installation. The update job finishes but says no data and the runbook which should patch the machine only shows the error message from my original post.
- I will try this feature in my test lab Thursday so I have a better understanding. could you confirm the following "Open the Windows Event Log, navigate to Application and Services Logs\Operations Manager and search for Event ID 3000 and 5002 from source Service Connector. These events indicate the computer has registered with the OMS workspace and is receiving configuration."