SCCM Deployment Dashboard

Overview Some of the challenges normally faced with SCCM is normally the issues which could possibly arise from carrying out any kind of deployment, and proceeding with caution to not disrupt service and cause any issues whilst performing any kind of deployment. Though yo

701 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
  • Error in reports
    2 Posts | Last post August 13, 2019
    • Hi,
      I am unable to open the report in report builder.
      "Failed to open report " SCCM deployment dashboard.rdl"
    • Which version of SQL report Builder and SQL are you using? Are there any other details to the error you are getting?
  • Packages Required in Dropdown List
    2 Posts | Last post July 04, 2019
    • I don't currently deploy any Packages, only Applications. Can the requirement for a Package be removed so the report will run without one being listed in the Dashboard?
    • Hi,
      Will be making some changes to this so that each part is optional
  • Version of Report Builder
    5 Posts | Last post April 10, 2019
    • What is the minimum required version of Report Builder? When I tried to upload the report file (.rdl) I got the following error; "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. Details: The report definition has an invalid target namespace '' which cannot be upgraded. (rsInvalidReportDefinition)"
    • Hi,
      I created this dashboard report on Report Builder 2016 and SQL Server 2016, try opening in Report Builder 2016.
    • I am able to open the report in RB 2016 but when I try and run it I get the same error. Does this report involve any BI?
    • FYI; I am using SQL 2012 SP4
    • Think it would be down to your SQL 2012 as well as I had a similar issue opening the Software Update dashboard in this way, so the minimum requirements would need to be SQL 2016 due to its default definitions. There isn't any BI involvement in this one, but...I may be looking to convert them at somepoint to make them compatible