PS Windows Update History question

Comments

6 comments

  • Andrew Gresbach

    actually i'm seeing a lot of reports w/ this same issue  since the 2004 build....if you run it local it starts to populate results but then hangs.....workaround is to add:  -last 100 to the command and seems to work

     

    0
    Comment actions Permalink
  • Colby Bouma

    Thank you for the suggested fix. I opened a pull request to add it to the scanner: https://github.com/pdq/PowerShell-Scanners/pull/78

    0
    Comment actions Permalink
  • Andrew Gresbach

    no problem! i've tried w/ anywhere from 100 to 500 as values and all work (i'm sure others should too)

    0
    Comment actions Permalink
  • Andrew Gresbach

    one more thing on this.....while this scanner works well for a history,  wondering how we could add a powershell scanner to JUST show the installed KB's instead (successfully installed ones that is).  I found this simple powershell command on a site that works great running local but cant quite get it to work well in PDQ (output is gibberish) so i'm sure its just my lack of experience translating it over

    Get-HotFix 

    I did actually get that to show some useful data but also pulls in way more into pdq than it does just running in PS but maybe i can just ignore that

    0
    Comment actions Permalink
  • Colby Bouma

    PowerShell formats objects in the terminal. Inventory doesn't know how to read that format data, so it returns the entire object. You can see what Inventory will see by piping your output to Out-GridView. To filter the result, you can use Select-Object.

    0
    Comment actions Permalink
  • Andrew Gresbach

    All good! That's what I figured was going on.....I messed with it a bit more and it gives the fields I needed so I was able to build a collection based on it great. Thanks for the reply

    0
    Comment actions Permalink

Please sign in to leave a comment.