Every managed IT provider says they track assets. Fewer can answer, today, how many laptops at a client are more than four years old and which servers run an OS that stops getting security updates next year. Those two questions are what an inventory is for.
This post covers what to record, how to keep it accurate without a full-time job, and the practical rules for deciding when hardware gets replaced rather than repaired.
What an inventory record needs
Keep it small enough that it stays correct. For each device: an asset tag, serial number, model, purchase date, warranty end date, assigned user or role, site, and the current OS version. The RMM agent can fill most of the technical fields automatically. The purchase and warranty dates come from the invoice, and you enter them once.
Add a status field with a short list of values: In service, Spare, Repair, Retired, Disposed. The moment a device changes hands or leaves the building, the record changes. If your tools do not sync, a shared spreadsheet that one person owns beats a fancy system nobody updates.
- Asset tag and serial number (the serial is the source of truth, the tag is for humans)
- Model, CPU generation, RAM, storage type and size
- Purchase date, warranty end date, vendor and invoice reference
- Assigned user, department, site, physical location for servers and network gear
- OS and firmware version, last check-in from the RMM
- Status and the date the status last changed
Get-CimInstance Win32_BIOS | Select-Object SerialNumber, Manufacturer, ReleaseDate
Get-CimInstance Win32_ComputerSystem | Select-Object Model, TotalPhysicalMemoryKeeping it accurate
Inventory rots at the edges: the laptop handed to a new hire without a ticket, the server decommissioned but never removed, the switch replaced during an outage at 2am. Fix that with two habits. First, every hardware change goes through a ticket, and closing the ticket requires updating the record. Second, reconcile quarterly: export the RMM device list, export the inventory, and diff them.
The diff catches devices in the RMM with no record (usually new purchases), records with no RMM check-in in 60 days (usually retired devices or ones sitting in a drawer), and mismatched users. Half a day per quarter keeps the whole thing trustworthy.
- Export the RMM device list with serial, last user and last check-in
- Export the inventory with serial and status
- Join on serial number; list devices present in one but not the other
- Chase each mismatch with a ticket: found, retired, or reassigned
- Update warranty dates from the vendor portal while you are there
When to refresh laptops and desktops
The honest answer is when the cost of keeping a device exceeds the cost of replacing it, and that includes the user's time. A laptop that takes three minutes to boot and drops Wi-Fi in meetings costs more than its replacement over a year. Set a policy age and treat it as a trigger for a review, not an automatic order.
Signals that a device should move up the list: out of warranty with a failed component, an OS that the vendor will stop supporting, a CPU that fails the requirements for the next Windows version, battery health below the point where it lasts a meeting, or a role change that needs more memory. Refresh in batches by site or department so imaging and shipping are efficient, and keep a small pool of spares so a failure never means a user waiting a week.
- Policy age reached (commonly four to five years for laptops, longer for desktops)
- Out of warranty and has already needed a repair
- Cannot run the next supported OS version
- Battery or storage health warnings from the RMM
- User role changed and the spec no longer fits
When to refresh servers and network gear
Servers are refreshed on support, not age. The vendor's hardware support end date and the OS end-of-support date are the two hard deadlines; write both into the record the day the server is deployed. Plan the replacement project to finish before the earlier of the two, because the last six months of support are when spare parts get scarce.
For each server refresh, ask first whether the workload should stay on hardware at all. Many file and application servers move cleanly to a hypervisor cluster or to a cloud service, and the refresh becomes a migration instead of a purchase. Network equipment follows the same rule: replace when the vendor stops shipping firmware fixes, not when it looks old. A ten-year-old switch with current firmware is fine. A three-year-old firewall with no more security updates is not.
Frequently asked questions
Do we need a dedicated asset management tool?
Not at first. The RMM plus a disciplined spreadsheet is enough for a few hundred devices. Move to a dedicated tool when you have multiple sites, multiple technicians and a need for audit history.
What happens to retired devices?
Wipe the drive with a documented method, record the wipe date and method against the asset, then recycle or resell through a vendor that gives a certificate. Keep the record; auditors ask.
Should spares be counted in the inventory?
Yes, with status Spare and a location. Spares that are not tracked walk away or sit unpatched for a year and then get handed to a new hire.
Takeaway
An inventory is a short record per device that is updated through tickets and reconciled against the RMM every quarter. Refresh laptops on a policy age plus health signals, and refresh servers and network gear on vendor support dates. Write those dates in on day one and the budget conversation happens a year early instead of during an outage.