Omnissa used its ONE 2025 conference this week to unveil a sweeping set of updates that extend its Workspace ONE platform to manage Windows Server, introduce a rearchitected Windows agent for PCs, and make application layering generally available on physical Windows desktops. The moves mark a decisive push to bring servers, virtual desktops, physical PCs, and even frontline peripherals under a single management roof—a consolidation that promises to reduce tool sprawl but brings its own set of co-management and licensing headaches.

For Windows-focused IT teams, the announcements are a mix of immediate capability and longer-term roadmap items. Workspace ONE Server Essentials (limited availability) adds cloud-native lifecycle management for Windows Server OS. A next-generation agent-based Windows management architecture—leveraging the Intelligent Hub agent—will replace legacy OMA-DM behaviors, with general availability planned later this year. And App Volumes Manager now supports physical Windows endpoints in general availability, offering application layering outside of VDI for the first time.

What Omnissa Changed for Windows IT

Windows Server management arrives in Workspace ONE
Server Essentials is a new module that allows administrators to onboard, configure, and manage Windows Server instances using the same Workspace ONE console they already use for desktops and mobile devices. The feature set covers server app delivery, update management, inventory, and remote support—all cloud-native. Omnissa states the goal is to eliminate the need for separate server management tools and cut operating costs. But it’s rolling out in limited availability, so customers must validate which Windows Server versions are supported, how clustering and Active Directory roles are handled, and whether the same Intelligent Hub agent or a dedicated server agent is used. Early adopters should also confirm WSUS integration for patching pipelines.

A new Windows management agent—no more OMA-DM
Perhaps the most significant change for Windows PC management is the rearchitecture away from OMA-DM. Omnissa is shifting to an agent-based model using the Intelligent Hub agent, which already handles device enrollment and compliance. This promises richer telemetry, better multi-user session support at logon, and near-real-time policy enforcement—all pain points of the current OMA-DM approach. The agent is designed to coexist with existing PC lifecycle tools like Microsoft Configuration Manager (SCCM) or Intune, allowing phased migration rather than a rip-and-replace. General availability is expected later this year, but IT teams will need to carefully test co-management scenarios: policy precedence conflicts with GPOs, SCCM, and Intune are a real risk.

App layering escapes the data center
App Volumes Manager for physical Windows endpoints is now generally available. With it, Omnissa extends application layering and Apps-on-Demand to physical desktops, letting IT deliver and update applications across the entire Windows estate—virtual and physical—using the same workflows. This can dramatically reduce image sprawl and the need to rebuild golden images when an app version changes. But compatibility with line-of-business installers, licensing enforcement within layers, and interactions with legacy packaging tools need local validation.

Other announcements that touch the Windows estate
For VDI shops running Horizon, Omnissa announced general availability of Experience Management for Horizon, bringing logon-time telemetry, AI-guided root cause analysis, and software metering to virtual desktop environments. For on-premises deployments, Omnissa Monitor (limited availability) offers similar insights without sending telemetry to the cloud. On the hardware front, Horizon will support NVIDIA RTX PRO 6000 Blackwell Server Edition GPUs and NVIDIA vGPU software later this year, promising higher VM density and improved Blast encoding. And in a move that broadens hypervisor choice, Horizon on Nutanix AHV enables VDI deployments on Nutanix Cloud Infrastructure, with integration into Prism management and Redirect-on-Write cloning. Also previewed: Horizon Cloud on Platform9’s Private Cloud Director, using an OpenStack provisioning engine for private-cloud DaaS. For mixed environments, Omnissa’s integration with Apple’s GitHub repository of DDM payloads promises same-day support for new Apple OS releases, which matters in Windows shops with a growing Mac footprint.

What the Updates Mean for You

For Windows desktop admins
If you manage Windows PCs through Workspace ONE, the new agent will eventually give you faster policy enforcement and richer telemetry than you get with OMA-DM. But until it reaches GA and you can prove co-management stability, your current workflows stay put. The co-existence promise with SCCM or Intune is appealing—many organizations run a mix of tools—but policy mapping will be essential to avoid unexpected compliance gaps. App Volumes on physical endpoints is a more immediate win: if you’ve been using it in VDI, you can now extend the same app layering to your physical estate, simplifying image management. Plan to test with your most complex LOB apps first.

For server administrators
Server Essentials could let you fold Windows Server lifecycle management into a single console that also handles endpoints. That is a major operational simplification if you currently juggle multiple tools. But the limited availability means feature depth is still unclear; validate support for your server fleet’s operating system versions, cluster awareness, and update mechanisms before committing production workloads. Co-management with existing tooling—like WSUS or SCCM for servers—must also be tested.

