Horizon. VDI is licensed twice.

Horizon is the VMware product most often double-counted in a Broadcom audit. The combination of concurrent-versus-named-user metrics, the infrastructure layer running ESXi underneath, and the Universal SKU bundles produces audit findings on almost every VDI estate we have assessed. We assess, defend, and negotiate the Horizon environment.

How Horizon licensing is structured.

Horizon is sold under two primary metrics: concurrent user (CCU) and named user (NU). The CCU metric counts simultaneous active sessions; the NU metric counts uniquely assigned users regardless of whether they are connected. The pricing differs, and so does the audit treatment. Most enterprises buy CCU, then accumulate named accounts that exceed the contract assumption over time.

Horizon also has multiple editions — Standard, Advanced, Enterprise — and the Universal SKU which spans cloud and on-prem. Universal carries its own attribution rules in audit that frequently surprise the buyer who purchased it as a flexibility play.

What auditors look at in Horizon.

The Horizon audit pulls the Connection Server inventory, the View Composer or Instant Clone history, the entitlement records by pool, the unique-user telemetry from event logs, and concurrent session peak data over the audit period. They reconstruct both the concurrent-session and named-user counts against the entitlement on file.

Buyers often discover the named-user count is multiples of the contracted concurrent number, because dormant accounts are never reaped. Even with a CCU contract, the auditor will often raise the named exposure as a separate finding for the negotiation.

Three Horizon audit traps.

Dormant named accounts in entitlement pools

Users assigned to a desktop pool but no longer active continue to count under the named-user metric and inflate the peak count under the concurrent metric on the day of audit reconstruction.

Underlying vSphere not separately licensed

Horizon entitles a limited vSphere Desktop edition for the hosts that run the VDI workload. Buyers running a general vSphere edition underneath their Horizon farm sometimes appear non-compliant under both products.

Universal SKU attribution across regions

Horizon Universal Subscription is treated as a single global pool. Deployments split across regions or affiliates that did not co-purchase Universal can produce attribution gaps the auditor will exploit.

Defences we use in Horizon engagements.

Horizon claims are usually disputed on the metric definition, the dormant-user reaping window, the underlying infrastructure entitlement, and the Universal SKU attribution. The defences below have all been used to reduce a real claim.

Concurrent versus named metric clarification

Dormant user reaping window and audit cut-off

Peak session methodology challenge

Edition reconciliation across Horizon Standard/Advanced/Enterprise

Horizon for vSphere Desktop entitlement coverage

Universal SKU global pool attribution

App Volumes and Dynamic Environment Manager carve-outs

RDS and published-app session attribution

Workspace ONE integration entitlement

Horizon Cloud Service treatment

Public cloud (VMC, AVS, GCVE) Horizon deployment

Multi-tenant service-provider exemption claims

Test, development, and pilot pool treatment

Education and not-for-profit pricing carve-outs

Decommissioned pool and clone evidence

Disaster recovery cold-standby exemption

Where Horizon savings tend to land

In documented Horizon engagements the largest single reduction usually comes from re-defining the dormant-user reaping window so that inactive accounts do not count against the entitlement. The second largest comes from carving the underlying ESXi infrastructure out of the Horizon claim by proving the Horizon-for-vSphere-Desktop entitlement covers the host. The third comes from rejecting peak-session methodology where the peak fell during a non-representative event such as DR failover testing.

Horizon licensing questions.

Which metric should we license under?

CCU is more expensive per unit but cheaper in total for most enterprises because concurrent peaks are typically 25-40% of the named population. The exception is a small power-user environment where named entitlement matches actual usage. The choice should be modelled, not assumed.

Do we need separate vSphere licences for the Horizon farm?

Horizon includes a Horizon-for-vSphere-Desktop entitlement covering the hosts running the VDI workload. General-purpose vSphere editions on the same hosts can create a double-entitlement question that needs to be resolved before audit.

What does Horizon Universal cover?

Universal is a subscription that spans on-prem Horizon and Horizon Cloud Service. The attribution rules across regions and affiliates are not symmetrical, and the SKU is frequently misinterpreted at point of sale.

Are App Volumes and Dynamic Environment Manager included?

In higher Horizon editions they are included. In lower editions they are separately licensable. Audit reconstruction frequently treats them as separate findings even when the buyer believes they are bundled.

Are we exposed if Horizon is decommissioned but still installed?

Yes, until the Connection Server inventory is fully removed. Installed-but-unused Horizon agents and pools continue to appear in the audit reconstruction. Documented decommission with contemporaneous evidence is the defence.

Horizon. VDI is licensed twice.

How Horizon licensing is structured.

What auditors look at in Horizon.

Three Horizon audit traps.

Defences we use in Horizon engagements.

Where Horizon savings tend to land

Horizon licensing questions.

Horizon in audit scope?
Don't reply alone.

Horizon. VDI is licensed twice.

How Horizon licensing is structured.

What auditors look at in Horizon.

Three Horizon audit traps.

Defences we use in Horizon engagements.

Where Horizon savings tend to land

Horizon licensing questions.

Horizon in audit scope?Don't reply alone.

Horizon in audit scope?
Don't reply alone.