4 Replies Latest reply on Nov 3, 2014 7:30 AM by justinm

    Computer Targets Needing Updates Count report

    justinm

      I have a Patch Manager report that I thought worked well, but now I'm not sure it's accurate. I've attached it for your perusal.

       

      My problem is that 134 PCs are perpetually listed in this report as needing updates, but only 7 PCs show up in the Update Services portion of the console as requiring one or more updates. For some further background, there is a Spiceworks thread I created about this when I thought it was a WSUS issue, but it appears that is not the case.

       

      Did I mess this report up, or is this a case of my thinking things work differently than they do?

        • Re: Computer Targets Needing Updates Count report
          Lawrence Garvin

          134 PCs are perpetually listed in this report as needing updates, but only 7 PCs show up in the Update Services portion of the console as requiring one or more updates.

           

          You've only attached the XDQ (report template), so it will be impossible to use that to inspect your data. I doubt this is an issue with the report template. At the base, this seems to be a simple matter of perpetually including stale data for 134 systems in the report, so my focus for the start is on the actual data.

           

          • When was the last WSUS Inventory task peformed?
          • What are the Last Reported Dates for these 134 PCs?
            • Re: Computer Targets Needing Updates Count report
              justinm

              That's the thing--I'm having trouble even figuring out which 134 PCs it's complaining about. If I run the WSUS Server Computers Updates Count Info report that comes standard with SWPM, I get 41 computers that report some combination of Not Installed, Downloaded, Failed, and/or Installed Pending Reboot.

               

              Now, one thing I did notice is that the inventory task that runs on all PCs daily does not include the Windows Update Scan datasource. I thought Windows Update History would be sufficient for this purpose. Is that not the case? It seemed to work prior to this update situation.

               

              If it matters, the updates in question were the x86 and x64 Microsoft .NET 4.5.1 Framework install. We have a web app that fails horribly if this is installed. It acts as if there is no .NET framework installed at all.

               

              EDIT: I'm sorry, you asked two very specific questions. I didn't mean to ignore them; I'm trying to answer this as I'm taking multiple phone calls and it's not working so well.

               

              • When was the last WSUS Inventory task performed?

              Every computer in the managed computer inventory gets inventoried every night. I don't see a specific "WSUS" datasource; there are several related to Windows Update that get collected: all but Windows Update Agent Log and Windows Update Scan.

               

              • What are the Last Reported Dates for these 134 PCs?

              Like I said above, I don't know which 134 are the problem exactly, but all 311 computers that report to WSUS have done so since 10/21. All but four have reported since 10/26. (Those four older ones are all laptops that aren't often directly connected to the network.)

                • Re: Computer Targets Needing Updates Count report
                  Lawrence Garvin
                  That's the thing--I'm having trouble even figuring out which 134 PCs it's complaining about. If I run the WSUS Server Computers Updates Count Info report that comes standard with SWPM, I get 41 computers

                   

                  Presumably it would be the 93 PCs that do not appear in the stock report. It should be fairly trivial to sort those two reports by computer name and reconcile the list.


                   

                  Now, one thing I did notice is that the inventory task that runs on all PCs daily does not include the Windows Update Scan datasource. I thought Windows Update History would be sufficient for this purpose

                   


                  Both are absolutely irrelevant to a WSUS report. WSUS reports are populated by the WSUS Inventory task, and only by the WSUS Inventory task.

                   

                  • When was the last WSUS Inventory task performed?

                  Every computer in the managed computer inventory gets inventoried every night. I don't see a specific "WSUS" datasource

                  I think this is a major lead on finding the source of your erroneous data.

                  Please review these resources for more information:

                  An Overview of Patch Manager Inventory & Reporting for WSUS

                  Reporting and Inventory Help


                   

                  but all 311 computers that report to WSUS have done so since 10/21

                   


                  That's not healthy either. Computers configured to use WSUS should be reporting at least once every 22 hours. Those that do not are either powered off or malfunctioning.

                    • Re: Computer Targets Needing Updates Count report
                      justinm

                      I don't know what happened because I changed nothing, but suddenly over the weekend the number in the report dropped from 134 to 2, exactly what the eyeball test tells me it should be at this point.

                       

                      Lawrence Garvin wrote:


                      That's not healthy either. Computers configured to use WSUS should be reporting at least once every 22 hours. Those that do not are either powered off or malfunctioning.

                      Right, they were powered down or laptops that were disconnected from the network.