Patch Management Group

 View Only
  • 1.  Reporting on Superseded Patches and Issue with MSWU-2012

    Posted Sep 27, 2016 10:22 AM

    This is a 2 part question as the patch in the example may not be superseded.

    1) How do you run a report on a patch that has been superseded ?

    Lets say you have a patch window and want to see how well the previous patch has been delivered while you are testing the current one?


    2) As an example (this also appears to be an issue for us) MSWU-2012 was released May 3rd 2016, KB3115127 for Outlook 2010, has 0 Targetd computers (in the resource manager) currently I have disabled the option to "Disable all superseded Software Updates" and for good measure I have turned off "Automatically revise Software Update policies after importing patch data".

    MSWU-2012 is now missing from my compliance report, yet it was there on Sep 20 and missing on Sep 22 (I do not save the report every day). There are over 100 computers that need this patch and I am not sure if they will get it. The patch is a prerequisite for an Exchange upgrade, therefore it is being closely monitored. I can not find any Microsoft documentation that states this patch was superseded either - otherwise I could deploy the current patch. I still would like a solution to #1 above.

    Per https://protect7.shavlik.com/2016/09/20/new-patch-data-available-2-0-2-723/   there was a revision  – Modified MSWU-2012(Q3115127): Updated detection logic

     



  • 2.  RE: Reporting on Superseded Patches and Issue with MSWU-2012
    Best Answer

    Trusted Advisor
    Posted Oct 13, 2016 11:13 AM
      |   view attached

    Hi Gregg,

    You'll want to open Patch Remediation center and change drop down to Windows Superseded Bulletins.  Then you can filter top right by name (check the screenshot, I type MSWU-201).

    You should see MSWU-2012 was superseded by MS16-088.

    Hope this helps!



  • 3.  RE: Reporting on Superseded Patches and Issue with MSWU-2012

    Posted Oct 17, 2016 01:18 PM

    Thanks (sorry for the delay) - I forgot all about that feature. 

    Actually I found different information from Microsoft, MS16-107 is the latest patch that needs to be installed to support Exchange 2016. 

    From : https://support.office.com/en-us/article/Outlook-Updates-472c2322-23a4-4014-8f02-bbc09ad62213?ui=en-US&rs=en-US&ad=US

    Click next to Outlook 2010.