Forum Discussion

Brass Contributor

Apr 26, 2017

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...

azure

Carsten Stahlberg
Jun 09, 2017
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

Carsten Stahlberg

Brass Contributor

May 08, 2017

Hi Kent,

all machines are based on the default azure Windows Server 2016 image from the azure portal.

The funny thing is that I get this error in two different subscriptions in completly differnt tenants and one of the OMS worklplaces was even setup by another colleage.

In the meantime I opened a Microsoft support case and we are now trying to find the cause of the issue.

Trying an update from your OMS is not necessary at the time but thanks for the offer.

I will update as soon as I know what happens here.

Carsten Stahlberg

Brass Contributor

Jun 09, 2017

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