Reclaiming hardware and licences that nobody is using is the cheapest saving available to an IT team. What it takes is metering you can trust, a policy people will accept, and an inventory that actually finds everything.
Your IT assets, hardware and software both, represent a significant investment. Like any investment, you want them properly managed and used to the full. A large and frequently ignored part of that is licence reharvesting: reclaiming assets that are no longer in use, or no longer needed for the purpose they were bought for.
It is the cheapest saving available to an IT team, because you have already paid for everything involved.
The obvious benefit is cost. Where reclaimed equipment is still current, it goes back into circulation. Where it is not, it can be stripped for parts — processor, memory, storage — to repair and upgrade other machines.
There is also a deadline case. If hardware was financed and the agreement has reached its end, it has to go back, and failing to return it costs money for nothing. Knowing which devices are on which agreement, and when each one expires, is an inventory problem before it is a procurement one.
Then you look at what is installed on the device you have just reclaimed.
On most reclaimed hardware, the licences are worth more than the metal. So reharvest them, reconcile them, and make them available for reuse elsewhere.
That does three things. It keeps you compliant, because a licence that is recorded as available is one you can prove is not being consumed twice. It reduces what you have to buy next, because demand gets met from stock before it gets met from a purchase order. And it reduces maintenance and support costs, because those are usually charged against your installed base rather than your active users.
In CerteroX SAM this is the Effective Licence Position doing its job: purchased, used, available, required, variance and exposure, calculated continuously rather than assembled in the week an audit letter arrives. A harvested licence shows up as available quantity immediately, which is what turns a reclamation exercise into an avoided purchase.
Reharvesting is not limited to hardware you get back. It also applies to software sitting on a machine that someone is using every day — where the machine is in use and the software on it is not.
To do that you need usage metering you can defend, because you are going to take something away from somebody on the strength of it. In CerteroX SAM that is AppsMonitor: file-based metering that records first-used and last-used dates per title per device, and a % Used utilisation metric calculated over a rolling 90-day window. Remote and streamed sessions are counted too, so Terminal Server and RDS usage is attributed to the right device rather than lost.
The output of that is a defensible list: this title, this device, this user, not opened since March. Where a title should never have been in the count in the first place — MSDN rights, development and training machines, second-use devices — the Exclude From Licensing workflow takes it out of the calculation rather than having someone maintain the exception in a spreadsheet.
Cost is the reason reharvesting gets approved. Security is often the better argument.
Unpatched machines running old software are a real way in. Left connected to the corporate network, they are exposed to everything that scans for known versions — and old software that nobody uses is exactly the software nobody notices is out of date. Reclaiming those installs removes the risk and recovers the licence in the same action.
Software recognition in CerteroX carries release, end-of-support and extended support dates alongside the title, so the list of installs nobody uses and the list of installs nobody should be running overlap far more than people expect.
Having decided reclamation is worth doing, how do you actually do it? You need to know what is out there, and that is an IT asset management problem. You cannot reharvest from a device you have no record of, and the devices that never touch the network are precisely the ones that go missing from the record.
CerteroX ITAM approaches that from ten directions: the native agent across Windows, macOS, Linux, AIX, HP-UX and Solaris; Network Discovery sweeping a class-C subnet in under five seconds over NetBIOS, SNMP and ICMP; agentless and command-line collection for locked-down machines; standalone inventory for air-gapped systems; Active Directory import; and cloud and SaaS connectors. All of it lands in one schema. Duplicate system detection and stale device archiving keep the number honest, which matters here — reharvesting against an inflated device list produces an inflated saving.
Once you can see it, reclamation can be policy-based or voluntary.
If you go voluntary, an amnesty works well for hardware. Publicise it through whatever channels people actually read, make returning something easier than keeping it, and a surprising amount comes back in a fortnight.
Software on machines in use is more contentious and needs rules agreed in advance. Do you ask the user before removing something they have not opened in 60 or 90 days, or do you simply remove it? There is no universally right answer, and the deciding factors are mostly not technical.
The single thing that most changes how people react is how hard it is to get software back.
If there is a self-service portal where someone can request a title and have it approved and installed quickly, they are far less bothered about an unused copy being removed. CerteroX ITAM includes App-Centre for exactly this, with manager approval chains, and software distribution behind it for MSI, EXE and Click-to-Run packages — so the reinstall is a request, not a ticket that sits for a week.
If software is hard to obtain, people will object loudly to it being taken away, even software they have not touched in a year. This sounds perverse, but it is just human nature: most people do not want something until they are told they cannot have it. Where that is the situation, ask first. An email explaining what you are doing and why usually gets agreement, and it costs you nothing.
Fix the supply problem and the reclamation problem gets easier on its own.
When this article was first written, reharvesting meant desktop software on reclaimed PCs. The principle has not changed. The surface area has.
SaaS seats. This is now where most of the recoverable money is. 46% of the SaaS licences bought go unused — the average organisation uses 54% of what it pays for. CerteroX SaaS Management flags licences with 30 or more days of zero usage across 47 vendor connectors, and offers the action alongside the finding: reclaim, reassign, downgrade the tier, archive, remind the user, or dismiss it with a reason. Bulk deprovisioning handles the multi-select case, and the offboarding checklist tracks every licence a departed user still holds, with the revocation status per connector and the monthly cost of whatever is still open.
Cloud resources. The same idea applied to infrastructure. CerteroX Cloud Management runs twenty-six named checks, several of which are reharvesting in all but name: volumes long unattached, instances stopped but not deallocated, abandoned load balancers and buckets, obsolete images, IP addresses and snapshot chains. Across cloud environments under management the average saving is 38%.
AI seats. The newest line item, and the one growing fastest. AI subscriptions are reclaimed through the same licence engine as everything else in CerteroX SaaS Management, which matters because AI seats are frequently bought by a team, used enthusiastically for six weeks, and then billed indefinitely.
The tooling and the process are the point. You need to identify the asset, prove it is not being used, act on that, and record what you did — across hardware, software, SaaS, cloud and AI, from one place, off one data model.
Want to see reclamation run end to end, from thirty days of zero usage to the seat back in the pool? Book a demo, or talk to us.
Other posts covering the same ground.
Before optimisation, rationalisation or audit defence, most organisations need something less glamorous: a trustworthy answer to what they actually own. Why the foundational phase deserves its own name — and what counts as "stuff" now that most of it never touches your network.
Discovery and inventory are not the same thing, and most tools that claim the first are only good at the second. Six criteria for choosing between them, and why "good enough" coverage stops being good enough the moment anyone outside SAM uses your data.
Providers compete on the size of their normalisation database. Size is the wrong measure. What decides whether recognition is any good is how each entry got there.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.