Collections, especially Computer Collections, aggregate differing types of devices, its a common complaint on my team that selecting columns when viewing a specific group doesn't persist to a specific Collection. For example, we have a Collection for onboarding to Windows Defender ATP, and when selecting a Column for Onboarding State, the column then shows up when viewing a Computer Collection that contains iOS Devices, and a different set of columns then has to be selected to view, for example, IMEI. It would be great if Column selection would "stick" with the collection it was selected for, in the form perhaps of a local user preference, so that when viewing a collection you have quick and easy access to relevant columns for that collection
awesome ask. makes sense.
I'll chime in here too, I like the idea of the Windows 10 Servicing via SCCM, but after experimenting with it we ran into the same issues. we spent a lot of time carving out the consumer elements prior to building our images, having that junk get re-inserted is a show stopper. in addition, we discovered the servicing option doesn't allow for the execution of custom scripts, i.e. to force a check for windows updates post-upgrade. it feels like the solution is almost ready, enterprise customers just need some additional under-the-hood control points before we can leverage it in production.
Tempted to mark this completed, now that we’ve released full blown powerBI integration:
Building reports & dashboards doesn’t get much easier than that.
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.