IGEL OS 11 is Going End of Life — Here's What You Need to Do

The clock is ticking for organizations running IGEL OS 11. With End of Maintenance confirmed for 30 June 2026, the window to plan and execute a migration to OS 12 is narrowing fast.

By Brian Riegels-Morgan

December 2025

OS 11 perpetual licence renewals end. Subscription migration pricing available.

October 2025 (past)

Microsoft Secure Boot revocation list update — older OS versions blocked from booting after BIOS update.

30 June 2026 — EOM

BIOS updates applied before OS migration can render devices unbootable — an outage risk if not managed carefully.

The End of an Era for IGEL OS 11

For many organizations running virtual desktop infrastructure (VDI) or cloud-delivered workspaces, IGEL OS 11 has been a trusted workhorse for years. Its lightweight Linux footprint, centralized management via the Universal Management Suite (UMS), and broad hardware compatibility made it the go-to choice for thin client and repurposed PC deployments around the world.

But that chapter is now firmly closing. IGEL has confirmed that OS 11 reaches End of Maintenance (EOM) on 30 June 2026, after which no further updates, security patches, or Secure Boot certificates will be issued. For IT teams that haven’t yet started their migration planning, now is the time to act.

Critical Date

IGEL OS 11 will no longer receive any updates — including Secure Boot certificates — after 30 June 2026. Devices left on OS 11 post this date will be unsupported and increasingly vulnerable.

Why this Matters: the Security Stakes are High

End of Maintenance isn’t just an administrative milestone. Once an OS stops receiving security updates, the risk profile of every device running it climbs steadily. In a world where thin clients and endpoint devices sit at the front door of your cloud or virtual desktop environment, leaving them unpatched is an invitation for trouble.

There’s also a very concrete Secure Boot complication to contend with. In October 2025, Microsoft delivered an updated Secure Boot revocation list that prevents older IGEL OS versions from booting once a BIOS/UEFI firmware update is applied. Organizations that update their endpoint firmware without first updating IGEL OS to a compatible version may find devices that simply won’t start.

Secure Boot Warning

Do not apply BIOS/UEFI firmware updates to IGEL OS endpoints before ensuring they are running OS 11 version 11.10.410 or later, or have been migrated to OS 12 version 12.7.0 or later. Failure to do so may result in devices being unable to boot.

What is IGEL OS 12 — and why it's a genuine step forward

IGEL OS 12 isn’t simply OS 11 with a version bump. It represents a fundamental architectural rethink, introduced as part of the broader IGEL COSMOS platform launched in April 2023. Since then, IGEL has continued to build on that foundation, most notably with the IGEL Adaptive Secure Desktop™ — a capability that delivers role-based, persona-driven workspaces, dynamically tailoring applications and data access to each user while enforcing Zero Trust security principles at every login and logout. This evolution makes the case for migrating to OS 12 even stronger: organizations that move now will be positioned to take full advantage of these advances, not just maintain the status quo. Understanding what’s changed in the platform will help IT leaders make the case for migration investment internally.

Modular Architecture

The OS base is completely separated from its applications, enabling independent updates without a full OS upgrade.

IGEL App Portal

Apps like Citrix Workspace, Zoom, and VMware Horizon can be delivered and updated via the IGEL App Portal independently of the OS.

UMS 12 Management

A rebuilt, web-based management console that supports both OS 11 and OS 12 simultaneously, easing phased migration.

Deep Endpoint Insights

New telemetry and compliance dashboards give IT teams visibility into endpoint health, security posture, and usage.

Critically, UMS 12 can manage a mixed estate of OS 11 and OS 12 devices simultaneously. This means organizations don’t need to execute a disruptive “big bang” migration — they can move device groups across at their own pace while managing everything from a single console.

Key Advantage

With UMS 12, you can run OS 11 and OS 12 devices side by side. There’s no need to migrate your entire fleet at once. Plan a phased rollout that fits your operational rhythm.

OS 11 vs OS 12: Key Differences at a Glance

Area	IGEL OS 11	IGEL OS 12
Architecture	Monolithic OS — full updates required for any change	Modular: base OS separated from apps
App updates	Bundled with OS firmware	Independent via IGEL App Portal
Management UI	UMS 6 (legacy desktop client)	UMS 12 (modern web-based console)
Licensing model	Perpetual (now retired) or subscription	Subscription (Platform Access Subscription)
Onboarding	Manual or USB provisioning	Self-enrolment via IGEL Onboarding Service (under 5 min)
Security updates post Jun 2026	None	Ongoing
Secure Boot support	Requires v11.10.410+ to boot after BIOS updates	Fully supported from v12.7.0+

