What's new in Workspace ONE UEM: Safeguards, scheduling, and support for more of your fleet
- Last updated 11/19/2026
-
The fourth major release of the year, Workspace ONE UEM 2610, brings more control, support, and flexibility to managing your fleet of endpoints. Want to know what’s worth your attention first? This post covers the headline features. For the full list of updates, including additional Android, ChromeOS, Linux, and printer enhancements, see the complete release notes.
Windows: signed deployments and maintenance-window scheduling
Unsigned payloads that reach managed Windows endpoints have long been a soft spot in device management. Workspace ONE UEM 2610 closes that gap. With the new signed resource delivery enforcement model enabled at the customer organization group (OG) level, Omnissa Workspace ONE Intelligent Hub verifies a JSON Web Token (JWT) and resource hash against your own JSON Web Key Set (JWKS) before applying any Windows internal application or Administrative Template (ADMX) profile. Intelligent Hub blocks anything unassigned outright. The UEM console shows a consistent signed indicator across resource types, and a dedicated role-based access control (RBAC) permission lets you control who can configure the model. Signed resource delivery enforcement is available in Limited Availability. Contact your Omnissa account team to enable it.
UEM 2610 also extends Time Windows to all Windows resource delivery. Previously limited to Omnissa Freestyle Orchestrator workflows, the same maintenance-window scheduling now covers applications, OS updates, drivers, profiles, scripts, sensors, and baselines. Admins can choose to install immediately or within a specific Time Window, select a particular slot when multiple schedules exist, and override the window when an emergency patch can’t wait. If an endpoint is offline during its window, delivery resumes the next time the endpoint comes online within the window. You can stick to maintenance hours without managing a separate schedule for every resource type.
Apple: Extended support for iOS, macOS, tvOS, and visionOS
Support for new identity assets on iOS and macOS
iOS and macOS both gain support for three new declarative device management (DDM) credential assets: Identity, Certificate, and Simple Certificate Enrollment Protocol (SCEP). You can create, assign, and reuse each one through the standard declarative profile workflow. Upload identity assets directly or source them from an integrated certificate authority (CA), and provision SCEP-based certificates through an integrated SCEP CA. UEM now enables certificate-related DDM status item subscriptions by default, so certificate status flows through declarative reporting without any admin setup. That closes a visibility gap that used to require manual checking.
OS update management with DDM for tvOS and visionOS
DDM-based OS update management now covers tvOS and visionOS too. Available versions of these OS platforms now appear in the Apple Device Updates dashboard alongside iOS and macOS. Declarative management is no longer limited to iOS and macOS. It now works as one consistent model across the Apple platforms your organization manages.
Android: More flexibility for app deployment and device lifecycle
Several changes give Android admins more control over how apps reach devices and how devices move through their lifecycle.
Internal apps can now install directly into the Work Profile on Samsung devices without going through the Play Store. That gives you a dependable option for highly regulated environments where Play Store distribution isn't viable. A new per-app toggle lets admins select which apps install in the Work Profile, and device actions like Clear App Data are available from the Device Details Apps grid just as they are for public apps today.
Fully managed Android devices can now migrate from a single-user configuration to multi-user shared Check-in/Check-out (CICO) mode using Workspace ONE Launcher, either from the UEM console or through the REST API. UEM validates eligibility (management mode, management source, account type, and minimum Hub and Launcher versions) before proceeding. After migration, Launcher takes over with a login screen, the device maps to the staging user specified, and the device now shows the shared device configuration in Device Details so the admin can be confident in the device readiness for shift work.
Android internal apps can also now be distributed through relay servers, extending a content-distribution option previously available for Product Provisioning and Windows internal apps. A per-app toggle opts an app into Relay Server delivery. Once you enable it, UEM seeds the Android Package (APK) to every applicable Relay Server in the OG hierarchy and devices pull it locally at check-in instead of from the cloud. If seeding isn't complete when a device checks in, the device falls back to content delivery network (CDN) delivery, so installation isn’t blocked.
Printer management: Extending support to Bixolon printers
Workspace ONE UEM now supports Bixolon printers, extending printer management to a new manufacturer with full profile coverage and enrollment support. Admins can manage Bixolon printer profiles, configure connection and wireless settings, deploy firmware updates, and trigger device actions such as reboot, factory reset, and test print. UEM reports Bixolon printer identity, firmware version, network details, battery level, and fault status, so admins have the same visibility into printers that they already have into mobile and desktop devices.
A mandatory second look before bulk actions take effect
In the new Device List View, when you stage a bulk wipe, delete, enterprise wipe, change OG, send message, or manage tags action, UEM now displays a review screen before it dispatches anything. Workspace ONE UEM computes the full affected device set against live OG membership and filter criteria, shows admins that computed count next to what's visible in the UI, and flags a discrepancy warning if the two don't match. Admins can download the entire staged device list as a CSV file before committing, and the confirm button stays disabled until the admin explicitly acknowledges the scope.
It's one extra step, and it makes sure bulk operations touch only the devices you intended.
UEM 2610 pairs that review step with a new Cancel Wipe bulk action. What if a wipe command reaches more devices than intended, or shouldn't have gone out at all? Admins can now cancel staged wipe commands across multiple devices in one action instead of hunting down each device individually. UEM queues the cancellation for every eligible device with a pending Break mobile device management (MDM) command, silently skips devices that don't have one, and logs every cancellation individually for a full audit trail.
Together, these two features help prevent bulk-operation mistakes in the first place and help you recover when one slips through.
Dual admin approval: Add a second layer of control for high-impact changes
A misconfigured assignment or compromised administrator account can have a fleet-wide impact. Dual admin approval helps mitigate this risk by requiring a second admin to review and approve changes covered by an approval policy before UEM deploys them.
Admins can define approval policies by platform and resource type, and designate who can approve the changes. When a change requires approval, UEM holds it until the designated approver reviews the proposed action and the impacted devices. Approved changes move forward to deployment, while admins can revise and resubmit declined changes.
In this release, dual admin approval launches in Limited Availability with support for Windows applications and profiles. It gives IT teams greater control over changes that can affect the entire device fleet. It strengthens governance, adds an important safeguard against unintended changes, and makes sure that high-impact actions receive the right level of review before deployment.
Reusable phased deployment templates: Simplify internal app rollouts
Until now, admins who deployed a new version of an internal app in phases had to recreate the rollout configuration for every version. Reusable phased deployment templates let you define the configuration once and reuse it across deployments.
Templates capture assignment groups, phase targets, and progression criteria. When you create a phased assignment for an internal app, you can apply a template to copy the configuration, eliminating repetitive setup and enabling faster, more consistent rollouts.
See the full release notes for the complete list of updates
The newest release of Workspace ONE UEM includes a long list of additional enhancements beyond what's covered here, including further Android and ChromeOS identity and IPv6 improvements, enhancements to Linux app management, printer certificate auto-renewal and Zebra alert streaming, certificate escrow recovery through DigiCert, OAuth 2.0 for Simple Mail Transfer Protocol (SMTP), a new Cloud Connectors monitoring page, Smart Groups API partial-success handling, Freestyle service commands, phased deployment templates, on-demand sensor evaluation, and refreshes to the Enterprise App Repository and Windows Baselines wizards.
For the complete list and full configuration details, see the release notes, or visit the links below.
Visit Omnissa Docs, TechZone, and the Omnissa Community for deeper guidance and peer discussion. Because several features are in Limited Availability, talk to your Omnissa account team about enabling them for your environment.