Omnissa Horizon 8.2106 EOL Action Plan (July 15, 2024)

Urgency Without Panic

Omnissa Horizon 8.2106 will reach end of life (EOL) on July 15, 2024. That date also marks the end of active support. For most estates, a complete migration to a newer release before then is no longer realistic — but you can still take meaningful steps in the remaining weeks to protect your environment and buy time for a planned upgrade.

This article focuses on what you can do: inventory affected systems, isolate and harden them, document risks for auditors and insurers, and line up a support contract that begins the day after EOL.

What Changes on July 15, 2024

On the EOL date, Omnissa will stop providing:

• Security patches
• Bug fixes
• Technical support and SLAs
• Knowledge base updates for this release

Omnissa Horizon 8.2106 is not an LTS release. The latest version in this line is 8.2106, so there is no further patch to install. After July 15, the product still runs, but it becomes unsupported software. Any new vulnerability discovered afterward will go unpatched by the vendor.

Your Last-Call Action Plan

With about three months left, follow this checklist to reduce risk and maintain compliance.

Weeks 1-2: Inventory and Assess

• Identify all production Horizon Connection Servers, replica servers, and security servers running 8.2106.
• Document all associated components: vCenter versions, ESXi hosts, View Composer databases, and third-party integrations.
• Determine dependencies: which applications and user groups rely on this Horizon pod.

Weeks 3-4: Isolate and Harden

• Restrict network access to management interfaces and security servers. Apply firewall rules to limit inbound traffic to known sources.
• Remove unnecessary protocols and services. Disable features you do not use (e.g., HTML Access, PCoIP if not needed in your environment).
• Verify that the latest available patch (for 8.2106) is applied. Check Omnissa's support portal for any last-minute hotfixes.
• Enable logging and monitoring for all Horizon components. Centralize logs for later forensic review.

Weeks 5-6: Document Exposure

• Create a risk register entry for the unsupported Horizon release. Note that no vendor security patches will be available after July 15.
• Share the risk register with your security team, internal audit, and cyber insurance carrier. Some policies require disclosure of unsupported software.
• Document compensating controls (firewall rules, MFA, IDS/IPS) that reduce the likelihood of exploitation.
• Update business continuity and disaster recovery plans to account for an unpatched Horizon environment.

Weeks 7-10: Secure Post-EOL Support

• Evaluate third-party support options that can cover Horizon 8.2106 after the vendor's EOL. A qualified provider can supply patches, fixes, and technical support for unsupported releases.
• Review contract terms: ensure coverage begins on July 15 (or July 16 at the latest) so that you have a support safety net from day one.
• Once a contract is in place, confirm escalation paths and response times with the provider.

Weeks 11-12: Final Checks

• Confirm that all monitoring and alerting is working. Test incident response procedures for a simulated Horizon outage.
• Perform a last inventory scan to catch any hidden instances (test labs, remote sites, DR replicas).
• Communicate the EOL status to all end-user groups and stakeholders. Manage expectations about support responsiveness.

The Role of Third-Party Support

If migrating away from Horizon 8.2106 by July 15 is not feasible, third-party maintenance can keep your environment safe and operational after the vendor's EOL date. Providers like Omnissa Horizon third-party support fill the gap by delivering patches, bug fixes, and expert assistance for releases that the vendor no longer supports. This lets you extend the life of your current deployment while you plan a migration at a realistic pace.

Next Steps

Start the inventory process today. Even a few weeks of structured action reduces the risk exposure on July 16. If you need help evaluating a post-EOL support arrangement, contact us to review your options.