Elastic Sky

Azure Azure Virtual Desktop Horizon Microsoft VCF VDI VMware vSphere VVF

Author: editor

  • Understanding Omnissa Horizon 8 Extended Service Branch (ESB)

    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 Release1st Update2nd Update3rd Update
    2111 / 8.4 ESB (Base)2111.1 / 8.4.12111.2 / 8.4.22111.3 / 8.4.3
    2212 / 8.8 ESB (Base)2212.1 / 8.8.12212.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 Release1st Update2nd Update3rd Update
    2111 / 4.5.0 ESB (Base)2111.1 / 4.5.12111.2 / 4.5.4—
    2212 / 4.9.0 ESB (Base)2212.2 / 4.9.22212.7 / 4.9.7—
    2312 / 4.13 ESB (Base)2312.2 / 4.13.2——

    Dynamic Environment Manager (DEM) ESB

    DEM Release1st Update2nd Update3rd 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:

    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.

  • VMware vSphere Foundation (VVF) vs. VMware Cloud Foundation (VCF): Licensing Overview

    1. Understanding the Products

    VMware vSphere Foundation (VVF)

    • What It Is
      VMware vSphere Foundation is an entry-level edition of VMware’s flagship hypervisor platform (vSphere). It provides the core functionalities needed to run virtual machines on a single cluster or a small set of hosts.
    • Primary Use Case
      Ideal for smaller environments, test labs, or organizations just starting out with virtualization.

    VMware Cloud Foundation (VCF)

    • What It Is
      VMware Cloud Foundation is an end-to-end software-defined data center (SDDC) solution. It bundles together key VMware products—vSphere for compute, vSAN for storage, NSX for network virtualization, and vRealize/Aria for operations/management—into a single, integrated platform.
    • Primary Use Case
      Ideal for large-scale or growing data centers looking to deploy private or hybrid clouds with unified lifecycle management.

    2. How Licensing Works

    vSphere Foundation (VVF)

    1. Basic vSphere Entitlement
      • CPU-Based Licensing: Like most vSphere editions, Foundation typically licenses per CPU (socket), with a specific CPU core count limit.
      • Limited Feature Set: Foundation offers the most basic virtualization features (e.g., vMotion is not included in Foundation).
    2. No Included Add-Ons
      • Tools like vCenter Server, vRealize Suite, or other VMware products are not bundled under Foundation. You can purchase them separately if you need more advanced capabilities (e.g., HA, DRS, or distributed switching—if not already included in your vSphere edition).
    3. Support
      • You can choose Basic or Production Support subscriptions for vSphere Foundation. This covers troubleshooting and maintenance for vSphere itself.

    VMware Cloud Foundation (VCF)

    1. All-in-One Licensing
      • Bundled SKU: VCF includes vSphere, vSAN, NSX, and vRealize/Aria in one license or subscription. Instead of licensing each component individually, you get them all under the Cloud Foundation umbrella.
      • Flexible Models: VMware increasingly offers VCF via term-based or subscription licensing, though perpetual options may exist in certain agreements.
    2. Lifecycle Management
      • SDDC Manager: VCF’s integrated management tool orchestrates updates and patches across all components—compute, storage, networking, and management.
      • This end-to-end lifecycle approach is a hallmark of VCF and part of what you pay for with its bundled licensing.
    3. Support & Maintenance
      • Because VCF is sold as a single product, your support contract covers the entire SDDC stack. This simplifies interactions with VMware for troubleshooting any aspect of the environment.

    3. Feature and License Comparison

    Here’s a high-level snapshot of how vSphere Foundation (VVF) and VMware Cloud Foundation (VCF) compare:

    AspectvSphere Foundation (VVF)VMware Cloud Foundation (VCF)
    ScopeBasic hypervisor and virtualization featuresFull SDDC platform (compute, storage, networking, management)
    License StructureCPU-based license for a reduced feature set within vSphereSingle SKU/Subscription including vSphere, vSAN, NSX, vRealize/Aria
    Environment SizeSmall footprints, limited advanced featuresMedium to large footprints, cloud-ready architectures
    Upfront CostLower upfront cost compared to higher vSphere editions and no bundled add-onsHigher cost, but includes multiple components in one license
    SupportTied to vSphere onlyUnified support for the entire stack
    Lifecycle ManagementManual upgrades (host by host, product by product)Automated updates via SDDC Manager across all integrated components
    Use CaseLabs, small businesses, pilot projects, or minimal virtualization needsEnterprises, hybrid cloud deployments, large-scale, multi-site environments

    4. Deciding Which One Is Right for You

    1. Smaller Environments or Proof of Concept
      • If you just need a basic hypervisor solution without advanced features, vSphere Foundation might suffice. It’s budget-friendly and straightforward for small labs or entry-level production virtualization.
    2. Comprehensive Data Center Modernization
      • If you plan a significant infrastructure overhaul, you need software-defined storage (vSAN), network virtualization (NSX), and centralized management (vRealize/Aria).
      • VMware Cloud Foundation provides a fully integrated, cloud-ready architecture, simplifying deployment and ongoing upgrades.
    3. Cost vs. Value
      • vSphere Foundation has a lower licensing entry point. However, it provides fewer enterprise-grade features.
      • VCF commands a higher price but delivers an advanced and cohesive platform that handles compute, storage, network, and cloud management.
    4. Growth and Future Plans
      • If your organization is on a growth trajectory and anticipates needing virtualization capabilities across multiple sites, advanced storage, or a move to hybrid cloud, adopting Cloud Foundation earlier might reduce complexity down the line.
      • If your environment is unlikely to expand or adopt additional VMware services, vSphere Foundation may be all you need.

    5. Final Thoughts

    VMware vSphere Foundation (VVF) is a streamlined edition focused on core virtualization. It works well for basic deployments that don’t require advanced features or comprehensive cloud management. In contrast, VMware Cloud Foundation (VCF) offers a complete SDDC solution—ideal for large or fast-growing organizations that want an integrated infrastructure with simplified lifecycle management.

    Key Takeaway:

    • Use vSphere Foundation if your main focus is on cost savings and minimal virtualization needs.
    • Use VMware Cloud Foundation if you need a robust, all-encompassing platform that unifies compute, storage, networking, and management under a single license and support structure.

  • Sizing Azure Virtual Desktop: Key Considerations and Best Practices

    sky at daytime

    Introduction
    Azure Virtual Desktop (AVD) is Microsoft’s Desktop as a Service (DaaS) solution that enables organizations to provide secure, remote access to Windows desktops and applications. Whether you’re migrating from an on-premises Remote Desktop environment or building a fresh virtual desktop infrastructure in the cloud, proper sizing is crucial. An under-provisioned environment leads to poor user experience, while over-provisioning increases costs unnecessarily. In this blog post, we will explore best practices for sizing Azure Virtual Desktop to ensure you strike the right balance between performance, cost, and scalability.

    1. Understand Your User Profiles

    User profiles are a foundational concept when sizing any VDI or DaaS environment. Each user’s workload requirements—memory usage, CPU consumption, graphics intensity, and disk I/O—vary widely. Typically, organizations classify users into categories such as:

    1. Task Workers – Minimal productivity applications (e.g., Microsoft Word, Excel, web browsers).
    2. Knowledge Workers – Heavier applications (e.g., Microsoft Teams, collaboration tools, multi-browser tabs).
    3. Power Users/Developers – Resource-intensive applications (e.g., Visual Studio, large datasets, analytics).
    4. Graphics-Intensive Users – Specialized workloads requiring GPUs (e.g., AutoCAD, 3D modeling, video editing).

    The better you understand each user profile, the more precise you can be when selecting the right Azure VM size and resource requirements.

    2. Estimate Concurrency and Peak Load

    Not all users are active all the time. Understanding the maximum number of concurrent sessions is essential for cost-efficient sizing. When planning concurrency:

    • Assess user work schedules: If your organization operates in multiple time zones or has shift-based usage, concurrency may be lower at certain times.
    • Evaluate burst and peak usage: Some applications or times of day (e.g., Monday mornings) may have heavier usage than others.
    • Leverage data from existing environments: If you have historical performance metrics or usage stats, use those to forecast concurrent sessions in AVD.

    A recommended approach is to combine concurrency data with your user profiles to get an accurate sizing baseline. For instance, 300 task users might share the same sessions as 50 power users, each requiring a different portion of the total resources.

    3. Choose the Right VM Sizes

    Azure offers a variety of VM families that suit different requirements:

    1. General Purpose (e.g., D-series) – Balanced CPU and memory, ideal for knowledge workers and light productivity tasks.
    2. Memory Optimized (e.g., E-series) – Increased memory per core, suitable for larger datasets or memory-hungry applications.
    3. Compute Optimized (e.g., F-series) – Higher CPU-to-memory ratio for CPU-intensive workloads.
    4. Graphics/Visualization (e.g., NV-series) – GPU-enabled VMs for graphics-intensive workloads.

    Selecting the right VM size often involves balancing the number of CPU cores, memory, and (if required) GPU resources for your user profiles. In many cases, a proof-of-concept (PoC) or pilot environment can help you test real-world performance before wider deployment.

    4. Plan for Storage and Profile Management

    Storage is a key consideration for both performance and cost:

    • User Profiles: Store roaming profiles on Azure Files or Azure NetApp Files for quick, consistent access to user data.
    • FSLogix Profile Containers: Simplify user profile management and reduce login times by using FSLogix with AVD. This helps ensure a more consistent experience as users move between session hosts.
    • IOPS and Throughput Requirements: If your applications are I/O-intensive, using Premium SSD or Azure NetApp Files may be necessary to meet performance requirements.

    Properly sizing your storage solution ensures minimal login delays, smooth application interaction, and a better overall user experience.

    5. Leverage Autoscaling

    One of the advantages of running virtual desktops in Azure is the ability to autoscale. By configuring autoscaling policies, you can:

    1. Scale Out – Automatically add more session hosts as usage spikes.
    2. Scale In – Shut down or deallocate underutilized hosts during off-peak times to minimize cost.

    This elasticity allows you to meet peak demands without maintaining a large number of constantly running hosts. Azure Virtual Desktop integrates with Azure Monitor and Azure Automation to adjust scale rules based on CPU utilization, user load, or time-based schedules.

    6. Optimize Cost and Evaluate Licensing

    AVD licensing is included with many existing Microsoft 365 or Windows 10/11 Enterprise agreements, simplifying licensing costs. However, you still pay for the underlying Azure infrastructure—VM compute, storage, networking, and other services. Keep these tips in mind:

    • Reserved Instances: For workloads with predictable usage, reserving VM compute resources for one or three years can save significantly on Azure costs.
    • Azure Hybrid Benefit: If you’re using Windows Server session hosts (RDSH), you can leverage Azure Hybrid Benefit to reduce licensing costs if you already own Windows Server licenses with Software Assurance.
    • Scale with Demand: Use cost analysis tools to identify underused resources and keep your environment aligned with demand.

    7. Monitor and Adjust

    Sizing an AVD environment is not a one-time activity. Performance and usage patterns may change due to software updates, new applications, or user growth. Regular monitoring helps ensure your sizing remains optimal. Tools and best practices include:

    • Azure Monitor and Logs: Track metrics such as CPU, memory usage, disk I/O, and network throughput.
    • Connection Diagnostics: Use built-in AVD diagnostics to troubleshoot connection issues and user performance.
    • User Feedback: Gather feedback from pilot users and end-users to refine and validate system performance.

    Constantly reviewing metrics and feedback helps you keep costs under control while maintaining a high-quality user experience.

    Conclusion

    Properly sizing your Azure Virtual Desktop deployment is essential to ensure performance, user satisfaction, and cost-effectiveness. By analyzing user profiles, planning for concurrency, selecting the right VM series, optimizing storage, and leveraging autoscaling, you can build a robust environment that scales with your organization’s needs. Finally, don’t forget to monitor and adjust your solution over time—user behavior and application demands rarely remain static. With the right approach, you can confidently deliver a secure, efficient, and cost-effective virtual desktop experience in the Azure cloud.