Two ideas -
Have a methodology to integrate license entitlements from an Enterprise Agreement (or select agreement) into asset intelligence. Perhaps in addition, there could be a report showing licenses under an expired agreement that you are no longer entitled to use (ie. any subscription based license).

Integration of the MAP toolset for license tracking purposes for licenses that are based on socket counts. For example, if you license the host for SQL Enterprise, there should be a way to roll up virtual instances to the host level to ensure compliance and report on them inside Asset intelligence. Assuming this is integrated, you can then apply app metering to understand where host based licenses are under utilized and move them appropriately.

Anything that makes it easier for us to do due diligence to ensure we are compliant from a licensing perspective. It is very labor intensive, and at times, compliance is unclear or left to interpretation.

Excellent work in adding new features in SCCM 2012.
Current model of metering thru exe, though works to an extent, it has flaws and doesn't offer needed confidence or trust to business about actual metering of an application as its limited to an exe. If possible, I request Microsoft to research on allowing SCCM admin to select an application, in backend SCCM converts that to all related exe for metering on clients and then monitor only installed application of those group of exe. Its note easy and throw some challenges but I trust and for experts at MS, nothing is impossible

After extending the hardware inventory to collect DEVICE_GUARD_DATA clients are sending the inventory but its failing to process on the SCCM server. It fails with error: Compilation failed~syntax error on line 8345, token ',' SMS_INVENTORY_DATA_LOADER 10/26/2016 2:54:48 PM 19308 (0x4B6C)

Got the MIF file from the customer and checked it. Its failing on below section on "AvailableSecurityProperties":

*******************************************************************
Start Group
Name = "Device Guard"
ID = 817
Class = "MICROSOFT|DEVICE_GUARD|1.0"
Pragma = "SMS:ADD"
Key = 2
Start Attribute Name = "AvailableSecurityProperties" ID = 1 Type = Integer Value = End Attribute
Start Attribute Name = "InstanceIdentifier" ID = 2 Type = String Value = "4ff40742-2649-41b8-bdd1-e80fad1cce80" End Attribute
Start Attribute Name = "RequiredSecurityProperties" ID = 3 Type = Integer Value = 2 End Attribute
Start Attribute Name = "SecurityServicesConfigured" ID = 4 Type = Integer Value = End Attribute
Start Attribute Name = "SecurityServicesRunning" ID = 5 Type = Integer Value = End Attribute
Start Attribute Name = "Version" ID = 6 Type = String Value = "1.0" End Attribute
Start Attribute Name = "VirtualizationBasedSecurityStatus" ID = 7 Type = Integer Value = 0 End Attribute
End Group
*******************************************************************************

It fails on "AvailableSecurityProperties" where as per the table design in database, it is expecting "NULL" or "nvarchar". If we check this class on Windows 10 Machine we find more than 1 values. That is what client would send to the server as a part of inventory but MIF file will never get processed because of the way Tables and triggers are created in the database. Due to this behavior Customers can never collect "Device_Guard_Data" as a part of inventory.

It would be great if we could check the OEM Windows license in the UEFI for asset management, OS Deployment and reports.
My scenario is thousands of computers with OEM licenses comprising all from Windows Vista to Windows 10.
To help the deployment of Windows 10 in the company we have bought hundreds of Windows 10 licenses.
Therefore, we have to maintain a list of these licenses and the computers they are given to.
I have a task sequence that checks the OEM license for Windows 10 in the UEFI and in a SQL database and then selects to install either Windows 10 or Windows 7 dependent on the available license for the current machine.
For the OEM check I use a little program from Github, ShowKeyPlus, that can return the product the OEM license key is for.
This TS is just to make it easier for IT support staff and the users to reinstall the OS without licensing mistakes.
Having this check directly in SCCM would be marvelous.
It could be used for asset management, OS deployment, reporting etc.
Having the option to import licenses and assign them to computers would be top notch too.