none
"Critical" Updates with "None" as a severity do not get pushed

    Question

  • Fine tuning my updates deployment and I saw that updates with the classification "Critical" in WSUS were not being pushed.  Sure enough they had "None" listed as the severity.  My ADR does not have "None" checked so I understand why they did not go out however we want to make sure ALL critical updates are deployed. 

    We did not really way ALL updates with the severity as "None" to go out which is what looks like will happen if I check "None" in my ADR.  Sort of silly MS does this.  Why does MS flag a critical update as "None" and what is the best practices to deal with those if you do not want to just push everything with a "None" severity.


    • Edited by JHFerry3 Thursday, May 16, 2013 4:01 PM
    Thursday, May 16, 2013 3:59 PM

Answers

  • Since there have been no other people attempting to answer this question, At this point I would suggest contact Microsoft Support (CSS) directly for support.


    http://www.enhansoft.com/

    Saturday, June 01, 2013 3:03 PM
    Moderator

All replies

  • 22 views?  Did I not ask clearly enough?
    Thursday, May 16, 2013 11:43 PM
  • just cleaning up old posts, did you figure this out?

    http://www.enhansoft.com/

    Saturday, May 25, 2013 2:09 PM
    Moderator
  • Since there have been no other people attempting to answer this question, At this point I would suggest contact Microsoft Support (CSS) directly for support.


    http://www.enhansoft.com/

    Saturday, June 01, 2013 3:03 PM
    Moderator
  • Fine tuning my updates deployment and I saw that updates with the classification "Critical" in WSUS were not being pushed.  Sure enough they had "None" listed as the severity.  My ADR does not have "None" checked so I understand why they did not go out however we want to make sure ALL critical updates are deployed. 

    We did not really way ALL updates with the severity as "None" to go out which is what looks like will happen if I check "None" in my ADR.  Sort of silly MS does this.  Why does MS flag a critical update as "None" and what is the best practices to deal with those if you do not want to just push everything with a "None" severity.


    Microsoft defines Critical Updates as "A widely released fix for a specific problem that addresses a critical, non-security-related bug." (see http://support.microsoft.com/kb/824684)

    So, as Critical Updates are not security updates at all, they do not have a Bulletin ID to define severity (this is why in WSUS Critical Updates have an empty Bulletin ID field and Severity equal to "None").




    Monday, February 02, 2015 10:16 PM