Tivoli Endpoint Manager and BigFix licensing.

Tivoli Endpoint Manager became IBM BigFix, and BigFix later moved to HCL. That product history is now the licensing problem, because legacy IBM entitlements, resource based counts, and a change of vendor all sit on top of the same estate.

One product, several identities

The endpoint management product that many estates still run started life as Tivoli Endpoint Manager, was rebranded to IBM BigFix, and was subsequently transferred to HCL as part of the wider move of several IBM software products. For a buyer this means a single deployment can carry entitlements bought under the Tivoli name, the IBM BigFix name, and later HCL agreements. Each was acquired under different terms, and the boundary between what IBM still has standing to audit and what now belongs to a different vendor is exactly where confusion, and exposure, lives.

How it is licensed

Endpoint management of this kind is licensed against the resources it manages rather than against processor capacity. Entitlements are typically counted per managed client device or on a resource value basis, scaling with the number of endpoints under management. That makes the count a function of how many devices the platform touches, including servers and workstations that may have been brought under management without a matching entitlement.

• Endpoints brought under management over time without tracking the entitlement.
• Decommissioned or duplicate devices still counted as managed.
• Server and workstation entitlements mixed without separating the counts.
• Uncertainty over which entitlements are IBM legacy and which transferred to HCL.

Why the vendor transition matters under audit

When products move between vendors, the right to audit and the entitlements that apply move with the governing agreement, not with the software install. An IBM audit of an endpoint estate has to establish what remains under IBM contracts and what is governed elsewhere before any count can be fair. Buyers who cannot evidence which agreement covers which deployment are pressed to accept the broadest reading. Establishing the contractual boundary first is the core of the defense.

How we defend the position

We reconstruct the entitlement timeline across the Tivoli, IBM BigFix, and HCL phases, then reconcile the managed device count against what is genuinely in scope for the auditing party. Stale, duplicate, and out of scope endpoints come out of the count, and any residual is matched to the correct agreement. The work runs as audit defense: contain the data, reconcile the estate, challenge the assumptions, settle the remainder.