Life is like a box of Enhanced Device Inventory Properties.

Patch My Pc | install & update thousands of apps

This blog will focus on Enhanced Device Inventory (Resource Explorer) and how this new Intune Core Feature will greatly enhance the reporting functionalities we now have in Intune.

Introduction

Say hello to Intune’s shiny new Enhanced Device Inventory (Resource Explorer) feature!

Enhanced Device Inventory Resource Explorer

This brilliant addition is here to make our lives as IT admins much easier by delivering a daily snapshot of device properties like TPM, CPU, and logical drive values.

Unlike the Device Query feature, which is great for live troubleshooting, Device Inventory takes a much more laid-back approach. Instead of firing off a remote query to get the latest details, it automatically collects and uploads the information to the Inventory service once a day. You heard that right, no more running live queries whenever you want to check on your devices. The data is already there, and we are waiting for you in the Resource Explorer.

And for the Configuration Manager veterans out there, does “Resource Explorer” ring a bell? If you’re getting déjà vu, you’re not alone. Using Resource Explorer, you can view the data collected by the hardware inventory uploaded for Configuration Manager devices. Looking at the resource explorer default classes, I am beginning to expect that it’s the same thing as we noticed with Intune Pivot / CMPivot Device Query.

resource explorer in sccm SYSTEM Center Configuration Manager

Microsoft seems to have taken some of the best bits of ConfigMgr’s hardware inventory and reimagined them for Intune. The result? A modern, cloud-first solution that finally bridges the gap between traditional on-prem tools and the Intune experience.

Let’s take a look at how we could configure the required policy to ensure the Resource Explorer is showing the data we need!

Configuring the Properties catalog

Now, with that out of the way, let’s get into the nitty-gritty of setting this up. To make the most of Enhanced Device Inventory, you’ll need to create a Properties Catalog profile. To do so, you need to create a new policy first

Configuring a new policy to setup enhanced device inventory

From there on, you can select the new Profile type called: “Properties Catalog“. This new profile type lets you choose which device properties you want to track. (again if the properties catalog doesn’t show up, your tenant is NOT yet flighted)

selecting the properties catalog to start creating the settings profile for device inventory

After selecting the proper profile, we need to define the properties themselves. Here’s the weird part: all properties are disabled by default. That means you get to pick exactly what you want to monitor. TPM? CPU? Logical drives? The choice is yours; just select them all using the properties picker.

after selecting the properties catalog , we need to configure which properties/entities we want to harvest. We can do so by selecting all properties with the properties picker

Once you’ve selected your desired properties, Intune will remind you that the data refreshes every 24 hours. Assign the policy to a test group of devices, and you’re off to the races!

it mentions that the device inventory data will be refreshed eery 24 hours

After the refresh overview, let’s scope it to a subset of devices to test with. After assigning it to your devices, you notice you don’t have a report.

Please Note: A quick heads-up: there’s currently no way to track the policy’s status directly. But once it’s applied, you can open the Resource Explorer for a device and start exploring the juicy details you configured. For example, if you have enabled the TPM properties, you’ll see all the relevant data in the resource explorer.

we can take a look at the device its harvested properties by clicking on the device and opening the resource explorer

As we noticed when configuring the policy, this data is refreshed every 24 hours by default and stays in the service for 28 days. When we slide to the right, we can also see when it was last refreshed, which is pretty important if you ask me! We want to know what we are looking at and how old it is!

device inventory data last refresh time stamp

Why Enhanced Device Inventory Is a Game-Changer

At this point, you might be wondering: “Why should I care about this when we already have Device Query?” Great question, let’s break it down.

Device Query is your go-to tool for live troubleshooting. It’s fantastic when you need instant answers about a specific device, whether you’re checking TPM status, CPU specs, or other properties. But here’s the catch: if you’re managing hundreds (or even thousands) of devices, manually querying each one becomes a logistical nightmare.

That’s where Enhanced Device Inventory steps in. Instead of running queries one by one, Device Inventory automatically gathers and uploads the data for you every 24 hours. This data is stored for 28 days, meaning you can hop into the Resource Explorer whenever you want and find the information you need—no delays, no manual effort, no fuss.

Plus, you’re not left wondering how stale the data might be. That “Last Refreshed” timestamp gives you peace of mind, showing exactly how fresh your data is.

Here’s the twist, though: right now, Enhanced Device Inventory is still tied to individual devices. To view the data, you’ll need to open the Resource Explorer for each device separately. But… could something bigger be on the horizon? Imagine being able to query this rich dataset across your entire fleet without diving into individual devices. Owww wait:

