Ability to Generate a Software Metering rule from Asset Intelligence Inventoried Software Data

Put beside the device name the related user of the device (Primary User) for reports, lists, views, dialogs....

For us it is always good to see that relation fast. So an option to add here and there the column for the primary user) will be very heklpful.

Many customers want to use Software Metering, but are legally not allowed to, because ConfigMgr always discloses the user's name and his/her usage. To be compliant with European law it should be possible to collect data only related to the machines software is installed on. Of course that would not allow for all metering features/reports to work, but at least could many companies start using the feature in general and act on that data.

It would be nice if there would be a report that shows all the current printers "attached" to a user profile (local and network). Without having to reside un custom SQL scripts or custom reports (for us the people that don't know scripting or SQL)

It will be very helpful to see both the device and user under one view in SCCM console!

Send Message to Device user to accept the remote Connection.
Users are rejecting the request as they are unaware of the connection requirement. So if we need to send a message explaining why he should accept request.

MAP Toolkit is a good tool but why should we have to use it when Asset Management is available in Configuration Manager? I'd expect to see edition of SQL Server, BIOS info on Windows licensing, virtualization rights, etc. in ConfigMgr. Reports are needed that would show number of processors/cores in front of products that are licensed based on number of processors/cores.

In version 1802 and below the uninstall Content ID is not visible in the console. Only the Install Content ID is visible next to the DeploymentType. That makes i hard to troubleshoot. Would be nice if you could add another column for the Uninstall Content ID next to the Install Content ID.
I wrote a littel script to extract the ID from the SDMPackageXML as a workaround. See attached.

With hardware inventory or another option, SCCM collect and sumarize data from performance monitor. The SCCM agent can start and stop the Performance Monitor.

It would be very useful to have a built in report that shows devices with details and primary user information for computers in a collection that do NOT have specific software installed. Currently we need to make a collection of target devices (based on OU for example) with software x installed, then another collection of those same target device, and add an exclude collection rule pointing to the first collection... it's difficult to explain that to basic operators and would be nice to have a built in report that does that for us.

In an Enterprise environment where multiple SCCM instances exist for a single active directory domain, the ask is that the OMS instance for a particular tenant support data input from multiple SCCM instances (OMS Connectors).

Ability to add Software Metering Data to the Data warehouse. This will allow potentially up to three years of trends of application usage that would help greatly with re-ups of applications.

Add missing properties to Win32_BIOS class to hardware inventory. In particular, both SystemBiosMajorVersion and SystemBiosMinorVersion property are missing which are useful to query BIOS versions with newer Dell hardware models, and for query in collections. No issues with using both properties on a query for a task sequence condition.

Currently there are scripts out there that can get warranty information, but HP for example seem to change the layout of their site that you have to reconfigure the scripts. It would be nice if Microsoft worked with the various vendors to be able to consistently retrieve that data.

Under Asset Intelligence for hardware requirements can you add TPM? with Cred Guard, Device Guard, BitLocker and other new features coming from Microsoft this would be a nice check to have built-in.

Part of the functionality seems to already be in the system, when adding a new Hardware inventory class. The point being the custom class(es) should be replicated to all providers, included in the database, and backed up when running the built-in backup task. This is useful when extending the console and striving for full integration, including the possibility to save settings and configurations.

Being able to right click an inventoried software and create a collection based on that inventoried software would be extremely helpful in easily affecting the computers for updates of said software.