Thanks for the feedback.
Updated by bobmn for sangeev/OSD
Updated to Noted. We’ve been discussing the same in our planning meetings.
BobMN on behalf of SangeeV for SCCM OS DeploymentAlexM02 commented
Great idea Niall. To add to bdam's comments ... After a Win ADK update, the previous Boot Image drivers and other settings are no longer displayed (whole tabs of each Boot Image Property are missing). You only need to forget to make a manual note of these settings once, to never forget to do so again (unless your drivers and installation notes are well structured)! Nevertheless, it would be great if these existing settings were captured and re-applied by the upgrade process - even if they were saved to a config file and then re-applied, for each image.
Tempted to mark this completed, now that we’ve released full blown powerBI integration:
Building reports & dashboards doesn’t get much easier than that.AlexM02 commented
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.