In today’s fast-paced digital landscape, maintaining a stable, predictable infrastructure for virtual desktops and applications can be challenging. Frequent updates, new features, and security considerations must be balanced against operational uptime and end-user experience. This is where Omnissa Horizon 8 Extended Service Branch (ESB) comes into play.
An Extended Service Branch (ESB) release aims to provide a stable and long-lived branch of Horizon, App Volumes, and Dynamic Environment Manager (DEM). In other words, it’s ideal for organizations that need to minimize disruptions and maintain consistent features over an extended period, while still receiving critical fixes and security patches.
Below, we’ll explore the fundamentals of Horizon 8 ESB, highlight the update timelines for Horizon, App Volumes, and DEM, and clarify some frequently asked questions about this extended support model.
Horizon 8 Extended Service Branch (ESB) Basics
1. ESB vs. Current Release (CR)
- Extended Service Branch (ESB): Receives periodic maintenance updates that focus on critical bug fixes, security patches, and updated Windows 10 & 11 support—with no new features added in these updates.
- Current Releases (CR): Offer frequent feature updates, improvements, and patches. Organizations that want the latest and greatest capabilities often opt for CR releases.
2. Release Cadence and Updates
- ESBs come out approximately once every 12 months.
- Each ESB gets at least three (3) scheduled maintenance updates (sometimes referred to as .1, .2, .3, etc.).
- Update 1: ~6–12 months after base version
- Update 2: ~15–21 months after base version
- Update 3: ~24–30 months after base version
These updates strictly include critical fixes (bugs and security) and ongoing support for new Windows 10 & 11 releases. No new Horizon features are introduced to an ESB mid-cycle.
3. Support Lifecycle
- Omnissa provides 3 years of General Support for Horizon 8 ESB versions.
- After 3 years, the ESB moves to the Technical Guidance phase for 1 year, meaning it still receives limited support but with fewer options for bug fixes or patches.
- The Omnissa Product Lifecycle Matrix details precise support dates and any extensions.
4. Interoperability and Licensing
- No special license is needed to access ESB releases—you can use the same license as Current Releases.
- You can switch between ESB and CR at any time as long as the version you’re upgrading to is released after the one you’re on.
Horizon 8 ESB Versions and Updates
Below is an overview of ESB versions and their scheduled updates:
| Horizon 8 Release | 1st Update | 2nd Update | 3rd Update |
|---|---|---|---|
| 2111 / 8.4 ESB (Base) | 2111.1 / 8.4.1 | 2111.2 / 8.4.2 | 2111.3 / 8.4.3 |
| 2212 / 8.8 ESB (Base) | 2212.1 / 8.8.1 | 2212.2 / 8.8.2 | — |
| 2312 / 8.12 ESB (Base) | 2312.1 / 8.12.1 | — | — |
Key Point: Omnissa recommends that customers deploy the latest available maintenance update for a given ESB version to stay current on security and bug fixes.
App Volumes 4 and DEM (Dynamic Environment Manager) ESBs
App Volumes 4 ESB
| App Volumes 4 Release | 1st Update | 2nd Update | 3rd Update |
|---|---|---|---|
| 2111 / 4.5.0 ESB (Base) | 2111.1 / 4.5.1 | 2111.2 / 4.5.4 | — |
| 2212 / 4.9.0 ESB (Base) | 2212.2 / 4.9.2 | 2212.7 / 4.9.7 | — |
| 2312 / 4.13 ESB (Base) | 2312.2 / 4.13.2 | — | — |
Dynamic Environment Manager (DEM) ESB
| DEM Release | 1st Update | 2nd Update | 3rd Update |
|---|---|---|---|
| 2111 / 10.4.0 ESB (Base) | 2111.1 / 10.4.1 | — | — |
| 2212 / 10.8.0 ESB (Base) | — | — | — |
| 2312 / 10.12.0 ESB (Base) | — | — | — |
Interoperability:
- Horizon 8 ESB, App Volumes, and DEM are aligned for broader interoperability.
- For optimal compatibility, it’s recommended to use the latest maintenance releases of App Volumes and DEM that match your Horizon release (e.g., matching YYMM versions).
- Always check the Omnissa Interoperability Matrix for the most up-to-date information.
Frequently Asked Questions
Q1. What is an ESB and how does it differ from a CR?
An Extended Service Branch (ESB) is a parallel release track to the standard Current Release (CR). The ESB track receives periodic maintenance updates focused on security and critical fixes—with no new features—allowing mission-critical environments to remain stable over a longer period.
Q2. Who should consider an ESB?
ESBs are best suited for organizations running mission-critical workloads where maximum stability is essential. If you need the latest features and can accommodate frequent upgrades, a Current Release is a better fit.
Q3. What about licensing?
There is no separate licensing requirement for ESBs. If you have licenses for CR, you can also deploy the ESB versions.
Q4. Can I mix ESB and CR versions?
Mixing is generally possible but depends on the interoperability matrix. For instance, you might run Horizon 2111 ESB with App Volumes 2111 ESB for maximum stability, but you could also check if CR versions are compatible if you need certain features.
Q5. How do I upgrade within ESB or from ESB to CR?
- Within ESB: Move from the base ESB version to its subsequent .1, .2, .3 updates as they are released.
- ESB to CR: You can switch anytime as long as the CR release date is on or after the ESB version/patch you’re on.
Q6. Are new Windows versions supported in ESB?
Yes. Each ESB update includes support for new Windows 10 & 11 releases. However, Omnissa does not add new Horizon features within these updates—only support for current and near-future Windows releases, alongside critical patches.
Q7. What about major releases of vSphere or other Omnissa products?
- Horizon ESBs aim to maintain stability and do not typically support major new features from other products.
- ESB releases do support updated releases of vSphere or vSAN for defect fixes but not for major new capabilities.
Final Thoughts
The Extended Service Branch (ESB) model in Horizon 8 is all about predictability, stability, and minimal disruption for critical desktop and application deployments. By providing longer support windows, periodic maintenance updates, and streamlined upgrade paths, ESB empowers enterprises to maintain a robust virtual desktop infrastructure without frequently revalidating new features.
Whether you need rock-solid stability for a highly regulated environment or simply want a predictable update schedule, Horizon 8 ESB—alongside App Volumes and Dynamic Environment Manager—offers a proven path. For those aiming to leverage every new feature the moment it arrives, the Current Release track remains the best option.
As always, remember to consult the:
- Omnissa Interoperability Matrix
- Product Lifecycle Matrix
- Official Release Notes
By staying informed and applying the latest ESB updates, you’ll keep your Horizon 8 deployments secure, resilient, and ready to serve your organization’s most demanding requirements.
References & Resources:
- Omnissa KB 86477: Information on Horizon 8 Extended Service Branch (ESB)
- Omnissa Interoperability Matrix
- Omnissa Product Lifecycle Matrix
Disclaimer: The information above reflects details available as of 11/12/2024. For the latest updates, always refer to Omnissa’s official documentation and release notes.