3 Replies Latest reply on Aug 3, 2017 10:44 AM by cwinning

    Severity of Microsoft Non Security Patches

    jiwilson Rookie

      There is a document for this subject, but it pre-dates the changes to the patching service model introduced by Microsoft since October 2016.

      Understanding patch severity in a Shavlik Protect patch scan and why it may differ from Windows Update

       

      Could I please ask for the document to be updated to accurately describe the current Ivanti process and information?

       

      Specifically, there is apparent inconsistency in the setting of the MSSevertyID for patches

       

      Example:

       

      SSWU-006/Q3211320/KB3211320 in Microsoft Update Catalog is classified as "Critical Updates"

      Microsoft Update Catalog

      In Ivanti HF7B it is MSSeverityID="0" (none or unknown)

       

      It is superseded by:

      SSWU-006/Q4013418]/KB4013418 in Microsoft Update Catalog is classified as "Critical Updates"

      Microsoft Update Catalog

      In Ivanti HF7B it is MSSeverityID="1" (Critical)

       

      This is superseded by:

      MSNS17-06-4023834/Q4023834/KB4023834 in Microsoft Update Catalog is classified as "Critical Updates"

      Microsoft Update Catalog

      In Ivanti HF7B it is MSSeverityID="1" (Critical)

       

      So, it seems that newer patches are more accurately reflecting the Microsoft Update Catalog classification

      Will Ivanti be taking action to consistently reflect the classification from Microsoft Update Catalog into the MSSeverityID?