For VDI architects and Horizon admins
The NVIDIA Blackwell support and Nutanix AHV integration open new deployment architectures, but they also change your TCO model. vGPU licensing costs, GPU density, and power/thermal implications will vary with workload. Run real-world POCs using your actual user profiles before settling on a hardware configuration. The DEX capabilities in Horizon are now GA and can immediately help you reduce logon times and identify performance bottlenecks if your environment is cloud-connected; if not, Omnissa Monitor provides an on-prem alternative, though it’s still in limited availability.

For security and compliance teams
Centralizing telemetry into Workspace ONE Intelligence for servers, endpoints, and peripherals raises data residency and privacy questions, especially in regulated industries. Confirm telemetry routing, retention policies, and whether on-prem options (like Omnissa Monitor for Horizon) meet your compliance needs. The AI-driven remediation in Playbooks and QuickFlows is powerful, but you’ll want approval gates and rollback capabilities to prevent automated fixes from causing wider service disruptions.

The Long Road to Unified Windows Management

Omnissa’s pivot toward a single platform for all Windows endpoints and servers didn’t happen overnight. The company, once VMware’s end-user computing division, became independent after Broadcom’s acquisition of VMware and now boasts 26,000 customers and $1.5 billion in annual recurring revenue. Its Workspace ONE product has long been a strong UEM contender, but the architecture leaned heavily on OMA-DM for Windows—a protocol with known limitations in telemetry richness, policy enforcement speed, and multi-user session handling.

Meanwhile, enterprise Windows management has become increasingly fragmented. Physical PCs are often a mix of domain-joined machines managed by Group Policy and SCCM, and cloud-native ones co-managed by Intune. Servers usually sit in their own silo with different tools. VDI adds another layer. Omnissa’s bet is that by offering a single agent (the Intelligent Hub) that can run alongside existing tooling, and by extending that management plane to servers and peripherals via the MQTT protocol, it can simplify this chaos. The same strategy applies to application delivery: App Volumes was born in VDI, but extending it to physical Windows endpoints erases an artificial boundary.

The moves also mirror broader market trends. Competitors like Microsoft Intune are gradually absorbing more endpoints (including servers, albeit lightly), and other UEM vendors are adding device health analytics and automation. Omnissa’s open-ecosystem partnerships with Nutanix, NVIDIA, and Platform9 differentiate it from lock-in narratives, but the real test will be execution—particularly around co-management friction and the timeliness of GA milestones.

Your Pilot Checklist: Getting Started Without Getting Burned

Omnissa’s announcements are a platform evolution, not a turnkey upgrade. These steps can help you evaluate the new capabilities without disrupting existing operations:

  1. Define measurable success criteria before you start: aim for specific improvements in logon time, MTTR, server patch compliance, or license reclamation.
  2. Pilot Server Essentials on non-critical servers first. Test onboarding, update deployment, and inventory reporting against your existing processes. Verify supported Windows Server versions and any impact on Active Directory roles or clusters.
  3. Map existing policy precedence for Windows PCs before introducing the new agent. Run the Intelligent Hub agent on a test group alongside SCCM, Intune, and GPOs to detect conflicts and understand which policy wins.
  4. Validate App Volumes with representative physical endpoints. Test with your most complex line-of-business installers, check licensing enforcement within layered apps, and ensure the apps behave as expected offline and online.
  5. Run a VDI POC that reflects your real workload mix. If eyeing NVIDIA Blackwell, measure GPU density, Blast encoding improvements, and total per-desktop cost including vGPU licenses and power. For Nutanix AHV, confirm support for features like vGPU, live migration, and Cloud Pod Architecture.
  6. Exercise Playbooks in read-only mode before enabling automated QuickFlows. Establish approval gates and rollback procedures so AI-recommended remediation doesn’t cascade into an incident.
  7. Secure written support scopes and escalation matrices for each partner integration (Omnissa + Nutanix, + NVIDIA, + Platform9) to prevent finger-pointing during outages.
  8. Address data residency early. If you’re in a regulated industry, decide whether cloud-connected telemetry is acceptable or whether you’ll rely on on-prem alternatives like Omnissa Monitor.

What to Watch Next

Omnissa has drawn a clear blueprint, but the timeline for general availability of its next-gen Windows agent and the full scope of Server Essentials will shape IT teams’ planning cycles for the next 12 months. Competition from Microsoft Intune—which is also deepening server and multicloud management—will likely heat up. NVIDIA Blackwell’s pricing and real-world VDI density numbers will become clearer as the hardware reaches general availability. For now, the smart play is to treat Omnissa’s platform updates as a phased evolution: pilot deliberately, validate claims against your environment, and resist the temptation to consolidate everything overnight. If Omnissa delivers on its roadmap, Windows IT teams could find themselves managing fewer consoles and delivering a more consistent employee experience—just not without a few co-management headaches along the way.