Now that we have the information about our monitors in our database, we need to figure out a way to display it. For that, we will need to write a new report. Since the report editing features in either the SCCM console or the Reporting Services Editor are quite bad, it’s much easier to first create the report in SQL management studio.
thank you very much, all three articles helped me greatly!
Worked out great for me. Very well presented, thank you!
Hi awesome work, much appreciated.
Quick query how would I go about editing the report to prompt for a collection prior to running the report, would this be possible?
Thanks in advance
great job !!
Awesome work. I’d like to know how could I add Collection into report. very much appreciated
For some reason, when I run the report, I get a listing from only one computer. I have run the script on several computers . I have checked the resource explorer to verify that the record was populated in WMI. I also see a number of new records in the SQL view.
For whatever reason, I don’t v_GS_MONITORDETAILS in my SQL views.
I can see data within Resource Monitor but that’s it.
Bob, you need to change the client settings like in https://exar.ch/collecting-custom-wmi-classes-with-sccm/ (do the “Hardware Inventory Class” step) to enable collection of the new WMI class into the database.
First and foremost, thank you for presenting this so well in this video.
Is there a way to filter this report with user or device collections?
Thanks,
Sigi
Sure, any report can do that. The view that contains collection memberships is called v_FullCollectionMembership. If you google for that you can find sample reports.