We have a lot of subscriptions that use the same Report Name, and it is nearly impossible to determine which Subscription is which. Can you please add a Column to the Subscription pane that will show the 'Subject' of each particular Report? this will make it much easier to identify what each subscription is. Thanks!

Reporting is limited by the available data. A Location field allows geographic reporting.

In this section of SCCM: \Monitoring\Overview\Reporting\Reports\Hardware - Memory, it would be great to be able to see all computers that have less than 4GB of RAM, based on model. For example, I want to know how many of the Dell 3440s have 2GB so I can order more RAM for them.
Thanks!

No information is provided whether and what has changed within the reporting. I am particularly interested in very technical information, like stored procedures or changes that include the RBA model. Some of the changes might affect individually created reports, if they use the same methodology like the MS reports. Proactively apply those changes would suit me much better than waiting for an incident to be reported on a specific report -> detailed technical information on changes should be provided with each update (sp, used fn, ...)

The datawarehouse reports are a welcome addition. However it would be much more useful to be able to filter on collection for the report "Endpoint Protection and software updates compliance - Historical". We could then drill down to collections built on OS Version etc

I currently have over 60 reports that I have to copy on a daily basis to 13 different directories (due to their content/category) on a SharePoint site, as the OneDrive sync tool has issues, not to mention that persistent drive mapping to an MS hosted SharePoint site is not consistent, and I have to remap the drive when the site is failed over to a different server for patching, etc.
Manually copying these files is tedious.

As we get closer to the EOL of Winodws 7, it would be cool to have another widget in the Windows 10 servicing dashboard that shows Win10 v Win7 usage and the EOL date. Its a small thing but some additional visibility like that could help kick some orgs in the rear to get going on the upgrade to Win10.

The "Software updates - Compliance by computer" sub-report is an easy way to see which computers have failed updates.

Updates often are in a "failed" state because the computer hasn't been restarted recently.

Therefore, adding the last time the computer restarted to the report would make it easy to quickly identify if that is the likely cause of failing updates.

(Additionally, adding "primary user" to the report would be appreciated.)

I would like to be able to go to Devices or open a collection of devices, or even from the queries section. Add whatever information I'm looking for in the "Columns to Fit" area then be able to export exactly what I have on my screen into Excel. It would make reporting so much more simple. For those small requests that managers give you.

Display "Microsoft Update" as data source.
If you enable "fallback to Microsoft Update" for SUP deployment you cannot see this as data source. You can only see "Distribution Point", "Cloud Distribution Point", "BrachCache" and "Peer Cache"

The ability to create email subscriptions gives rudimentary notification when alerts happen. The ability to run a powershell script would open the possibility of integrating with 3rd party monitoring and notification systems. Current systems such as Solarwinds, PRTG,nagios/icinga2 and others have REST interfaces that can easily be addressed from powershell. This kind of integration would enable shops that choose not to run SCOM a way to integrate SCCM alerts into their existing monitoring set ups.

Ideally the script call would be able to pass the alert data to the script in some fashion.

Request SCCM enhancement to search for compliance by IAVM# (IAVA, IAVB) for either Enterprise-level or individual site under SCCM reports. A single IAVM may have several KB #'s (ex: MS patches) or there are very limited search capabilities for most 3rd party applications. Capability to capability to search SCCM reports by IAVM# will reduce amount of time in searching/compiling compliance metrics and will allow for quicker reporting of overall compliance.

"Hardware 01A - Summary of computers in a specific collection" shows logical drive space in GB but column header show MB. Update OOB reports to match avail data in DB

In the subscriptions I would like to be able to relabel a canned report name to what the report is doing.

Ability to generate a report in SCCM to list Primary mobile device for a user. Lack of this reporting feature creates additional overhead to MDM Administrators in identifying the user's device to take any remote actions. E.g. The device name could be "iPhone" There can be 100's of device with name "iPhone". This should be a very basic reporting capability that should have been in place. Kindly consider this request and introduce this reporting feature.

There is no view that will list the Language Name to LCID. The view must included "any" used within Software Metering. The closest that exist is the sys.syslanguages but this doesn't not included "any" aka LCID = 65535

missing Software Distribution report that will show deployment status (same as Status of a specified package and program deployment report)

It would be nice to have File Replication reporting for large sites. This way you can see all of Site to Site connection information and policies. Thus avoiding having to open and check each one for Rate Limits and Schedules. Maybe also tie in the Rate Limits from the DPs.

We have about 1200 computers, and would like to have a report to show the computers not shutdown after work duty

Microsoft reports that have other reports linked, don’t work anymore with our modified folder structure. So we applied changes to those MS reports. In this case we didn’t create our own report but modified the MS reports. -> links should be added like this: ..\subfolder\reportname, not using the complete hardcoded folder structure. That way – since the linked reports are always in the same folder or in the subfolder like in the default structure – all links will work no matter in which folder the report actually sits.