Omnissa has released Windows Server management for Workspace ONE UEM, hitting general availability on May 6, 2026. The addition closes a long-standing gap in cloud-based endpoint management, allowing IT teams to manage Windows Server systems from the same console they already use for desktops, laptops, and mobile devices. No more separate tools, no more hybrid compromises.

Workspace ONE UEM already handles Windows 10 and Windows 11 endpoints, but servers were left to legacy on-premises solutions like SCCM or manual patch cycles. With this release, organizations can bring Windows Server 2022, Windows Server 2025, and even some older builds under a modern, unified policy engine. This marks a significant step in Omnissa’s strategy to become the single pane of glass for all enterprise endpoints.

The Long Road to Server Support in UEM

Unified endpoint management has traditionally been a desktop and mobile story. Servers sat in a separate bucket, managed by data center tools that didn’t speak the same language. Omnissa (formerly VMware’s End-User Computing division, now an independent company since Broadcom’s 2024 divestiture) has been steadily broadening Workspace ONE’s scope.

Windows 10 support arrived years ago, and Windows 11 followed quickly. Macs, iOS, Android, and even ruggedized devices joined the fold. But Windows Server remained the elephant in the room—present in every data center, yet invisible to the UEM console. Omnissa’s own forums lit up with requests over the years, with admins asking why they couldn’t apply the same compliance policies or patch schedules to a Windows Server VM as they did to a Windows 11 laptop. The answer was always “coming soon”. Now it’s here.

What’s Included in the May 6 GA Release

On May 6, 2026, Omnissa flipped the switch, making Windows Server management generally available to all Workspace ONE UEM customers with an active license. The feature set covers the essentials, with more planned through future updates.

Core capabilities

  • Enrollment and discovery: Servers can be enrolled via standard Windows MDM enrollment methods, including bulk provisioning through Azure AD join, domain join with automatic discovery, or manual enrollment using a dedicated server enrollment link. Existing servers already on the network can be discovered and imported.
  • Patch management: IT can approve, schedule, and report on Windows Server updates directly from the Workspace ONE console. This includes quality updates, feature updates, and out-of-band patches. Administrators can set maintenance windows and automatic reboots.
  • Configuration policies: Push configuration profiles to enforce settings such as firewall rules, RDP access, local user rights, and disk quotas. The policy engine supports inheritance and exceptions, just like desktop profiles.
  • Compliance and remediation: Define compliance rules tailored to servers—for example, ensuring specific services are running, certain ports are closed, or that the server has joined a domain. Non-compliant servers can trigger automated remediation scripts or alerts.
  • Scripting and automation: Run PowerShell scripts on servers remotely, either on-demand or on a schedule. Omnissa provides a library of pre-built scripts for common tasks like resetting the Windows Update components, cleaning disk space, or restarting services.
  • Inventory and reporting: The console shows detailed hardware and software inventory for every managed server. Dashboards surface server-specific views to track patch compliance, uptime, and configuration drift.

Licensing model

Omnissa confirmed that Windows Server management is included in the existing Workspace ONE Advanced and Enterprise editions. There is no per-server surcharge, though customers must have sufficient device licenses to cover each server. This pricing simplicity was highlighted during the announcement as a differentiator against competitors that charge per workload or require separate server management add-ons.

Why It Matters: IT Operations Unified

For most organizations, servers aren’t just a handful of VMs. Even mid-sized companies run dozens of Windows Servers hosting domain controllers, file shares, print services, and line-of-business applications. Managing these with SCCM or other legacy tools requires dedicated infrastructure, specialized skills, and time-consuming manual processes. Meanwhile, the same organization already uses Workspace ONE for its desktop fleet.

Bringing servers into the same platform brings immediate operational gains:

  • Single console: Security teams can see compliance status for both servers and workstations in one place. During a zero-day event, they can audit patch coverage across the entire Windows estate instantly.
  • Consistent policies: Policies written for Windows 11 can often be reused or extended to Windows Server, reducing the policy sprawl that comes from maintaining separate management tools.
  • Reduced shadow IT: When servers are invisible to the main endpoint console, admins sometimes bypass formal processes. With official support, everything stays recorded and auditable.
  • Automation at scale: Scripts that touch desktops can now touch servers too, without switching tools. A compliance script that checks for a specific registry key can run across all Windows devices—physical, virtual, on-premises, or in the cloud.

One early beta tester, a systems administrator for a financial services firm, posted in the Omnissa community: “We finally retired our WSUS server last week. All updates, including server updates, now come through Workspace ONE. It saved us a whole maintenance window per month.” Such anecdotes are likely to proliferate as the feature matures.

How It Works Under the Hood

Windows Server management in Workspace ONE UEM uses the same MDM protocol (MS-MDM) that Windows 10 and 11 use. Microsoft has steadily improved the MDM stack in Windows Server, making it possible for third-party UEM solutions to manage servers without agents. Omnissa’s engineering team worked closely with Microsoft to validate scenarios and ensure compatibility.

