Software inventory

Software inventory needs application inventory turned on in Settings → General → Application inventory. Admins can open that setting from the Software inventory page. While application inventory is off, the Software inventory page shows that it’s turned off.

To see which applications are installed across your devices, open Software inventory in the sidebar. Admins, members, and auditors can open it. Each row is one application on one platform, with the number of devices that have it installed, the number of distinct versions, the latest version, and when we first saw it on a device. The counts cover devices in audit scope, and we refresh them within minutes of a device checking in.

Search by application name, and use the OS filter to show only some operating systems. Select a column header to sort by that column, and select it again to reverse the order. Versions sort part by part, so 1.10 comes after 1.9. Rows with nothing to sort by, such as an application whose version we don’t know, come last in either order. Select a row to open the application’s page, which lists each installed version with its device count, and the devices that have the application installed with the versions on each. Sort either list by its column headers the same way. Check one or more versions to narrow the device list to the devices with any of them, and select Clear to see every device again. Admins and auditors can select a device to open its page.

Admins can check devices in the list to act on them together, the same way as on the Devices page. With Oneleet MDM, that includes Install applications, so you can check the devices on an old version and install the current one from your app catalog.

Select Export to download the rows loaded so far as a CSV file. The list loads more rows as you scroll, so scroll further down first to export a longer list.

If a Windows device cannot refresh its packaged apps after an agent restart, we keep their last known device counts while processing partial inventories. We stop retaining those rows when a later inventory update is processed more than a day after the last complete collection time reported by the device. This is not a fixed expiration deadline: unchanged inventories can take another day to upload, offline devices take longer, and an incorrect device clock can shorten or extend retention. Registry application changes still update during that time. The collection time stays at the last complete inventory until the package query succeeds again.