Microsoft

System Center Configuration Manager Feedback

How can we improve Configuration Manager?

SCCM Report - Easy way to create Report & Dashboard

Not really easy to create some SCCM report or Dashboard if your're not a SQL DBA .. even with Report Builder.
Could be awesome to have a new tool where Reports or Dashbaord could be created easily whithout searching which SQL views I need ..ect ... Like some others concurrent application give.

638 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    MERIGOTMERIGOT shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    31 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • JimJim commented  ·   ·  Flag as inappropriate

        Do the right thing MS, do try to force to buy cloud services for reporting on a tool that we already purchased. This is a joke! Get it together Microsoft!

      • Anonymous commented  ·   ·  Flag as inappropriate

        If PowerBI is the solution then I'll quit administrating your product and move on. The current SCCM DB is a joke. PowerBI is a joke.

      • AlexM02AlexM02 commented  ·   ·  Flag as inappropriate

        Creating Custom Queries is intuitive, is based on SCCM inventory (and other) information and can be displayed as WQL Queries. Converting WQL Queries to SCCM Custom Reports is the best way forward, as it would not require a detailed understanding of SCCM's SQL Schema, tables, and views in the way Report Builder does - something that is complex, poorly documented, and time-consuming. PowerBI does not seek to address the industry's main requirement of making user customised (formatted) reports easily accessible. It seeks to provides additional solutions, brings in an additional Azure requirement, and is over-engineered. While it is acknowledged that Query Results can be copied into Excel, a query to report conversion will satisfy 95% of the customised report requirements that I have worked on over the years, across dozens of SCCM customer projects of all sizes.

      • HeikoHeiko commented  ·   ·  Flag as inappropriate

        PowerBI cant be the solution. Our customers need a solution that makes creating reports easier. Working with the current DB structure is an impossible task for many since its so complex and undocumented. Just pointing to a different visualisation tool will not help anyone ....
        not even talking about the cloud only aspect which many customers will not tolerate.

      • Roy PadrickRoy Padrick commented  ·   ·  Flag as inappropriate

        This could not be further from a real answer. Telling people "there's a third party app" for basic functionality is not a real solution to tell people.

      • MattyFonzMattyFonz commented  ·   ·  Flag as inappropriate

        How about a full refresh of the SSRS reports with updated graphics so they don't look so 90s? And the ability to tie into PowerBI (free or paid for auto updating options) for customers that want to explore that avenue?

      • Iain FairbairnIain Fairbairn commented  ·   ·  Flag as inappropriate

        PowerBI is NOT the solution. you can't just assume all organisations will use a cloud based reporting solution for their on premises enterprise management systems, additional licensing or cloud data charges alone will basically blow it out of consideration, not to mention privacy concerns. But the real issue is that in the mean-time if the MS response is "use PowerBI" then that means they have no incentive to enhance one of the fundamental features of SCCM, that frankly is given inadequate development already. SSRS is okay, but it has a steep learning curve and arguably is harder to use in some ways than classic SCCM 2007 reporting. So while it is more capable if you really know what you are doing with the SQL schema and reportbuilder (arguably one of the least user friendly design tools I have ever encountered). SQL management studio create views functionality shows some good capability with graphically allowing you to join tables\views and have it then generate the SQL code for you. something like that perhaps simplified would be a great addition to an on-premises reporting tool either built into the SCCM console or (more likely) as a companion tool launched from the console.

      • Jason KellarJason Kellar commented  ·   ·  Flag as inappropriate

        Hi djam,

        Regarding your reply with Microsoft Power Bi. Where can i get information about what data is transferred to the USA and if there is data transferred to the USA is their a version for Canada? i work at a university and our privacy laws are very strict about what can be sent and stored in the USA.

        Thanks

      • Qasim MashwaniQasim Mashwani commented  ·   ·  Flag as inappropriate

        @djam While creating reports via PowerBI is very easy many SCCM users may not be licensed for it and the feature requests states integration of features into SCCM.

      • Dustin AdamDustin Adam commented  ·   ·  Flag as inappropriate

        we've implemented the PowerBI Report Pack, and while it's great, it feels... unfinished. there are a number of tables that don't have active cardinal relationships. hopefully there will be an update to the report pack, or at least the sql scripts that extract data to the report pack sql database.

      • Patrick TilsenPatrick Tilsen commented  ·   ·  Flag as inappropriate

        On-prem is definitely a requirement for many organizations. Integrating anything not built-in fails to meet the "easy" criteria. This should either be in-console, or an easy-to-use tool that installs alongside the console.

      • JustynaJustyna commented  ·   ·  Flag as inappropriate

        @Mattias, thank you for letting us know. This bug has been fixed but requires you to download the latest MSI from the website. Sorry about the inconvenience!

        @Everyone, thanks a lot for the feedback around the SCCM Solution Template. If there is direct feedback you would like to pass onto our team (about how we could improve the Power BI SCCM reports) please contact our team at pbisolntemplates@microsoft.com

      • MarcMarc commented  ·   ·  Flag as inappropriate

        Report looks pretty, data is very useful, but I'm not sold that SCCM admins are going to become PowerBI experts. I still think the request here would be for an Administrative Schema to flatten the entire CI table structure used for Updates, Compliance, etc... Once the admins don't need to learn the complex SQL schema between all the sprocs and tables then it should be much easier for people to create the queries needed and dump them into an SSRS report.

      • Anonymous commented  ·   ·  Flag as inappropriate

        PowerBI is a significant improvement to SSRS and report builder but unless you are creating basic reports with a 1:1 relationship of data to a chart, PowerBI doesn't make creating reports easier as the core issue is knowing the db schema and how to map data together.

        As of now you need to have a skillset in SCCM, Structured Query Language (you don't need to be a dba just know joins and some aggregate functions at minimum), and a skillset in a reporting platform\tools (SSRS).

        We need an offline method (No internet connection, no subscription) for reports and at least and at lease updated documentation on the db schema. Ideally an easy way for admins to map views without being a SQL expert.

        Until the entire reporting platform can be revamped, an idea that can help (not solve) the issue is create a converter of the SCCM queries (WQL) to SQL and maybe even a button that says “Create report” that’ll do it for you.

      • MattiasMattias commented  ·   ·  Flag as inappropriate

        There is a bug in the solution that prevents data to be populated in the Updates Page.

        There is an error in the store procedure called pbist_sccm.sp_populateupdate.

        On row 35 it says:
        TRUNCATE TABLE pbist_sccm.update;

        but it should say:
        TRUNCATE TABLE pbist_sccm.update_staging;

        Otherwise the store procedure just moves the data from pbist_sccm.update_staging to pbist_sccm.update but then wipes the data again...

      • Andres PaeAndres Pae commented  ·   ·  Flag as inappropriate

        Power BI is great, but it requres separate infra/licensing? I believe initial idea is to get it EASY way :)

      ← Previous 1

      Feedback and Knowledge Base