Windows Server 2016 Will No Longer Be Eligible for IBM Sub-Capacity Licensing Starting December 31, 2026

Windows Server 2016 Will No Longer Be Eligible for IBM Sub-Capacity Licensing Starting December 31, 2026 — What It Means for Your Business

IBM has officially announced that Microsoft Windows Server 2016 will be removed from the list of eligible sub-capacity technologies, effective December 31, 2026.

If your IBM software estate includes Windows Server 2016, this change can significantly impact your licensing position, audit exposure, and renewal costs.

Let’s break down what this means in simple terms.


What is IBM Sub-Capacity Licensing (and why does it matter)?

IBM Sub-Capacity licensing allows customers to license IBM software based on the resources allocated to a virtual machine (VM), rather than licensing the full physical capacity of the underlying host.

This is one of the biggest cost-saving mechanisms for IBM software running on virtual environments, but it only applies if your OS / virtualization technology remains eligible. IBM maintains this eligibility list and removes technologies over time.

What Changes After December 31, 2026?

If you are still running IBM software on Windows Server 2016 after that date, your environment may no longer qualify for sub-capacity licensing, meaning IBM would enforce Full-Capacity licensing.

In plain terms:

✅ Before (sub-capacity): You license only the VM capacity
❌ After (full-capacity): You may need to license the entire physical server capacity

Simple Example: PVU Impact (Sub-capacity vs Full-capacity)

Let’s assume you purchased IBM software using the well-known PVU (Processor Value Unit) metric.

  • Your IBM software runs on a VM with 4 vCPUs

  • That VM sits on a physical host with 16 cores

  • Under sub-capacity licensing, you only license the portion being used (4 vCPUs equivalent)

  • Under full-capacity licensing, you must license all 16 physical cores

Now assume:

  • 1 PVU = $1,000

  • A server core requires 70 PVUs per core

Before (Sub-capacity):

  • 4 cores × 70 PVUs = 280 PVUs

  • Cost = $280,000

After (Full-capacity):

  • 16 cores × 70 PVUs = 1,120 PVUs

  • Cost = $1,120,000

That’s a jump from $280K to $1.12M for a single server.

Now imagine this impact across your environment wherever IBM products are deployed on Windows Server 2016.

This Is Not Only About PVU, VPC Licensing Is Also Impacted

IBM’s full-capacity enforcement risk applies not only to PVU, but also to VPC (Virtual Processor Core) licensing.

Example: A single core of IBM DB2 on VPC can cost ~ $75K list price (varies per agreement).

  • Moving from sub-capacity requirement of 4 VPCs per server to full-capacity 16 VPCs per physical host shifts:

    • $300K per server → $1.2M per server

For many organizations, this is not a small compliance change, it’s a major financial risk.

How to Mitigate this Audit Risk?

1) Act fast — 12/31/2026 will arrive quicker than you think

Start planning now:

  • Identify where Windows Server 2016 exists in your IBM estate

  • Create a migration roadmap

  • Start internal RFCs / change approvals early

2) Keep IBM ILMT accurate and up to date

Your ability to prioritize the right systems depends heavily on visibility.
Keeping IBM License Metric Tool (ILMT) healthy ensures you can:

  • Identify high impact servers first

  • Measure sub-capacity usage correctly

  • Reduce “unknown” audit exposure

3) Work with an independent IBM licensing advisor

IBM compliance is complex, and many customers only discover this risk during an audit.

MooseTech Consulting works independently, with one goal:
Protect IBM customers, reduce audit exposure and optimize licensing costs

📩 Reach out to us at info@moosetechconsulting.com