locked
How to generate a WSUS 3.0 report on a Win2008 Standard SP2 server that shows not installed/needed updates that were released prior to a given date? RRS feed

  • Question

  • Hi,

    We recently switched over to WSUS.  We have 77 Windows 7 x64 Enterprise clients.

    We're trying to find a way to display Not Installed / Needed updates that were released prior to a given date in a report.

    So for example, we'd like to know which updates released prior to 1/9/2016 are still Not Installed/Needed for our machines.

    Ideally the report would contain the computer name, update description and pertinent KB, and release date of the update.

    Is there a way to do this?  I've tried using Powershell and it seems like the different Powershell objects are not really geared to do this in an intuitive way.

    Thanks,
    Erik


    Tuesday, February 16, 2016 5:41 PM

Answers

  • Hi Avanti Press,

    >Computer 1:

       KB234234234 FakeUpdateName 2/10/2016

    Yes, the GUI is hard to form the result directly, it seems we need to find a specific script to achieve this goal.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, February 23, 2016 8:57 AM
  • Hi Avanti,

    have a look at the project below:

    https://poshwsus.codeplex.com/

    There are a lot of useful cmdlets, that should work for you.

    Best regards,

    Andrei


    We could change the world, if God would give us the source code.

    Friday, February 26, 2016 5:47 PM

All replies

  • Hi Avanti Press,

    The method I could provide is as follow:

    1. Click All updates, and choose the "Approval" and "status" type you want;

    2. click "Title", then right click, you will see the view as the screenshot, then check "Release Date":

    3. Click "Release Date", then the update will sort by the release data:

    And if you have other requirements, you may check the related column you want.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Wednesday, February 17, 2016 3:32 AM
  • Hi Ann,

    Thanks, but that doesn't tell us what computers are missing the updates.

    We're looking for a way to show basically this:

    KB / Description | Release Date

    Computer 1:

    KB234234234 FakeUpdateName 2/10/2016

    Computer 2:

    KB234234234 FakeUpdateName 2/10/2016

    Thanks,

    Erik

    Thursday, February 18, 2016 3:47 PM
  • Hi Avanti Press,

    >Computer 1:

       KB234234234 FakeUpdateName 2/10/2016

    Yes, the GUI is hard to form the result directly, it seems we need to find a specific script to achieve this goal.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, February 23, 2016 8:57 AM
  • Thanks Anne.

    How would we achieve this using Powershell?

    Friday, February 26, 2016 5:35 PM
  • Hi Avanti,

    have a look at the project below:

    https://poshwsus.codeplex.com/

    There are a lot of useful cmdlets, that should work for you.

    Best regards,

    Andrei


    We could change the world, if God would give us the source code.

    Friday, February 26, 2016 5:47 PM
  • Good Day

    Have you tried to query the WSUS db?
    You can get the information that you need from there
    Regards

    Friday, February 26, 2016 6:33 PM
  • How to Determine Out-Of-Compliance Computers

    https://msdn.microsoft.com/en-us/library/ff426350(v=vs.85).aspx


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Saturday, February 27, 2016 9:03 AM