A consolidated view like that would truly take Device Inventory to the next level. Intriguing, right? Stay tuned, there might be more to this story than meets the eye!

Real-World Use Cases

Now, let’s talk about why this feature matters. Here are just a few examples of what you can do with Device Inventory:

  • Identify devices without a TPM to enforce compliance with security policies.
  • Find devices with specific CPU models to ensure they meet the requirements for upcoming upgrades.
  • Monitor storage capacity on logical drives to prevent devices from running out of space.

In other words, this isn’t just a shiny new toy,it’s a powerful tool to make your job easier and your device fleet more manageable.

The Device Inventory Agent

What’s the secret sauce behind this feature? Meet the Device Inventory Agent, a new addition that automatically installs when you target a device with the Properties Catalog policy. This little helper works in the background, collecting data using WMI and sending it to the Inventory service.

If you’re curious about the magic behind this agent, how it installs, how it communicates with the service, and all the juicy details, take a look at this blog! I’ll take you on a deep dive into the agent and its inner workings.

Dealing with the 2147749902 Properties Catalog error

If you deployed the properties catalog policy to your devices and it ends up with the 2147749902 error status

2147749902 error in the properties catalog report of device invenvtory

You will need to read this additional blog, which shows you how to fix it and what the culprit was!

Conclusion:

In a nutshell, Enhanced Device Inventory takes reporting in Intune to a whole new level. Automating daily uploads of key device properties saves you time, reduces complexity, and makes getting the insights you need easier than ever.

As Microsoft noted in their announcement, this feature builds on the foundation of Configuration Manager’s Resource Explorer and reimagines it for the cloud. You’ll always have up-to-date data with the Device Inventory Agent pulling the data for you.

And remember: “Life is like a box of Enhanced Device Inventory properties“. With the right tools, you can access all the information you need to do your job!

17 thoughts on “Life is like a box of Enhanced Device Inventory Properties.

    1. Hi.. could you share some more information? are you noticing this at the properties catalog profile you configured or?

      1. No OP but I am also getting the same message when I check the deployment status for a device.

        In my policy I did tick every property available.

  1. It’s a great functionality, but it’s extremely frustrating that you can only view the results on an individual device basis. Collecting all of this useful inventory information and then hiding the aggregated data behind the paid Advanced Analytics option stinks of a cash grab.

  2. Thanks for the blog post! I have a quick question – When I view Resource Explorer for any device, I see ALL the options listed as columns, including the items I did not select. Is this normal? I know I can adjust what columns I see on each page, but that isn’t permanent and makes the whole thing kind of ugly.

  3. Like others, I was seeing the 2147749902 error on deployment to our test group but it has since resolved 24hours later. Prehaps a sync issue pending the agent install or a general sync issue.

    The remaining errors so far on the same models are
    Instance Name, Design Capacity and Manufacturer Error 2147746132 on one Machine
    Full Charged Capacity, Cycle Count, Instance Name, Manufacturer, Manufacturer(again?) Error 2147943515

    I suspect these will resolve as the machines are rebooted. I’ve pinged the users to reboot and will update when I can

  4. I’m also unable to deploy my newly created device properties catalog profile to a test device group. The profile report shows error 2147749902 on all devices and for every setting (i have selected all available properties from the catalog).
    I inspected one of the devices in my test group. I can see the folder “C:\Program Files\Microsoft Device Inventory Agent” with the two subfolders “InventoryService” and “Logs”. There is no subfolder “InventoryAdaptor”. In the subfolder “InventoryService” there is an empty (zero-byte) file InventoryServiceHarvesterDatabase.sqlite. In the Logs subfolder there is a regularly updated log file. The log file only contains the following recurring error:

    13.12.2024 08:26:11 [Exception] Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: ‘no such table: InventoryEventCollector’.

    I guess the intune profile fails to even install the inventory agent.

    1. Update: I’ve found the reason for why the inventory agent is not properly installed on my test devices. It’s because the MSI fails when it tries to start the inventory service. I tried to install the MSI manually with a local administrator. It results in the same error. The service itself is installed, but it cannot be started (error 1053: the service did not respond to the start or control request in a timely fashion). At that point the MSI installer fails in silent mode and performs a rollback, leaving just some files in the program files directory.

      1. Yep :).. it looks like its something that is already installed on the device that breaks the msi.. The msi log will show you 1920… but nothing more.. trying to manually register the cim provider of the mof file doesnt work as it alreadu breaks just before

Leave a Reply

Your email address will not be published. Required fields are marked *

  −  1  =  4

Proudly powered by WordPress | Theme: Wanderz Blog by Crimson Themes.