Omnissa Horizon 8.2106 EOL July 2024: 3 Options

Omnissa Horizon 8.2106 reaches end of life (EOL) on July 15, 2024 — roughly nine months from the date this post is written. This version is not an LTS release, and 8.2106 is the latest version in its line. After that date, Omnissa will no longer provide active support or security patches for this release.

Nine months is a realistic window to plan and execute any of three available paths: migrate or upgrade to a supported release, purchase vendor extended support (if offered), or transition to third-party maintenance. Each path has a distinct cost, risk, and timeline profile. Below is an honest comparison to help determine which option fits your environment.

Option 1: Migrate or Upgrade to a Supported Release

Cost profile: Licensing fees for a newer version, labor for planning, testing, and deployment, plus potential training costs if the new release introduces significant changes. Migration may also require upgrading underlying infrastructure (e.g., vSphere, connection servers).

Risk: Moderate. Compatibility issues between existing configurations and the new release, user downtime during cutover, and regression in custom scripts or integrations are the primary risks. A thorough test environment can mitigate these.

Timeline: Nine months is sufficient for most organizations if the project is scoped and resourced properly. An aggressive timeline (2–3 months) is possible for simple environments; complex deployments may need the full nine months.

Best suited for: Environments under active development, where new features (e.g., improved protocols, management tools) are valuable, or where compliance requires staying on a fully supported vendor release. Upgrading also eliminates the need to manage a support gap later.

Option 2: Vendor Extended Support

Cost profile: Typically premium – often 50–100% above standard support costs. The exact pricing and availability are determined by Omnissa and may vary by region or contract size. Extended support is usually offered in 1- or 2-year increments.

Risk: Low for the duration of the extension, as vendor patches (including security fixes) continue. However, extended support is temporary – it delays the eventual migration rather than solving it. Negotiations must begin before the EOL date.

Timeline: Requires action now to secure a contract. Once in place, it buys time without immediate pressure. The extension period is finite.

Best suited for: Organizations that need a short bridge to align migration with a broader IT refresh or budget cycle, or those that cannot complete an upgrade within nine months due to resource constraints or complex dependencies. Not a long-term solution.

Option 3: Third-Party Maintenance and Support

Cost profile: Generally lower than vendor extended support – often 40–60% less than the vendor’s standard support pricing. No licensing fees; you pay only for support. Contracts are flexible (monthly, annual) with no penalty for cancelling early.

Risk: Moderate. You will not receive new features or official vendor patches. However, a third-party provider can deliver root-cause analysis, workarounds, and custom fixes for bugs. Security posture depends on compensating controls (e.g., network segmentation, hardening) and the provider’s ability to backport critical patches from later releases when legally permissible.

Timeline: Can be engaged immediately and continues past the EOL date. There is no hard deadline for moving to third-party support – you can switch at any point before or after July 15, 2024.

Best suited for: Stable, mature environments that do not require new features – for example, a remote desktop fleet that is functioning well and will be replaced by a different solution in 1–3 years, or a compliance‑regulated environment where change is costly and the existing version is already certified. Also suitable for organizations that want to defer capital expenditure and manage support costs predictably.

Decision Checklist

Use the following questions to guide your choice:

• Is this environment under active development or planning to adopt new Horizon features? → Upgrade path.
• Can the upgrade be completed within nine months with available staff and budget? → Upgrade path.
• Does your compliance framework require vendor-supplied security patches? → Upgrade or vendor extended support.
• Is the environment stable, with no planned changes for 1–3 years? → Third-party support.
• Do you need to defer the upgrade cost to a later budget cycle? → Third-party support or vendor extended support.
• Can you begin vendor extended support negotiations immediately? → Vendor extended support (temporary bridge).

Conclusion

A nine-month runway gives IT teams real flexibility. If an upgrade is feasible, it remains the cleanest option for staying current. Vendor extended support buys time at a premium cost. Third-party maintenance offers a cost-effective way to keep a stable Horizon 8.2106 environment running safely past the EOL date, without forcing a rushed migration.

If you’d like to explore how third-party support could fit your Horizon environment, contact our team. We can provide a no-obligation comparison of coverage and pricing.