IBM ILMT deployment. The 2026 sub capacity guide.

ILMT decides whether IBM bills 16 cores or 200. This guide covers the six deployment steps, the four contractual requirements, and the quarterly cadence that keeps sub capacity eligibility alive.

Why does ILMT decide what your IBM estate costs?

ILMT is the contractual gate to sub capacity licensing, and sub capacity is routinely the difference between paying for 16 cores and paying for 200. The IBM sub capacity terms require an eligible tool deployed, configured, and reporting; without it, full physical capacity applies.

That makes ILMT a financial control, not a SAM hygiene item. A single uncovered VMware cluster can swing seven figures of PVU exposure.

The four contractual requirements

• Deploy within 90 days of the first eligible sub capacity product, per the Passport Advantage program rules.
• Cover every eligible host, including virtualization managers, not just the VMs running IBM software.
• Generate quarterly reports and retain them for two years.
• Keep the catalog current so bundled and supporting components classify correctly.

How do you deploy ILMT correctly in 2026?

A correct deployment is a six step sequence: server build, agent rollout, VM manager connections, catalog classification, report validation, and operational handover. Most failed estates skipped step three or six. The ILMT documentation covers mechanics; the sequence below covers survival.

Steps one to three: infrastructure

1. Build the ILMT server on a supported stack and size the database for your endpoint count.
2. Roll out agents through your standard software distribution, with acquisition and DMZ estates explicitly in scope.
3. Connect VM managers. vCenter and other hypervisor connections let ILMT see physical capacity; without them sub capacity math fails.

Steps four to six: data quality

1. Classify the catalog. Confirm bundled components map to their parent entitlements instead of billing standalone.
2. Validate the first quarterly report against a manual count on a sample of hosts.
3. Hand over to operations with a named owner, a quarterly review meeting, and an agent coverage KPI.

How do you keep ILMT audit ready after go live?

Audit readiness is a quarterly cadence, not a deployment artifact. The estates that pass audits without drama review the report, the coverage KPI, and the catalog version every quarter, and they archive the signed report the same day.

Treat agent coverage below 98 percent as an incident. Every uncovered eligible host is a full capacity claim waiting for an audit letter.

Which evidence the auditors actually request

Expect requests for the quarterly report archive, agent coverage proof, and catalog versions, mapped against the ILMT configuration documentation. The report history is the exhibit; the install is assumed.

Where the common advice on ILMT is wrong

The standard advice is that deploying ILMT is the finish line, and many SAM teams celebrate at go live. We disagree. In roughly 18 of the 25 ILMT remediation projects Morten Andersen ran in 2024 to 2025, the tool was installed and technically working; what failed was operations. Catalogs aged, acquisitions never entered scope, and reports sat ungenerated for quarters, which voided sub capacity eligibility exactly as if the tool were absent. The buyer side move is to fund the quarterly operating cadence with the same seriousness as the deployment project, because IBM audits test the report history, not the install date.

IBM does not audit whether you installed ILMT. It audits whether ILMT was telling the truth every quarter for the last two years.

What to do next

1. Inventory every host running PVU or VPC licensed IBM software, including acquisitions.
2. Verify agent coverage against that inventory and treat gaps as incidents.
3. Confirm VM manager connections exist for every hypervisor platform in scope.
4. Update the software catalog and reclassify bundled components.
5. Generate and validate this quarter's report against a manual sample.
6. Name a report owner and put the quarterly review on the calendar.
7. Archive two years of signed reports where an audit response team can find them.

Pair this guide with the ILMT sub capacity guide, the wider IBM knowledge hub, or an estate review with the IBM advisory practice.

Related advisory: Start with our IBM audit defense playbook, engage the IBM audit defense service, and prepare for IBM audit negotiations before the settlement phase.

Frequently asked questions

Is ILMT required for IBM sub capacity licensing?

Yes, with narrow exceptions for very small estates and approved alternative tools. The sub capacity terms require an eligible tool deployed, configured, and generating retained quarterly reports; otherwise full capacity applies.

How quickly must ILMT be deployed?

Within 90 days of deploying your first sub capacity eligible product under Passport Advantage. Late deployment risks full capacity assessment for the uncovered period.

Why does ILMT need a VM manager connection?

Because sub capacity math compares virtual cores to physical capacity. Without vCenter or equivalent hypervisor visibility, ILMT cannot see physical capacity and the calculation, and your eligibility, fails.

How often should ILMT reports be generated and reviewed?

Quarterly at minimum, with two years of reports retained. Generate, validate against a host sample, have the named owner sign off, and archive the same day.

What agent coverage level is acceptable?

We hold estates to 98 percent or better of eligible hosts. Every uncovered host is exposed to full capacity billing, so coverage gaps are incidents, not backlog items.