After you run the Getting Started wizard in the Workspace ONE UEM console to establish the trusted relationship between the two services, you go to the Omnissa Access console, to complete the setup.
| Configuration Page | Description |
|---|---|
| Workspace ONE UEM Configuration | The Workspace ONE UEM settings created in the Getting Started wizard are populated to the UEM Integrations page in the Omnissa Access console. To complete the configuration, you can enable Domain Mapping and verify that the App Catalog setting is correct. |
| Compliance Check | You enable compliance checking in the Omnissa Access console Integrations > UEM Integration page and configure Device Compliance in the Integrations > Authentication Methods page to verify that Workspace ONE UEM managed devices adhere to Workspace ONE UEM compliance policies. When you configured Device Compliance authentication, you configure access policy rules to check the Workspace ONE UEM server for device compliance status when users sign in from their devices. See Enabling Compliance Checking for Workspace ONE UEM Managed Devices in Omnissa Access. |
| User Password Authentication through Workspace ONE UEM | Password Authentication with Workspace ONE UEM authenticates using AirWatch Cloud Connector through the Workspace ONE UEM service. When AirWatch Cloud Connector is used, you enable User Password Authentication through Workspace ONE UEM in the Omnissa Access console Integrations > UEM Integration page and configure Password (with Workspace ONE UEM) authentication in the Integrations > Authentication Methods page. You create access policies to apply to this authentication method. See Implementing Authentication with AirWatch Cloud Connector. |
| User External Access Token Authentication through Workspace ONE UEM | When users receive a new Dell® Windows 10+ device with out-of-box (OOBE) provisioning enabled in the Workspace ONE UEM Windows 10 Provisioning Service, you can enable User External Access Token Authentication through Workspace ONE UEM in the Omnissa Access console Integrations > UEM Integration page and configure Workspace ONE UEM External Access Token authentication in the Integrations > Authentication Methods page to manage Workspace ONE Intelligent Hub app logins. |
Enable Domain Mapping and Workspace ONE Intelligent Hub App Catalog
Enable Domain Mapping to map Workspace ONE UEM Organization Group (OG) to the user's domain in the Omnissa Access service to register that user's devices to the OG. See Mapping Omnissa Access Domains to Multiple Organization Groups in Workspace ONE UEM.
The Fetch from Workspace ONE UEMis automatically enabled in the Catalog section to include apps from the Workspace ONE UEM catalog. The Workspace ONE Intelligent Hub app catalog displays web and virtual apps configured in the Omnissa Access console and native apps and web links configured in the Workspace ONE UEM console. The Device Service URL for new device enrollment with UEM is automatically configured.
-
In the Omnissa Access console Integrations > UEM Integration page, scroll down to the Domain Mapping section.
-
Enable Map Domains to Multiple Organization Groups.
-
Select a domain from the drop-down menu.
-
Add the Workspace ONE UEM organization group for that domain, the API key, and the Workspace ONE UEM name.
Click ADD ORGANIZATION GROUP to add another organization group to the domain.
-
-
Verify that Fetch from Workspace ONE UEM is selected and the Device Services URL listed is correct.
-
Click Save if you made any changes.
Was this page helpful?