Omnissa Horizon 8.2006 EOL: Action Plan

Omnissa Horizon 8.2006 End of Life on August 11, 2025 – What You Need to Do Now

Omnissa Horizon 8.2006 reaches end of life (EOL) on August 11, 2025 – roughly three months from today. This release is not an LTS version, and the latest (and only) build in this line is 8.2006 itself. After that date, vendor support, patches, and SLAs will cease entirely.

For most estates, a full migration to a newer Horizon release before August 11 is no longer realistic given the time and scope required. That doesn’t mean you’re out of options. The next few weeks are critical for protecting your environment, documenting your exposure, and securing a support path for the day after EOL.

What Actually Changes on August 11, 2025

On the EOL date, Omnissa (the vendor formerly known as VMware’s EUC business) will:

• Stop releasing security patches and bug fixes for Horizon 8.2006.
• Cease providing technical support and SLAs for any new issues.
• Remove the product from active lifecycle management.

Your Horizon environment will continue to run, but you will be operating without a safety net. Any new vulnerabilities discovered after August 11 will remain unpatched unless you have a third-party support arrangement in place. Auditors and cyber-insurance underwriters will view an unsupported, unpatched VDI deployment as a significant risk.

Your Week-by-Week Action Checklist

Time is short, so focus on four parallel workstreams: inventory, isolation, documentation, and support procurement. The plan below assumes you can start immediately.

Week(s)	Action	Owner / Notes
Week 1 (now)	Inventory all Horizon 8.2006 components: Connection Servers, Security Servers, App Volumes, DEM appliances, and any dependent agents. Tag them in your CMDB.	Infrastructure team
Week 2	Identify which Horizon workloads are business-critical and which could be isolated or decommissioned. Prioritise hardening of the remaining environment.	VDI admins, security team
Week 3	Begin isolating the 8.2006 environment: restrict inbound/outbound network access, apply strict firewall rules, and ensure only authorised admin accounts can reach the Horizon infrastructure.	Security team
Week 4	Document your exposure for internal auditors and cyber-insurance providers. Create a risk register entry that notes: Product: Omnissa Horizon 8.2006, EOL date: August 11, 2025, no vendor patches after that date, mitigation: [your planned third-party support or migration timeline].	Risk/compliance team
Week 5–6	Evaluate third-party support providers. Send RFPs or request NDA-reviewed proposals. Focus on providers that offer security patches, 24/7 TAC-style support, and flexible term lengths.	Procurement, IT director
Week 7–8	Finalise a third-party support contract before August 11. Ensure the agreement covers the entire Horizon 8.2006 stack and includes a clear escalation path.	Legal, procurement
Week 9–10	Final hardening pass for the Horizon environment. Remove unused agents, tighten credential policies, and verify backup/DR procedures operate independently of vendor support.	VDI ops, security
Week 11 (last week before EOL)	Confirm your third-party support contract is active as of August 11. Notify your team and your SOC that the environment is now under third-party maintenance.	IT director, SOC

Why Third-Party Support Is the Realistic Option Here

A full migration to a newer Horizon release – whether an LTS version or a subscription-based offering – typically takes four to six months for a moderately complex environment. With only three months left, the risk of rushing is higher than the risk of staying on 8.2006 – provided you have a qualified support partner.

Third-party maintenance for Omnissa Horizon can keep your production VDI environment running safely past the vendor’s EOL date. A reputable provider will:

• Supply security patches for critical vulnerabilities.
• Offer 24/7/365 engineering support for break-fix issues.
• Provide a contractual SLA that satisfies your compliance and insurance requirements.

This is not a “do nothing” strategy – it’s a deliberate risk management approach that buys you the time to plan a proper migration at your own pace, without the pressure of an arbitrary vendor deadline.

Next Steps

You have approximately 12 weeks. Use the checklist above to move forward immediately. If you haven’t yet started the procurement process for a third-party support contract, week 5 and 6 are your deadline – providers need onboarding time.

To discuss your specific Horizon 8.2006 environment and get a no-obligation quote for third-party support, contact our team today. We can help you build a bridge from August 11 to your eventual migration date.

---

Lifecycle data sourced from endoflife.date/horizon.