At the Omnissa ONE 2025 conference, the freshly independent company dropped a series of announcements that reshape how IT teams can manage Windows devices, servers, and applications—without ripping out their existing Microsoft tooling. The headline: Workspace ONE now uses an agent-based architecture that coexists peacefully with Intune and ConfigMgr, while new capabilities extend unified endpoint management to Windows Server and automate vulnerability remediation using CrowdStrike data.

Workspace ONE sheds MDM constraints

Omnissa rearchitected Windows management for Workspace ONE, moving away from the OMA-DM APIs that have historically caused conflicts when other management tools are present. Instead, an Intelligent Hub agent now enforces policies and collects telemetry, allowing Workspace ONE to run alongside Microsoft Intune, Configuration Manager, or Group Policy without the API collisions that plagued previous versions.

This agent-based model means IT teams can adopt Workspace ONE incrementally for specific capabilities—say, virtual desktop integration or app management—while keeping their existing PC lifecycle tools in place. TechTarget analyst Garth Landers called the shift “an end-around” that frees Omnissa to innovate without being limited by Windows’ MDM framework.

Workspace ONE Server Essentials brings UEM to the data center

In a limited-availability launch, Omnissa extended Workspace ONE to manage Windows Server workloads. Server Essentials allows onboarding, inventory, patching, app delivery, and remote support for servers from the same console used for desktops and mobile devices. For organizations running a mix of Windows Server instances, this could reduce the number of consoles admins must juggle during incident response and routine maintenance.

Autonomous Workspace: starting with vulnerability defense

Omnissa’s bolder vision is the Autonomous Workspace—an AI-assisted operational model that aims to shrink mean time to repair (MTTR). The first tangible piece is Workspace ONE Vulnerability Defense. It ingests exposure data from CrowdStrike Falcon, maps CVEs to affected endpoints, prioritizes risk, and triggers automated remediation through playbooks. Future releases promise more agentic (self-driving) workflows, but for now, human approval gates remain.

App Volumes breaks out of VDI, targets physical PCs

Long tied to Horizon virtual desktops, App Volumes is being repositioned as a cross-platform app lifecycle tool. The new Apps Essentials bundle packages App Volumes, ThinApp, and Dynamic Environment Manager for broader app delivery. Crucially, App Volumes will soon support physical Windows endpoints, delivering MSI-wrapped VHDs via an agent without requiring a full App Volumes Manager infrastructure. This allows organizations to package an app once and deploy it to physical and virtual machines alike.

More hypervisor and GPU choices

Omnissa also announced Horizon support for Nutanix AHV, a preview of Horizon Cloud on Platform9, and integration with NVIDIA RTX PRO 6000 Blackwell GPUs and vGPU software. These partnerships give IT architects alternatives to single-vendor stacks—particularly important as organizations re-evaluate licensing and costs in the wake of Broadcom’s VMware changes.

What it means for IT teams

For endpoint managers
If your organization uses Intune or ConfigMgr, you can now pilot Workspace ONE for additional features—like Freestyle automation to build Horizon VM pools—without a rip-and-replace migration. Co-management becomes a practical option, though you’ll need to test policy precedence and logon performance in shared desktop scenarios.

For server administrators
Server Essentials could simplify patch management and inventory for non-critical Windows Server roles. However, treat it as experimental: Omnissa is rolling this out slowly, and you should pilot on a small set of non-production servers first.

For VDI and desktop engineering teams
App Volumes’ expansion to physical endpoints means you can streamline app packaging and delivery across your entire fleet. If you’ve been using App Volumes in Horizon, extending it to laptops and workstations reduces image sprawl. The Nutanix and NVIDIA options offer potential cost savings or performance gains, but model your TCO carefully—Blackwell GPU and vGPU licensing can be significant.

For security and governance leads
Vulnerability Defense promises faster patch times, but automated remediation carries blast-radius risks. Start with read-only playbooks and manual approval steps; only enable autonomous execution after validating rollback procedures.

How we got here

Omnissa launched as an independent company after its carve-out from VMware and acquisition by KKR, publicly citing roughly 26,000 customers, 4,000 employees, and $1.5 billion in annual recurring revenue. The new entity needed to differentiate and address customer frustration with Broadcom’s licensing tactics. The MDM API conflicts were a longstanding pain point; by decoupling, Omnissa can compete on features rather than fighting Windows’ management stack. The industry-wide push for consolidation and “autonomous endpoint management”—with 96% of organizations expressing interest, according to research cited by TechTarget—provided a receptive market for these pragmatic, automation-led moves.

What to do now: a pilot checklist

1. Test co-management
Deploy the Workspace ONE Intelligent Hub agent on a test group of Windows devices that are also managed by Intune or ConfigMgr. Verify that policies don’t conflict and that logon times remain acceptable.

2. Evaluate Server Essentials
Choose a handful of non-critical servers (e.g., test file servers) and onboard them via Server Essentials. Compare the management experience against your existing tools.

3. Run a GPU VDI POC
If GPU-accelerated VDI is on your radar, benchmark representative workloads on NVIDIA Blackwell vGPU profiles. Measure density and user experience.

4. Try App Volumes for physical endpoints
Package a common application as an MSI-wrapped VHD and deliver it to a mix of physical and virtual desktops. Monitor app start times and I/O.

5. Start vulnerability defense in audit mode
Ingest CrowdStrike data, let Vulnerability Defense prioritize CVEs, and run suggested remediations manually before switching to automated flows.

6. Model TCO
For any new infrastructure options (Nutanix, NVIDIA, Platform9), calculate three-year costs including licensing, support, and training.

7. Establish governance
Define RBAC, approval workflows, and rollback playbooks before activating any autonomous playbooks.

8. Hold Omnissa and partners accountable
Get written SLAs and joint support runbooks from Omnissa and key partners like CrowdStrike, Nutanix, and NVIDIA for the configurations you intend to run.

Outlook

Omnissa’s roadmap includes more autonomous features and deeper platform integrations, but the company’s near-term success hinges on how well these initial capabilities perform in customer POCs. Watch for GA dates on Server Essentials and further agentic AI releases later in 2025. For now, the message is clear: consolidation and choice are no longer just conference keynote themes—they’re capabilities you can start testing today.