IGEL, You Have My Attention

IGEL Dual Boot and Omnissa together change the ransomware recovery playbook

All right, I have a hot one here. If you care about EUC, business continuity, or endpoint security in general, this is worth your attention.

IGEL recently announced a Dual Boot solution that pairs with Windows, and the core idea is simple but powerful: install IGEL OS alongside Windows so that if a compromised endpoint is hit by ransomware or another serious security event, the user can reboot into a clean, managed operating system and reconnect to critical apps in minutes.

For me, that is where this is really interesting.

We spend a lot of time talking about prevention, detection, and containment. And to be clear, all of that matters. But when a ransomware attack gets through, and from what I have seen no amount of lockdowns and security tools can stop everything, the question changes fast. It stops being "How do we prevent this?" and becomes "What the heck do we do now, and how do we get people working again quickly?"

Most companies do not have days to wait while machines are reimaged, replaced, and shipped out. Time is money.

That is exactly why IGEL Dual Boot stands out to me.

Instead of treating the endpoint as dead weight until IT can rebuild Windows, the device becomes part of the recovery plan. If a machine is suspected to be compromised, the user reboots, selects IGEL OS instead of Windows, and then returns to a clean environment. With access to the right SaaS apps, VDI, DaaS, collaboration tools, and secure browser-based workflows, the user can be productive again in minutes instead of sitting idle for hours or days.

That matters because ransomware response is not only about security. It is about operational continuity.

Many recovery plans still assume the endpoint must be rebuilt before work can resume. That creates a painful chain of dependency: isolate the device, investigate the damage, reimage Windows, restore apps, restore trust, and only then hand the machine back to the user. Even if the backend infrastructure is still healthy, the endpoint becomes the bottleneck.

Dual Boot flips that model. The endpoint does not have to be fully repaired before the employee can be effective again. It just has to boot into a trusted operating environment that gives the user access to what they need most.

That is the breakthrough.

And in practice, this is where the value becomes very real. If your critical workflows are already accessible through technologies like Omnissa Horizon, Microsoft 365, Teams, Zoom, perhaps a secure enterprise browser like Island, or other supported apps, the endpoint recovery experience can be dramatically simplified. The user restarts the PC, chooses IGEL OS from the boot menu, authenticates, launches the required tools, and gets back to work. 

This is a much stronger story than telling the business to wait while IT rebuilds one device at a time.

Why this matters

We have already seen plenty of examples of why this matters.

The MGM Resorts incident is a good reminder that an attack does not have to involve a zero-day exploit to bring operations to a halt. Public reporting tied that incident to social engineering and massive operational disruption across MGM systems. That is the important lesson: you do not need a zero-day for the impact to be severe. A disruptive cyberattack is still a disruptive cyberattack, and when endpoints and access paths are affected, the business feels it immediately.

There are other infamous ransomware cases that make the same point.

Colonial Pipeline paid millions after ransomware disrupted operations. JBS also paid after ransomware affected major parts of its business. CWT reportedly had 30,000 computers knocked offline and paid millions as well. The details vary from case to case, but the pattern is familiar: systems become unavailable, endpoints become unusable or untrusted, operations slow down or stop, and the organization is forced into recovery mode under pressure.

That is why I see IGEL Dual Boot as more than just an interesting feature. I see it as a practical recovery option.

IGEL & Omnissa

After seeing and working with this, the one thing that occurred to me that was missing, though, was a strong delivery mechanism for the dual boot environment. It is one thing to have this technology. It is another thing entirely to deploy it at scale across an entire fleet of PCs. A recovery platform is only useful if you can actually get it onto devices before an emergency happens.

So I tested that part myself.

I uploaded the IGEL Dual Boot installer .exe into Omnissa Workspace ONE UEM and configured it as a native app deliverable to enrolled managed Windows devices. The tricky part was determining where to store the OS image so the installer could deploy it, along with figuring out the right sequence of command-line switches and install parameters. But once I had that in place, it worked great.

The app deployed successfully, the dual boot experience was there, and in testing it performed exactly as I hoped.

That matters because it turns this from a compelling conference announcement into something operationally real.

Bringing it home

IGEL Dual Boot is not just about booting into another operating system. It is about changing the endpoint from a recovery problem into a recovery path. In a ransomware event, or even in a broader attack that leaves Windows unavailable or untrusted, the ability to reboot into IGEL OS and reconnect users to the tools they need could dramatically reduce downtime.

And when paired with a delivery method like Omnissa Workspace ONE UEM, it becomes something IT teams can realistically deploy, test, and build into a resilience strategy.

You do not need a zero-day for business disruption to become severe. MGM showed that. Colonial Pipeline showed that. JBS showed that. CWT showed that.

What organizations need is a way to quickly restore user productivity.

That is why IGEL Dual Boot got my attention.