SCCM Software Update Deployment Dashboard

 OverviewThis dashboard provides a full SPOG (Single Pane of Glass) look into your entire WSUS/SUP infrastructure to see exactly how all deployments are running, and what your overall expected successful forecast figures will be.There are various sections which go into the dashbo

4 Star
288 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
Sign in to ask a question

  • Error "tbUpdate" not valid
    2 Posts | Last post June 04, 2019
    • Hello, thanks for this dashboard but for me it's not working.
      I have error for the "lastestdeclinedUpdates" and "ObsoleteUpdates" datasets request : object name "tbUpdate" not valid.
      I don't have Wsus Server, my SCCM server get the rule of Wsus Server, coul'd you help me for this error ?
    • I found, sorry, my problem was about the data sources of the Wsus base, i select the correct database and the problem disappear.
  • Dashboard is not running
    2 Posts | Last post March 27, 2019
    • My user is SCCM admin, and still get this error.
    • Are you able to run a direct query in SSSMS against this view? If getting the same errors it would be down to permissions. What role does this account have in your SCCM console and also what roles does this account have in SQL in its user mapping? Would need to be a sysadmin or with an account in SCCM with admin rights to run the queries for
  • Custom table
    4 Posts | Last post March 06, 2019
    • Hey there, correct me if I am wrong but modifying the database puts you out of support from Microsoft if I am not mistaken.  I know it's just adding a table and not modifying existing tables, just want to be sure that if that does break support that we know prior to implementing.  I imagine you could just drop the table if you had to call MS Support but something folks should know.  Again I am not 100% positive on this but have always heard this was the case?
    • Hi, I think you are right. It should just be a matter of dropping the table as it's just a separate one which is used as a reference for the error codes. I did however have the original design which I made a separate database on the same instance rather than the table. So I'll add to the overview to state this aswell as add the option to the instructions and the query to reference the DB with the error codes. Thanks
    • Ive added the information in for the instructions for the custom table for a custom database to be created method also, i can edit this and re-upload so the queries will point to a custom DB rather than a table aswell
    • Cool.  Thanks Dwalsham!
  • Dashboard is not running
    2 Posts | Last post March 04, 2019
    • I am trying to implement your reports, but report builder shows Access denied for (vSMS_UpdatesAssignment)
      Do we need some custom permissions?
      TITLE: Microsoft SQL Server Report Builder
      An error occurred while executing the query.
      The SELECT permission was denied on the object 'vSMS_UpdatesAssignment', database 'CM_ITD', schema 'dbo'.
      The SELECT permission was denied on the object 'vSMS_UpdatesAssignment', database 'CM_ITD', schema 'dbo'. (Microsoft SQL Server, Error: 229)
    • Looks like the account you are using doesnt have enough permissions to look at the Software Update Point tables and views. You'll need an account which has permissions to see the software update deployments and assignments. An SCCM admin account could be of preference to ensure all tables and views and have queries ran against
  • What version of Report Services is required?
    2 Posts | Last post March 04, 2019
    • i get this:
      The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas 
    • Hi
      The report was created using SQL Report Builder 2016. If you are able to upgrade your SQL Report Builder to the 2016 version try to run it after, haven't tried this on an earlier version