An inventory is only true on the day it was taken — unless something keeps re-taking it. Endpoint Central's agent-driven scans do exactly that. Here is the rhythm that keeps your hardware data honest.
Every office has had the spreadsheet: ninety careful rows of laptops, models and RAM sizes — accurate for exactly one afternoon. Then someone upgraded a disk, a PC was replaced, and the sheet became fiction that still gets quoted in meetings. Agent-based inventory does not rot the same way, because the record is re-read from the machine on a rhythm instead of being typed once by a human. This guide explains how that freshness actually works in Endpoint Central, what can still make records go stale, and the small habits that keep the console trustworthy.
Each managed PC's agent performs inventory scans and reports the results to the Endpoint Central server. Hardware inventory — processor, memory, disks, BIOS, network cards — and the full installed-software list are re-collected, not assumed. When the agent contacts the server, the record updates. You can also trigger a scan on demand from the console when you need an answer now — before a purchase meeting, for example — instead of trusting whatever the last scheduled scan found. The practical effect: the console's picture of a machine is never older than its last successful scan, and that date is visible, so the data carries its own expiry label.
Freshness is mostly about matching the rhythm to how fast your office changes. For a typical office, a working pattern is:
None of this is heavy administration. It is fifteen minutes a month of reading a column most admins scroll past.
Three honest exceptions. A laptop that lives in a drawer cannot scan, so its record freezes at its last sighting — the data is not wrong, it is dated, and should be read that way. A broken agent stops reporting while the PC works happily, which is exactly why the last-scan column matters more than the record itself. And a PC that was replaced but never removed from the console leaves a ghost record that inflates every count. The freshness review catches all three — that is its whole job, and the case guide on missing devices below goes deeper on telling a sleeping laptop from a stolen one.
Once a quarter, pick five PCs at random, walk to them, and compare: the console's RAM figure against the machine, its disk size, its serial number against the sticker. Agent data is machine-read and almost always right — but the quarterly physical check is what lets you tell an auditor, or your owner, 'this inventory is verified', not just 'this inventory is automatic'. It also catches the one class of error automation cannot: two PCs swapped between desks, where every record is accurate and the map is still wrong.
See every screen from this guide live in the video — hardware inventory, software inventory, the License Manager and the alerts, on a real Endpoint Central console.
▶️ Watch Full VideoThe agent scans on its regular contact cycle with the server, and an administrator can also start an inventory scan on demand from the console for any machine that needs an immediate answer.
Not necessarily wrong — just dated. It shows the machine as it was at its last successful scan. Chase the machine first (drawer laptop, dead agent, retired PC), and read its record with the date attached until it reports again.
Because nobody removed it, and nothing can scan it to prove otherwise. Retired machines must be removed from the console deliberately — build that step into your disposal process so counts stay honest.