When a server enrolls, it receives a set of policies: enrollment restrictions, compliance rules, update rings, and configuration profiles. The Windows Server MDM client processes these policies just as a Windows 11 machine would. Omnissa’s cloud infrastructure (which runs on AWS, with regions globally) handles the communication, policy distribution, and reporting.

For servers that cannot connect directly to the internet, Omnissa offers an on-premises connector component called AirWatch Cloud Connector (ACC). ACC proxies the traffic, so no inbound firewall holes are required. This is crucial for servers in isolated networks or DMZs that still need managing.

Competitive Landscape and Market Impact

Omnissa’s move puts pressure on several fronts. Microsoft’s own Intune has supported Windows Server management for some time, but many organizations find Intune’s server features lacking compared to its desktop capabilities. Omnissa now offers a credible alternative, especially for shops already invested in the Workspace ONE ecosystem.

Other UEM players like Ivanti and ManageEngine also have server management modules, but they often require additional licensing or separate consoles. Omnissa’s all-in-one licensing and seamless integration may sway them. In the SMB space, where Workspace ONE is less common, the impact will be muted—those customers tend to use Windows Admin Center or third-party remote monitoring and management (RMM) tools.

For cloud-forward enterprises moving toward Windows Server on Azure, this release pairs well with Azure Arc. Omnissa can manage the server’s OS policies while Azure Arc handles cloud-adjacent tasks like inventory and policy compliance at the Azure level. The combination covers more ground than either alone.

Real-World Adoption and Early Feedback

Although the feature just reached general availability, Omnissa ran an extensive beta program throughout late 2025 and early 2026. More than 200 organizations participated, ranging from universities to large retailers. Feedback posted on the Omnissa community forum has been mostly positive, with a few common threads:

  • Enrollment pain points: Some admins struggled with enrolling servers in locked-down environments where PowerShell execution policies or network restrictions prevented the out-of-the-box enrollment. Omnissa addressed these by providing a full set of manual enrollment options and thorough documentation.
  • Depth of server-specific policies: Early betas lacked some advanced server settings, such as detailed Hyper-V host configuration or Windows Server failover cluster rules. According to the May 6 blog post, these are on the roadmap, but not yet delivered. Omnissa product managers have committed to quarterly updates focusing on server-specific enhancements.
  • Performance: Managing thousands of servers did not introduce noticeable latency, thanks to the scalable cloud backend. However, the console’s server inventory page could benefit from additional filtering and bulk-action capabilities, which are slated for a mid-summer update.
  • Third-party patch support: Unlike desktop management where Omnissa partners with software vendors like Adobe and Zoom for third-party application updates, server-specific third-party patches (e.g., SQL Server, Exchange) are not currently supported through the integrated patch module. Admins can still deploy these as custom scripts, but the community hopes for deeper integration soon.

One university IT director commented: “We manage over 600 servers across campus. Getting them all into one console with our 12,000 endpoints is a game-changer for our vulnerability management program. The script automation alone is worth the price.”

What’s Next for Omnissa and Windows Server

Omnissa executives hinted at several server-focused initiatives in the coming quarters:
- Automated server lifecycle management: From provisioning to decommissioning, integrate with vSphere and Azure to manage the full server lifecycle.
- Intelligent Insights: Use machine learning to predict server failures or capacity issues based on Workspace ONE’s telemetry.
- Expanded third-party patching: Direct integration with the major server application vendors.
- Better integration with cloud providers: Tighten the thread with AWS and Azure to manage Windows Server IaaS instances natively.

All this points to Omnissa treating servers not as an afterthought but as a first-class citizen in the endpoint ecosystem. For a company that built its name on mobile device management over a decade ago, it’s a notable evolution.

Getting Started

Existing Workspace ONE UEM customers can enable Windows Server management immediately in the console settings. No additional server software is required. The Omnissa team has published a setup guide, a video walkthrough, and a migration guide for organizations moving away from WSUS or SCCM. They also announced a series of live webinars throughout May to assist with onboarding.

For new customers, a 30-day free trial of Workspace ONE UEM is available, which now includes server management. Omnissa’s partner network has been trained and is ready to assist with deployments.

Conclusion

The GA release of Windows Server management in Workspace ONE UEM on May 6, 2026, marks the end of an era of fragmented endpoint management. Organizations that already trust Omnissa for their desktop and mobile endpoints can now bring servers into the fold without juggling extra tools or costs. While some advanced capabilities remain on the roadmap, the current feature set—patch management, configuration, compliance, and scripting—covers the needs of most Windows Server environments. IT teams should evaluate how this unification can reduce operational overhead, improve security posture, and simplify compliance reporting. As always, testing in a non-production environment is recommended before rolling out production servers.

For ongoing updates, follow Omnissa’s official blog and the Workspace ONE community forums.