What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The most dependable way to manage software licenses is to run them as a recurring IT asset management (ITAM) process rather than a one-off clean-up. In practice that means assigning owners, setting approval rules, keeping an accurate inventory and entitlement record, reconciling what is installed or consumed against the applicable agreement, investigating exceptions, and reviewing renewals on a fixed schedule. Discovery and license tools can support the inventory and reporting, but the contract and the original purchase records remain the authority.
What managing software licenses actually involves
License management is a management system, not a spreadsheet or a network scanner. ISO/IEC 19770-1:2017 specifies requirements for an IT asset management system, and the ISO/IEC JTC 1/SC 7 committee describes it as a Plan-Do-Check-Act cycle covering 15 ITAM process areas. The standard applies to organizations of all sizes, but it is a framework to adapt to your organization rather than a deployment recipe to copy.
Good license management depends on two records that must be reconciled with each other. Discovery shows what is installed, running, or assigned. Entitlement records show what you are allowed to run, on what metric, and under which conditions. ISO/IEC 19770-2:2015 defines software identification tags, which help identify products, while ISO/IEC 19770-3:2016 defines an entitlement schema with common terms. Neither standard prescribes how your team performs the reconciliation; that work belongs to your process.
Free tools Windows power users keep installed
One-click scans. No signup required.
The agreement settles disputes. ISO/IEC 19770-3 states that the original licensing documentation takes precedence for legal purposes. A database entry, dashboard, or tool-generated position is a working record that should point back to the contract, not replace it.
#1 Best Overall
A seven-step method
The steps below follow the Plan-Do-Check-Act logic of ISO/IEC 19770-1. Each one produces evidence that the next step depends on, so skipping a step usually shows up later as a reconciliation error.
1. Set scope, ownership, and policy
Define what is in the program before counting anything. List the business units, geographies, cloud accounts, devices, servers, SaaS subscriptions, and software families that fall within scope. Name accountable owners across ITAM or software asset management (SAM), procurement, finance, security, legal, and system administration as needed. Then write the rules: who may request, approve, install, assign, transfer, and retire software, and what evidence each decision requires.
2. Build a trustworthy inventory
Discover installed applications and relevant infrastructure using endpoint, cloud, and service records. Normalize publisher, product, edition, version, deployment type, and the device or account each installation belongs to. Record where each data source came from and where collection has gaps, such as laptops that have not connected to the network for months or cloud accounts outside the scanning scope. An inventory without provenance is hard to defend in a vendor review.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute3. Build entitlement records from authoritative evidence
For every purchase or subscription, keep the agreement and any amendments, the order or invoice evidence, the product and edition, the quantity and license metric, the term, the renewal date, the rights and restrictions, and any assignment or transfer conditions. Normalized entitlement records make reporting easier, but any ambiguous point should be checked against the vendor’s original documentation before it drives a decision.
4. Reconcile against the actual license metric
Compare discovered installations, assignments, or consumption with the entitlements. The correct unit varies by product and contract, so do not assume a universal per-user or per-device count. Some products are licensed by physical core, some by virtual core, some by socket, and some by named user or subscription seat. Microsoft publishes product-specific requirements through its Licensing Guidance portal, and AWS License Manager tracks usage by vCPU, physical core, socket, or machine in its documented scenarios. Flag missing evidence, deployment mismatches, excess capacity, and unclear interpretations for human review rather than resolving them automatically.
5. Control the changes that consume rights
Connect license checks to procurement, access management, provisioning, cloud launch, and change processes where practical. The most effective control is preventing unauthorized consumption before it happens: restrict the operations that create license consumption to authorized users, and build approval steps into the request workflow. Automated rules are useful only when they accurately reflect the applicable agreement. AWS License Manager can apply hard or soft limits in its supported scenarios, but those limits do not interpret every external agreement on their own.
6. Review use, exceptions, renewals, and evidence
Set a review cadence that matches your risk and change volume. A fast-moving cloud estate may need monthly checks, while a stable on-premises estate may be reviewed quarterly. Each review should cover stale installations, assignment changes, low or unused capacity where reliable usage evidence exists, upcoming renewals, open exceptions, and unresolved contract questions. Keep the reports and approvals that support each decision so you can show how a conclusion was reached. Avoid promising savings percentages or audit outcomes that your own data does not support.
7. Improve the system over time
Data quality and process ownership come first. ISO/IEC JTC 1/SC 7 describes the progression as Trustworthy Data, then Lifecycle Integration, then Optimization. Lifecycle integration links license records to procurement, onboarding, offboarding, and retirement, so that a departing employee’s or retired server’s rights are released rather than forgotten. Optimization uses that clean history to make better purchasing and consolidation decisions. Teams that try to optimize before the data is trustworthy usually end up optimizing the wrong numbers.
Choosing an approach: spreadsheet, platform, or specialist
The right method depends on how many products, locations, and agreements you manage and how many people need to change records. The three common approaches differ mainly in where the effort goes.
| Approach | Useful when | Compare on |
|---|---|---|
| Controlled spreadsheet or registry | The software estate and contract set are small enough for named owners to keep current by hand | Data ownership, change history, review cadence, evidence links, access control, and error risk from manual entry |
| Dedicated SAM or license management platform | Discovery spans many endpoints, teams, cloud accounts, license metrics, or vendors | Product normalization, inventory sources, entitlement workflow, contract-specific rules, integrations, audit trails, reporting, security, and total operating effort |
| Specialist-supported program | Agreements, virtualization, cloud deployment, or vendor-specific metrics require expertise the internal team lacks | Independence, experience with the relevant vendors and deployment types, scope of work, evidence handling, conflict disclosures, and engagement terms |
These are evaluation criteria, not a ranking of named products. The ISO standards describe a management process, and the AWS material describes AWS’s own service capabilities. Neither is a neutral comparative test of commercial SAM products, so run a trial against your own inventory before committing.
Where a platform fits, and where it stops
AWS License Manager is a useful example of what a platform can automate. According to AWS documentation, it provides consolidated visibility and reporting for licenses across AWS regions and accounts, tracks licenses by vCPU, physical core, socket, or machine in its documented scenarios, and can discover certain applications on premises through AWS Systems Manager Inventory. It can then apply licensing rules to tracked resources.
Recommended Free Tools
Its scope has boundaries. Setup, supported sources, product coverage, and agreement-specific behavior need to be checked for your own environment. A platform that covers AWS workloads well may say little about a desktop application licensed per named user, and a rule that works for one contract may be wrong for a renewal with different terms.
Best Value
AWS Audit Manager also provides a prebuilt License Manager framework to support audit preparation with customer-defined licensing rules. AWS states explicitly that the framework’s controls are not intended to verify that systems comply with license rules. Treat it as preparation support, not as certification or legal assurance.
AWS describes three prerequisites for effective license management: “An expert understanding of language in enterprise licensing agreements; Appropriately restricted access to operations that consume licenses; Accurate tracking of license inventory.” Tools can support the last two. The first still requires people who can read the contract.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Standards and what they cover
- ISO/IEC 19770-1:2017, IT asset management systems — Requirements. Applies to IT asset types and organizations of all sizes. ISO lists it as reviewed and confirmed in 2024, and lists Amendment 1:2024. Check the ISO catalogue before citing edition details, because standards are revised over time.
- ISO/IEC 19770-2:2015, Software identification tag. Specifies software identification tags. It does not prescribe the ITAM processes needed to reconcile tags with entitlements.
- ISO/IEC 19770-3:2016, Entitlement schema. Describes common terms and a format for software entitlement information. Original licensing documentation takes precedence for legal purposes.
Common failure points and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Installed counts do not match purchased counts | Discovery gaps, such as devices that rarely connect, or unmanaged cloud accounts | Record collection gaps as data-quality findings, extend discovery scope, and mark unverified counts as provisional |
| A tool reports compliance but the vendor disagrees | The license rule in the tool does not match the contract’s metric or deployment terms | Compare the rule against the original agreement and amendments, then correct the rule and retain both versions |
| Renewal arrives with no one prepared | Renewal dates live in one person’s inbox rather than in the entitlement record | Store term and renewal dates in the entitlement record, and schedule review ahead of each notice window |
| Released licenses are not reclaimed | Offboarding and retirement steps do not touch license records | Link access removal and decommissioning tasks to entitlement updates |
| Installations appear without approval | Installation rights are not restricted or approvals are not logged | Limit installation to authorized roles and keep an approval record for each request |
Most of these failures trace back to the same gap: a record that is not tied to its source document or to a named owner. When a problem appears, start by checking which record is wrong and which document it should match.
Keeping the method current
Licensing terms change with product versions, vendor programs, and contract renewals, so the method needs a named owner who checks vendor documentation on each renewal and each major product change. Keep a dated log of the sources you relied on. That log is often the most useful evidence when someone later asks why a decision was made.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