What your organization needs to action now

Whether your fleet is 50 devices or 50,000, the migration from OS 11 to OS 12 requires planning. Here’s a practical framework for getting started.

Audit Your Current Estate

Identify every device running IGEL OS 11, the versions in use, and whether any are already on a version below 11.10.410 — those are at immediate Secure Boot risk if firmware updates are applied. Use UMS 12 (which is backwards compatible) to gain visibility if you haven’t already upgraded your management layer.

Upgrade to UMS 12 first

Before migrating any endpoints, upgrade your Universal Management Suite to version 12. This is the foundation for everything else — it manages both OS 11 and OS 12 devices, gives you access to the IGEL App Portal, and opens up the full IGEL COSMOS cloud services. You can do this without touching a single endpoint.

Review and Migrate your Licensing

IGEL OS 11 perpetual licences reached end of renewal in December 2025. You’ll need to transition to IGEL’s subscription model (Platform Access Subscription) to continue receiving updates and to access OS 12. IGEL offered advantageous migration pricing for customers who moved early — engage your IGEL partner or account team immediately to understand your options and co-term your licences.

Run a Pilot Migration — and Rebuild your Profiles

Select a representative group of devices — ideally across different hardware models and use cases — and migrate them to OS 12. Test your most critical applications (Citrix, AVD, VMware Horizon, Zoom, Teams) through the IGEL App Portal. One of the most important things to understand before you begin: OS 11 profiles are not directly transferable to OS 12. The configuration model has changed significantly, and there is no automated migration path for existing UMS profiles and policies. IT teams will need to audit their current OS 11 profiles, understand what each setting achieves, and then rebuild equivalent profiles natively in UMS 12 for OS 12 devices. This is not a minor task for environments with complex or numerous profiles, so budget time for it accordingly. Use your pilot to identify the most critical profiles first, validate them thoroughly, and establish a templating approach before scaling the rollout.

Plan and Execute Phased Rollout

With UMS 12 managing both OS versions simultaneously, you can migrate device groups progressively. Prioritise devices that are most exposed (older OS versions, high-security environments, or those most likely to receive BIOS updates) and work through the fleet in waves. Document your rollback procedures before you begin.

Freeze BIOS Updates Until Migration is Complete

Instruct your infrastructure and device management teams not to apply BIOS or UEFI firmware updates to any IGEL endpoint until that device has been confirmed on OS 11 v11.10.410+ or OS 12 v12.7.0+. Communicate this clearly across teams — an automated patch management tool applying a BIOS update could leave devices unbootable.

Do not wait for the Deadline

End-of-life migrations have a habit of compressing at the worst possible time. What looks like months of runway today becomes weeks when procurement cycles, change management approvals, and phased rollouts are factored in. The organizations that will feel the least pain are those that start assessing, planning, and piloting now — not in Q1 2026.

The good news is that IGEL has been thoughtful in its migration approach. UMS 12’s backwards compatibility, the availability of IGEL’s migration tooling and documentation, and the phased licensing options all make this a manageable project for most organizations. However none of that helps if planning is deferred too long.

If you’re a Citrix, AVD, or VMware Horizon shop with IGEL OS 11 in your environment, the question isn’t whether to migrate — it’s whether you have a plan to do so before 30 June 2026.

Key Takeaways

IGEL OS 11 reaches End of Maintenance on 30 June 2026 — no further security updates, patches, or Secure Boot certificates after this date. Upgrade UMS to version 12 immediately. Migrate OS 11 perpetual licences to subscription. Freeze BIOS updates until endpoints are on compatible OS versions. Plan time to rebuild OS 12 profiles from scratch — OS 11 profiles do not migrate directly. Run a pilot, then execute a phased rollout well before the deadline. And look ahead: OS 12 is the foundation for the IGEL Adaptive Secure Desktop and the broader IGEL platform roadmap. Engage your IGEL partner or account team now to understand your specific licensing and migration path.

Need help planning your IGEL OS 12 migration? Contact us to assess your environment, minimise risk, and build a phased migration strategy tailored to your organisation.