Horizon 8.2206 EOL After July 19, 2025

What Happened on July 19, 2025

Omnissa Horizon version 8.2206 — the latest release in the 8.2206 line — reached end of life on July 19, 2025. Both active support and security patch availability ended on that date. This release was not designated as a Long-Term Support (LTS) version, so the standard lifecycle applies: support stops for all customers who have not already migrated to a newer release.

If you are reading this after July 2025 and still have Horizon 8.2206 running, you are now operating a system that no longer receives vendor-provided bug fixes, security updates, or technical support from Omnissa.

What End of Life Means in Practice

What Stops Working (from Omnissa)

• Security patches: No new CVEs will be addressed by Omnissa for 8.2206.
• Bug fixes: Any defects discovered after the EOL date will not be patched.
• Vendor technical support: Omnissa will not accept support tickets, provide troubleshooting, or offer workarounds for 8.2206.
• New feature releases: The 8.2206 branch is frozen; no further updates are delivered.

What Still Works

• The software continues to run as-is. Connections, existing configurations, and agent functionality remain unchanged.
• Horizon Connection Server, Security Server, and agents for supported guest operating systems do not automatically break.
• Integration with Active Directory, vSphere, and other infrastructure that does not require a newer Horizon version will continue to function — until something changes (e.g., a vCenter update that drops compatibility with older Horizon releases).

Real Risks of Running Unsupported Horizon 8.2206

Security Exposure Without Patches

New vulnerabilities in Omnissa Horizon components are discovered periodically. After EOL, no vendor-provided mitigations exist. Attackers often target legacy VDI infrastructure because it is exposed to remote access and frequently handles sensitive data.

Compatibility Drift

Modern operating systems, browsers, and endpoint software may drop support for older Horizon agents or client versions. For example, newer Windows 11 feature updates or Linux kernel changes can cause unpredictable behavior.

Compliance & Insurance Implications

Many regulatory frameworks (PCI DSS, HIPAA, SOX) require that software running in production is under vendor support or has an equivalent maintenance agreement. Running EOL software may lead to audit findings or policy violations.

No Escalation Path for Critical Outages

If a kernel panic, memory leak, or database corruption occurs in the Horizon infrastructure, your internal team bears the full burden of root-cause analysis and workarounds — with no vendor escalation.

Who (Legitimately) Might Still Be on Horizon 8.2206?

Despite the risks, many enterprises remain on an older release for valid business reasons:

• Stable workloads: The environment works reliably, and the team prioritises avoiding change over gaining new features.
• Locked application dependencies: A legacy application or custom agent works only with Horizon 8.2206 and cannot be migrated without an expensive re-architecture.
• Hardware constraints: Older hypervisor hosts or unsupported CPU generations that are not certified with newer Horizon versions.
• Long certification cycles: Some regulated industries require months of re-validation after any software upgrade, making a timeline to migration unrealistic before EOL.

How Third-Party Support Keeps Horizon 8.2206 Maintained

Third-party maintenance providers, such as 3rd Party Support, can fill the gap left by Omnissa’s departure. Instead of paying for a forced migration or accepting full EOL risk, you can contract with an independent vendor to:

• Apply security patches and bug fixes backported to the 8.2206 codebase (where source-level fixes are feasible).
• Provide direct technical support for Horizon infrastructure, including troubleshooting, tuning, and root-cause analysis.
• Extend the usable life of your deployment — often at a fraction of the cost of a last Omnissa renewal.

Third-party support does not require you to upgrade your Horizon version. You keep your existing 8.2206 environment running safely while planning a more strategic migration on your own timeline.

Next Steps

If your organisation is still on Omnissa Horizon 8.2206 and you want to understand your support options, contact 3rd Party Support to discuss a custom maintenance plan. We can help you avoid rushed upgrades and maintain compliance without sacrificing stability.

---

Lifecycle data sourced from endoflife.date/horizon.