LoadRunner Enterprise controller and load generator licensing

LoadRunner Enterprise distributes a performance test across a controller and a set of load generators, and the architecture invites a basic licensing error: charging for the machines rather than for the Vusers they run. The controller and load generator components are infrastructure, and the LoadRunner Enterprise license is sized by Vuser capacity, so a finding that counts servers overreaches against the metric the entitlement actually uses.

In a distributed performance test the controller orchestrates the run and the load generators produce the simulated traffic, spreading the virtual user load across several machines so that no single host has to generate all of it. That topology is an implementation detail of how the test is delivered, not a separate licensable quantity. The Vuser count is the metric, the peak number of simultaneous virtual users the test drives, and it is the same whether that load is generated by two machines or twenty. Because the EULA places compliance on the licensee, the buyer must be able to show that the components are infrastructure serving a Vuser entitlement, and that clarity is what keeps the finding tied to the right metric.

How LoadRunner Enterprise is actually licensed

LoadRunner Enterprise is licensed by Vuser, and the controller and load generators are the means of delivering that Vuser load, not units to be counted in their own right. Adding a load generator to spread the same total load across more machines does not increase the licensed requirement, because the requirement is the peak simultaneous Vuser figure, not the number of hosts. The defensible position establishes the Vuser capacity in the entitlement and the peak Vuser load actually run, and treats the controller and load generator inventory as the infrastructure that delivered it. The volume question itself, how the Vuser figure is counted, is addressed in how Vuser counting inflates a LoadRunner finding.

The error appears when a finding counts load generators as though each one carried a separate charge, or treats the controller as a licensable seat. A larger load generator pool may simply reflect a sensible architecture for distributing load, and it tells you nothing about the Vuser count, which is set by what the test drove at peak. Keeping infrastructure and metric separate is the core of the defense, and the peak figure rests on the same burst against sustained reasoning as how to scope LoadRunner Vuser bursts.

Where the LoadRunner Enterprise finding overstates

Load generators counted as separate charges

The clearest overcharge is treating each load generator as its own licensable unit. The number of generators reflects how load is distributed, not the Vuser requirement, which is set by peak simultaneous use, the figure examined in how Vuser counting inflates a LoadRunner finding.

Non production controllers and generators

Components that exist only in test or staging environments should not carry production licensing, the question addressed in LoadRunner non production and test environment scope.

Environment counts conflated with capacity

How many environments hold a controller and generators is a different question from the Vuser capacity, and letting one inflate the other double charges, the distinction set out in LoadRunner environment counts and license exposure.

How we defend a LoadRunner Enterprise finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take over the single controlled channel and ensure the deployment topology, the run results, and the entitlement records are captured together, because the metric argument depends on showing the components as infrastructure.

Reconstruct. We build the effective license position by establishing the Vuser capacity in the entitlement and the peak Vuser load actually run, and mapping the controller and load generators as the delivery infrastructure, before any vendor measurement script runs.

Rebut. We challenge every line that counts a controller or load generator as a licensable unit, that includes non production components, or that conflates environment counts with Vuser capacity. The finding falls back to the Vuser metric the license actually uses.

Resolve. We settle on the Vuser based count and, where it serves you, convert forward into an OpenPass agreement that records the Vuser metric and treats the controller and load generators as infrastructure, so a later review cannot recharge the machines.

An anonymised outcome

The reason the metric matters is the remedy behind the finding. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so charging for infrastructure rather than Vusers can multiply a finding well beyond the entitlement. Our anonymised case files show reductions of comparable scale across the estate, including a banking ArcSight finding reduced from $6.0M to $1.8M, a 70 percent reduction achieved by holding the count to the metric the license actually used. A LoadRunner Enterprise finding responds to the same discipline: separate infrastructure from the Vuser metric, and the machine charges come off.

Hold the count to the Vuser metric

The lasting lesson is that LoadRunner Enterprise is sized by Vuser capacity, and the controller and load generator architecture is the way that capacity is delivered, never a separate quantity to be counted. A buyer who establishes the peak Vuser load and treats the components as infrastructure holds the finding to the metric the entitlement uses. To carry the analysis further, read LoadRunner protocol bundles and license scope and the Vuser volume side in how to scope LoadRunner Vuser bursts. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If a LoadRunner Enterprise finding has charged for controllers or load generators, open a case.