You can’t patch what you can’t see.

When an update goes wrong, the post-mortem usually starts with the same discovery: nobody knew that machine was there. It was under a desk, or in a cabinet at a branch, or running a single task nobody had thought about in years. It didn’t get the update because it wasn’t on the list. There wasn’t really a list.

Updates, security fixes, licence renewals, hardware refreshes — all of them assume you know what you have. Most businesses know roughly. Roughly is where the surprises live.

Start with what already answers

The good news is that most of your environment is already telling you it exists. Devices sign in to the network. Laptops check in with whatever manages them. Servers report to monitoring. Phones enrol for email. Each of these is a partial inventory.

Start there. Pull the list from every system that sees devices and merge them on the things they share: a serial number, a hostname, a network address. The first merge will be messy, with duplicates and strays. That mess is information: every device that appears in one list and not another is a question worth asking.

A week, not a project

An inventory doesn’t need to be perfect to be useful, and it will never be finished. Aim for a week:

• Days one and two: export and merge what already reports in.
• Day three: chase the strays — anything seen by the network but not managed.
• Day four: give every device an owner, even if the owner is “the branch office”.
• Day five: decide what happens to the ones nobody claims.

At the end of the week you won’t have everything, but you will have most things, and you will know where the gaps are. That is already better than most.

The four columns that matter

It is tempting to record everything. Resist it. An inventory is only as useful as the questions it answers, and most questions need just four things:

1. Owner — who to ask about it.
2. Place — where it physically is, or which site it serves.
3. Last seen — when it last reported in.
4. Update state — how far behind it is.

With those four, you can answer “what hasn’t checked in for a month?”, “what is behind on updates at the warehouse?” and “who do I call about this?”. Everything else is detail you can add when a real question needs it.

Keep it true

The hard part isn’t building the inventory; it’s keeping it true. A spreadsheet updated by hand is accurate for about a fortnight.

So make the inventory maintain itself. New devices should enrol into management as part of being set up, not afterwards. Devices that stop reporting should raise a flag after a set number of days. Devices that leave the business should be retired in the inventory as part of leaving.

Once the list keeps itself, updates stop being a scramble. You know what needs them, where it is and who owns it — and the machine under the desk is on the list.