This illustrative scenario shows how incomplete records can hide maintenance work, especially when one person manages company computers with limited IT support.
The fix is not more tools. It is treating device data the way you would treat any other business data: collect it consistently, check its quality, and measure results honestly.
Key Takeaways
- Check the device behind the record. A listed device still needs confirmation that it is enrolled, patched, and reachable.
- Gaps become a fix list. Old versions, stale check-ins, and unsupported systems each map to a check and an action.
- Verification closes the loop. Count devices confirmed at the required version and keep unknown devices visible.
Build an Inventory You Can Trust
An endpoint is a work device, such as a laptop or desktop, that connects to company systems. An inventory records what exists: devices, the software on them, and who uses them.
Endpoint management covers the actions taken to maintain those devices, including enrollment, updates, software removal, and configuration checks.
The Center for Internet Security (CIS) treats inventory as the starting point. CIS Control 1 ties an accurate asset inventory to identifying unauthorized and unmanaged assets so they can be removed or remediated.
CIS Safeguard 2.1 extends the same idea to software, calling for a detailed inventory of all licensed software installed on company assets.
A compact template with linked device and software records is enough to start. Use the following fields, and check which ones your tools already collect automatically:
- Stable device ID or serial number (for example, LT-0412)
- Assigned owner and whether the device is company or personally owned
- Operating system and version
- Application and version, one row per application
- Last inventory timestamp
- Management status (enrolled, pending, unmanaged, retired)
- Action owner for anything unresolved
Microsoft Intune offers a concrete reference point. Its All devices view shows how each device is managed, its compliance status, operating system details, and when it last checked in.
Keep credentials and recovery keys out of the sheet, and limit access to the staff who maintain it.
Reconcile the records
Compare the management tool's export against purchase and onboarding records, resolve duplicate IDs, and flag any device that has stopped reporting.
Then separate two timestamps: when a device last checked in and when its software inventory last refreshed.
Intune's device details documentation states that hardware and software inventory refreshes every seven days from the enrollment date.
That interval does not apply everywhere. Microsoft notes that Win32 app information collected through the Intune Management Extension refreshes every 24 hours.
Either way, a device that checked in yesterday can still carry software data that is several days old.
Once the fleet outgrows a side-by-side comparison, a short script can do the matching for you.
For small teams without dedicated IT staff, this kind of automation is part of building reliable tech support and infrastructure, where automatic patching across laptops is a core component, because repetitive checks across many machines are exactly where manual review breaks down.
Turn Inventory Gaps Into Targeted Fixes
Once the records are clean, the inventory becomes a fix list. Vulnerability management means identifying and addressing known weaknesses in installed software and operating systems. Patch management means applying the updates that address those weaknesses.
A version number identifies a candidate for investigation, so confirm the affected product, configuration, and vendor advisory before deciding what action it needs.
Exploitation evidence should shape the order. In an advisory sharing lessons learned from an incident response engagement, CISA lists prioritizing patches for critical vulnerabilities in public-facing systems and for known exploited vulnerabilities as a key action.
The agency tracks those flaws in its Known Exploited Vulnerabilities (KEV) catalog, which held 1,705 entries on September 10, 2026. CISA's directive for federal agencies, BOD 26-04, also weighs KEV status alongside whether an asset is publicly exposed.
Small teams can borrow that logic: combine exploitation evidence with applicability and business exposure, rather than relying on age or severity score alone.
| Signal | Check | Action |
|---|---|---|
| Old application version | Verify the affected version and vendor advisory | Pilot the update |
| Known exploited vulnerability on an affected device | Confirm applicability and business exposure | Prioritize remediation |
| Missing owner or stale check-in | Contact the responsible person and confirm management status | Investigate before closing |
| Unsupported operating system | Check edition and ESU status | Plan migration or a documented exception |
Operating system status needs the same care. Microsoft ended support for Windows 10 on October 14, 2025, but Long-Term Servicing Branch (LTSB) and Long-Term Servicing Channel (LTSC) editions follow separate lifecycle policies, and eligible devices can enroll in Extended Security Updates (ESU). Check the edition and ESU status before labeling a machine unsupported.
Test before widening the rollout
Start with a small pilot group. Microsoft's own Windows 11 migration guidance recommends assigning new policies to pilot groups, validating the results, and then scaling across the organization.
Agree on a maintenance window with the pilot owners, plan for reboots, and record the result for each device. Groups built from inventory criteria, such as every machine running a given application version, make the target explicit.
Endpoint management platforms can turn this workflow into a routine. PDQ, for example, identifies which vulnerabilities affect an environment, ranks what needs immediate attention using real-world threat intelligence, and lets teams deploy fixes right away or automate patching when new vulnerabilities are detected.
It also deploys operating system updates, applications, and scripts from a single dashboard and reports back on whether fixes installed successfully, which feeds directly into the verification step below.
Verify Progress With a Simple Device Dashboard
Verify the installed version after deployment. In Intune, discovered apps acts as a software inventory and is a separate report from app installation reports, which show total installs and failures.
Microsoft also warns that the two counts may not match, partly because they are collected at different intervals.
Use inventory data to check what is installed and deployment results to identify successes and failures. A useful dashboard needs both.
Three measures are enough to start tracking a small fleet. These formulas are suggested measures, not industry benchmarks:
- Management coverage = enrolled in-scope active devices ÷ all known in-scope active devices
- Verified patch coverage = devices verified at the required version ÷ all devices requiring that update
- Stale records = active device records older than your chosen freshness threshold
Keep offline and unknown devices in the denominator and report them on their own line. Remove a device from the active fleet count only when its retirement is confirmed and recorded, never because it stopped reporting.
Hypothetical example: 20 devices require an update. After the rollout, 16 are verified at the new version, 2 report failures, and 2 have not checked in.
Verified patch coverage is 80%, with four devices unresolved. Excluding the two that have not checked in would show 16 of 18, or roughly 89%, which overstates coverage and hides unfinished work.
Assign and review exceptions
CIS Control 7 frames vulnerability management as a continuous activity, and CIS Safeguard 2.3 asks teams to either remove unauthorized software or give it a documented exception, reviewed monthly or more often.
Hold a recurring review at a cadence that fits your risk, assign a named owner to every unresolved record, and note what changed since the last review. Repeat the pilot-then-expand step each time you deploy an update.
Give each failed or missing device a next action and a review date. Close the item only after a fresh check confirms the required version, or a documented exception explains why it remains unresolved.
Conclusion
Inventory data improves endpoint management only when it is treated as evidence rather than as a list. Clean the records first, separate check-in times from inventory refresh times, and rank fixes by exploitation evidence and exposure.
Then measure verified coverage with unknown devices left in plain view. That routine turns a monthly update report from a reassuring summary into an accurate picture of which machines are protected and which still need work.
FAQ
What is the difference between an IT inventory and endpoint management?
An inventory records what exists: devices, installed software, owners, and versions.
Endpoint management is the set of actions taken on those devices, such as enrollment, updates, software removal, and configuration checks.
The inventory tells you where work is needed, and endpoint management is how the work gets done.
How often does device inventory data refresh?
It depends on the tool and the data type. In Microsoft Intune, standard hardware and software inventory refreshes every seven days from enrollment, while Win32 app data collected through the Intune Management Extension refreshes every 24 hours. Check your own tool's documentation before setting a freshness threshold.
Should every high-severity vulnerability be patched first?
Not automatically. CISA recommends prioritizing known exploited vulnerabilities, and its federal guidance weighs exploitation evidence alongside public exposure.
Confirm the vulnerability applies to your configuration, then order fixes by exploitation evidence, exposure, and business impact.
Why keep offline devices in patch coverage numbers?
Removing them makes coverage look better than it is. A device that has not checked in may be unpatched, so it stays in the denominator until it is either verified or formally retired.