Mastering the Silent Step up from Windows Hub Registered to Hub Managed via API
Managing Windows devices at scale often requires a seamless transition from initial enrollment to full enterprise management—without disrupting end users. While Hub Registered Mode provides a lightweight onboarding experience, organizations often need the additional control, security, and automation that come with Hub Managed Mode.
In this article, we’ll explore how to silently upgrade Windows devices from Hub Registered Mode to Hub Managed Mode using the Omnissa Workspace ONE UEM API. By leveraging API-driven automation, IT administrators can eliminate manual user interaction, streamline device lifecycle management, and ensure devices are quickly brought under full management. Whether you’re looking to simplify migrations, accelerate deployments, or enhance compliance, this approach provides a scalable and user-transparent solution.
First of all let us have a look on all the 3 modes we have at Omnissa to managed Windows.
Hub Registered Mode:
Supports Tunnel , Assist , DEX , supports Scripts , Sensors and Apps Sample.
Hub Managed Mode (new in 26.02 ):
Same as Hub Registered plus , Commands like Lock & Wipe, Software Deployment , ADMX Profiles, Baselines
MDM Managed (with OMA-DM):
all above plus OMA DM Profiles , Compliance and all the Management Capapbilites Omnissa has on Windows.
While the recommendation is to go with a MDM Managed Mode with OMA-DM there are cases to start with Hub Registered to use the DEX Solution of Omnissa and then step up at some point. So let us first look on the Requirements:
– UEM 26.02 or newer
– Windows Intelligent Hub Version 26.02.1 or newer
– Hub Registered Mode Enrolled Device
– Desktop Essentials , Advanced and Enterprise SKU
Device before Migration
Before the Migration we see the App Inventory , we can use Tunne, Assist and all the DEX Data is there. But We can not use all Profiles and also we can not install Apps etc.
Go to “Devices & Users” , “General”, “Enrollment” and select the Management Mode Tab:
As the devices are in Hub Registered Mode the Settings should look similar like this:
To enable the Step up ensure the OG is allowed to use “Intelligent Hub Managed Mode” like shown here:
With this settings are are ready to migrate the Device.
API Call
the following API can be used to uplift the Enrollment Silent from Hub Registered to Hub Managed :
with UEM 26.02 / UEM 2604 the V3 API should be used. With a future version of UEM the V4 API can be used, but at the time of writing V3 was supported and working.
Intelligence Connector
As a single API Call might be nice for a Test, but we can also build a Automation in Intelligence, scope the Step up with filters etc.
I build a Custom connector for Intelligence to Update the Mode from Hub Registered to Hub Managed , it if available here :
https://github.com/EUCPatrick/Intel-Connector/blob/main/Windows%20Step%20up%20Registered%20to%20Hub%20Managed%202602%20v3.json
Once Added, it has automatically the Lookup Values from Intelligence and can be used in Automations:
Device Post Migration
Post Migration the Device has more UEM data and all the usual Action of a Hub Managed Device.
After a Reboot of the Device the Apps and Profiles are installing and all the new Capabilities are available for the User without any interruption.
vExpert, blogger and VMware & Omnissa champion. Worked 10 years as a Architect for a partner before joining VMware in 2017. Moved to Omnissa in 2024.