VMware Workspace ONE XR Hub is a companion to Workspace ONE Intelligent Hub that provides an enterprise experience and cross-platform native launcher for Virtual Reality (VR) devices. XR hub provides secure and simple access to corporate applications and content on a wide variety of standalone eXtended Reality (XR) devices.
XR Hub works with Workspace ONE UEM to provide secure access to native VR and remote XR applications and shared device check-in/check-out functionality. XR Hub can also be used with Workspace ONE Access to provide advanced authentication and unified application catalog purposes.
Client Components
Cloud/Server Components
Workspace ONE UEM combined with Workspace ONE Access (optional) provides the best approach enabling your XR device fleet.
See the XR Hub Device Interoperability Matrix for the current list of supported devices.
The following XR devices are compatible with Workspace ONE XR Hub 23.04.
Note: When enrolling a device using Workspace ONE Intelligent Hub, Device Owner admin rights are granted as part of the enrollment process. If this device is later unenrolled from Workspace ONE UEM, a factory reset is automatically performed as part of the unenrollment process, erasing all files and content from the device.
Before configuring XR Hub, you should understand the different deployment options available.
Recommended: Device Management with Secure Launcher and Unified App Catalog
Minimum: Device Management with Secure Launcher
VR Streaming: Device Management with Secure Launcher, Unified App Catalog, and VR Streaming
Managing VR devices with Workspace ONE UEM allows you to remotely control, secure, manage, and support devices. XR Hub must be remotely installed on VR devices managed by UEM. UEM provides additional functionality to XR Hub such as shared device check in / check out, Single Sign-On and remote configuration.
To manage VR devices with UEM, the device must be “enrolled” first. UEM supports manual, scripted, and QR code enrollment for VR device setup and management.
For details on setting up VR devices with Workspace ONE UEM, see https://techzone.vmware.com/resource/extended-reality-xr-device-management-vmware-workspace-one-uem.
Once a device is enrolled into Workspace ONE UEM, XR Hub can be deployed and used on that VR device.
You must use Workspace ONE UEM to configure and deploy XR Hub. XR Hub must be uploaded as an application to UEM before configuration can take place. It is recommended as a best practice to have a separate organization group (OG) per device vendor. Take the following steps per device vendor (HTC, Meta, PICO).
Select the Continue button on the Add Application screen. The Add Application - XR Hub v xx.xx screen displays. The uploaded APK prepopulates all the required fields so you can accept the default values or make customization per your preferences.
Select the More tab followed by SDK.
In the Distribution tab, enter the following information.
| Setting | Description |
|---|---|
| Name | Enter an assignment name for the deployment assignment. |
| Description | Enter the assignment description. |
| Assignment Groups | Enter the smart group name(s) for your VR headsets. |
| Deployment Begins On | For a typical as-soon-as-enrolled deployment use the default value. |
| App Delivery Method | For a typical as-soon-as-enrolled deployment choose Automatic. |
Move to the Restrictions tab, and enable the Managed Access slider.
Move to the Application Configuration tab and enable the Send Configuration slider. The Application Configuration screen displays with its full compliment of options. Enter the following information.
Note about configuring URLs in this section Most options here accepting URLs can instead accept a file based URL that references a file stored locally on the device rather than a web hosted file. The format used must be file:///storage/emulated/0/[path and fileame] for example file:///storage/emulated/0/vmware/company_logo.jpg. Based on the version of Android OS used by the device, there might be limitations on file system access.
| Setting | Description |
|---|---|
| Workspace ONE Access URL | If you are using Workspace ONE Access for user authentication, then THIS URL MUST BE SET TO THE WORKSPACE ONE ACCESS SERVER FQDN (not the Workspace ONE UEM server). Optionally, the end user can enter another URL from within the client at any time by using the Change Workspace One Domain button at the bottom of the login window. Example: https://myvmware.workspaceair.comIf you are using Workspace ONE Access and this option is not configured, the user will be prompted for the URL (not a recommended user experience). |
| Entitlement Refresh (mins) | Standard Setting Workspace ONE Access entitlements are refreshed manually with the refresh button within the XR Hub Client (top right) and also automatically refreshed with a timed interval. By default, this interval is set to 8 hours (480 minutes) but can be altered using the “entitlementsRefreshMinutes” setting. VMware recommends to leave this interval set to the default value. |
| Enable Kiosk Mode (Meta Quest 2 Consumer) | Standard Setting If you are using the Meta Quest 2 consumer device, set this value to enable so that XR Hub launches on device startup. Refer to Kiosk Mode for Meta Quest 2 for required steps to enable kiosk mode. |
| Tutorial Video URL | Standard Setting Enter the URL of an mp4 video to display first launch of XR Hub and subsequent launches after a user has logged out. If this is left blank, no video is shown. |
| Allow Skip Tutorial | Standard Setting If you are pushing a custom video tutorial to the device to be displayed in XR Hub, you can set this to enable to allow the user to skip the tutorial on first use. Setting it to disable prevents the user from logging in until the video has finished playing. |
| Config Entitlements Only | THIS OPTION MUST BE ENABLED ONLY WHEN WORKSPACE ONE ACCESS IS NOT USED to specify that the app catalog is defined with client configured entitlements only. This prevents XR Hub from attempting to authenticate with Workspace ONE Access. Shared devices managed by UEM still prompt users to check out a device with username and password if the device is checked in and clientConfigEntitlementsOnly is set to enable.In summary, Enable this option when you are NOT using Workspace ONE Access. Disable this option when you ARE using Workspace ONE Access. |
| Show All Installed Applications | Standard Setting Enable this to show all launchable applications that are installed on the device under the Immersive Apps filter. Note: Some apps, including Intelligent Hub, Tunnel, and XR Hub are automatically filtered out. |
| Ignore Shared Device Checkout | Standard Setting If you have enrolled a device as a shared device but do not want users to checkout the device, set this to enable. This is only relevant to deployments where devices maybe pre-enrolled as shared devices and then moved automatically to another user account. |
| Loading Screen Custom Logo URL | Standard Setting The URL of a logo (image) to display above the spinner animation on the XR Hub loading screen. If this is left blank, no logo is displayed. |
| Intro Web Page URL | Standard Setting The URL of a webpage to display after XR Hub as loaded. If this is blank, no web page is shown. |
| Application Window Logo URL | Standard Setting The URL of a logo (image) to display at the top of the XR Hub application screen. If this is left blank, the logo from the console branding is used. |
| Custom Credential Configuration | Advanced Setting XR Hub can be configured to pass a username or email address to a native application that is launched by XR Hub. This is only required if not using Workspace ONE Access for SSO. Click on Configure.  The Custom Credential field settings:
|
| Enable SSO | Standard Setting Setting Enable SSO to enable enables SSO. You can stop (Workspace ONE Access) single sign-on to XR Hub by setting this to disable. |
| Authorization Profile: | Standard Setting If you are managing shared devices and the check out process requires Multi-Factor Authentication (MFA) then set this to MFA. If your check out authentication flow only requires username and password set this to SFA for Single Factor Authentication. |
| XR Environment Theme | Advanced Setting Select the environment background you wish to present in XR Hub. For more information, see Customize XR Hub User Experience. |
| XR Environment Type | Advanced Setting Select a type:
|
| XR Environment Custom Skybox URL | Advanced Setting Set to asset url, to override skybox when using Default Office with Custom Logo theme. See Customize XR Hub User Experience. |
| XR Environment Custom Models | Advanced Setting Configure a custom 3D environment or custom 3D logo for XR Hub. The environment theme must be set to Default Office with Custom Logo theme or a custom environment theme. Only one environment model (for a custom environment theme) or one logo model (for the Default Office with Custom Logo theme) can be set. Click on Configure to configure the model.  For more information, see Customize XR Hub User Experience. |
| XR Environment Custom Artwork | Advanced Setting Specify the URLs for the Top, Left, and Right artwork to show on the back wall when using the Default Office with Custom Logo theme. See Customize XR Hub User Experience. |
| Applications | Standard Setting You can manually define native, web, WebXR, and remote XR applications to appear in the XR Hub application window. If not using Workspace ONE Access, applications must be defined here to appear in the XR Hub application window. Click Configure to add applications.  The Application field settings are:
|
| CloudXR Windows Client Path | Advanced Setting Not applicable for the current version of XR Hub. |
| CloudXR Android Client Bundle ID | Advanced Setting If accessing CloudXR applications with VMware Horizon, Workspace ONE Access, or manually defined Remote XR applications, then define the bundle ID of the CloudXR client you push to the XR device. For example, com.nvidia.cloudxr.ovr. |
| Entitlement Filters | Standard Setting Using entitlement filters you can hide or ensure applications are shown first in the XR Hub application window. Click Configure to add entitlement filters.  The Entitlement Filter settings are:
|
| Firmware Updates | Not currently supported with this version of XR Hub. |
| Max Window Drag Height | Advanced Setting Use this to specify how high a user may drag UI windows within the XR Hub environment. This is useful when using a custom made environment. |
| Min Window Push Distance | Advanced Setting Use this to specify how close a user may drag UI windows within the XR Hub environment. This is useful when using a custom made environment. |
| Max Window Push Distance | Advanced Setting Use this to specify how far away a user may drag UI windows within the XR Hub environment. This is useful when using a custom made environment. |
| StyleSheet URLs | Advanced Setting Specify the URL of the StyleSheet used to configure the color scheme of XR Hub. See Customize XR Hub User Experience. |
| WebXR Browser Configuration | Advanced Setting This setting enables you to define what WebXR browser or package should be used to launch WebXR applications from XR Hub. It should be noted that any browser or application should be configured for Single Sign-On (SSO) to avoid the user from being presented with a Workspace ONE password login flow (if using Workspace ONE Access). Click Configure to configure a WebXR browser. The settings below can be used for the Wolvic VR Browser on Meta Quest:  The following settings can be used for Mozilla Firefox browser on PICO or VIVE Focus devices:  |
Select Create.
Configure flexible deployment settings for your application by editing the schedules and priority for your deployments. Options that are displayed on this window are platform-specific.
| Setting | Description |
|---|---|
| Copy | From the ellipses-vertical, you can click copy if you choose to duplicate the assignment configurations. |
| Delete | From the ellipses-vertical, you can delete to remove the selected assignment from the application deployment. |
| Priority | You can modify the priority of the assignment you configured. Priority is from 0 to N with 0 being the highest priority. For a typical as-soon-as-enrolled deployment, this is set to 0. |
| Assignment Name | View the assignment name. Click for details. |
| Description | View the assignment description. |
| Smart Groups | View the assigned smart group. Click for details. |
| App Delivery Method | View how the application pushes to devices. Auto pushes immediately through the Workspace ONE UEM Catalog with no user interaction. On Demand pushes to devices when the user initiates an installation from a catalog. |
| EMM Managed Access | View whether the application has adaptive management enabled. |
Select the Exclusions tab and enter smart groups, organization groups, and user groups you want to exclude from receiving this application.
Select Save & Publish.
You can make changes to an XR Hub configuration that is already uploaded or assigned.
Any changes made to the application configuration are pushed to devices automatically. Users are alerted to the fact that a new configuration is available and they are asked to restart XR Hub from the users menu.
) to the left of the listing for XR Hub. The Edit Application - XR Hub screen displays.Using Workspace ONE Access is the recommended approach when deploying XR Hub as it provides you the ability to publish any Workspace ONE UEM, Workspace ONE Access, or Horizon managed applications to the XR Hub application launcher. In addition, Workspace ONE Access integration enables advanced authentication flows such as third-party identity providers (Okta, Ping, Active Directory, Azure Active Directory), conditional access, Single Sign-On (SSO), Multi-Factor Authentication, and so on.
For more information, see Configuring Authentication Methods in VMware Workspace ONE Access.
Configuring Workspace ONE XR Hub in this way informs Workspace ONE Access that any XR Hub Client is a trusted client for authentication purposes. The following instructions enable you to register the XR Hub Client Template ID and redirect URI with Workspace ONE Access.
Log in to the Workspace ONE Access admin console using your tenant admin account.
Select Settings.
Select the Add Template button. The Create Template dialog box displays.
This dialog box allows you to enter the XR Hub Client Template ID and Redirect URI. It also lets you choose what types of information (Scopes) your app requests from Workspace ONE Access and the user during End User Authentication.
http://localhost:3000/
If deploying custom assets or files to Meta Quest 2 devices with Workspace ONE UEM, then XR Hub must be explicitly given Read/Write permissions to access files pushed by UEM.
Select Add > Add Profile, then select Android as the platform.
Give a name for the profile such as XR Hub Read/Write Permissions.
Enter the following in the Custom Settings text field:
<characteristic uuid="ece876fd-da7d-424f-9bab-85a1b483e95e" type="com.airwatch.android.androidwork.permissions" target="1">
<parm name="MasterRuntimePermission" value="1" type="integer" />
<parm name="AppLevelRuntimePermissions" value="W3sicGFja2FnZU5hbWUiOiJjb20udm13YXJlLnhyLnhyaHViLnF1ZXN0IiwicGVybWlzc2lvbnMiOlt7Im5hbWUiOiJhbmRyb2lkLnBlcm1pc3Npb24uUkVBRF9FWFRFUk5BTF9TVE9SQUdFIiwidmFsdWUiOiIwIn0seyJuYW1lIjoiYW5kcm9pZC5wZXJtaXNzaW9uLldSSVRFX0VYVEVSTkFMX1NUT1JBR0UiLCJ2YWx1ZSI6IjAifV19XQ==" type="string" />
</characteristic>
Select Next
Additionally, you must grant All File Access permission to the Workspace ONE Intelligent Hub client. For more information, see https://techzone.vmware.com/resource/extended-reality-xr-device-management-vmware-workspace-one-uem.
You can configure a VR device to automatically launch XR Hub at device boot.
The process to set up Workspace ONE XR Hub as the first app to launch differs between supported headsets.
Note: For Meta Quest devices, the configuration must be done as part of staging, before the device is sent to the user.
Kiosk mode for the HTC VIVE Focus 3 and XR Elite requires pushing an xml configuration file to the device and running an Intent to trigger it.
Navigate to Devices > Provisioning > Components > Conditions.
a. Click the ADD CONDITION button, then select Android as the platform. The Create Condition screen displays.
b. Complete the Condition Settings.
| Setting | Value |
|---|---|
| Name | XR Hub for HTC |
| Description | XR Hub for HTC is installed |
| Condition | File |
c. Select the Next button.
d. Enter the Condition Details
| Setting | Value |
|---|---|
| File Name | /$internal$/Android/data/com.vmware.xr.xrhub.wavevr |
| Condition Met When | File Found |
| Frequency | 15 minutes |
| Duration | 1 Day |
| After Duration Exceeded | Pass Condition |
e. Select the Save button.
Navigate to Devices > Provisioning > Components > Files/Actions.
a. Use the ADD FILES/ACTIONS button at the top of the page to create a new File/Action.
b. Select Android.
c. Configure the General Tab
| Setting | Value |
|---|---|
| Name | Download HTC XML Config |
| Description | Optional description. |
| Managed By | Prepopulated with the correct OG. |
d. Move to the Files tab and select ADD FILES.
e. Select Choose Files and upload a copy of the mns.xml file shown below, after the last step.
f. Select Save to save the file.
g. Specify the download path as $internal$/VMware and select Save to save the configuration.
h. Move to the Manifest tab.
i. Select ADD ACTION under the Installation Manifest section.
j. In the Action(s) To Perform drop-down, select Run Intent.
k. For Command Line and Arguments to run, enter
mode=explicit,broadcast=false,action=com.htc.vr.launcher.SCENE,package=com.htc.vrs.launcher,class=com.htc.vr.unity.WVRUnityVRActivity,extraString=LaunchScene=UpdateKioskMode
l. Select Save to save the Files/Action.
Navigate to Devices > Provisioning > Product List View.
a. Select Add Product and select Android.
b. Configure the General tab.
| Setting | Value |
|---|---|
| Name | HTC Kiosk Mode Config |
| Description | Optional description. |
| Managed By | Prepopulated with the correct OG. |
| Smart Groups | Enter the Smart Group(s) that the product is applied to. |
c. Move to the Manifest tab, select the +Add button, and configure the following.
| Setting | Value |
|---|---|
| Actions(s) to Perform | File/Action - Install |
| Files/Actions | Select the File/Action created above, called “Download HTC XML Config” |
d. Move to the Conditions tab and select Add for Install Conditions.
e. In the dropdown list box, select the Condition you created above, named “XR Hub for HTC”.
f. Select the Save button to save the product. If ready to activate Kiosk Mode, select the Activate button to give the Product an active status.
If you want to activate the product later, navigate to the Product List View page, locate the “HTC Kiosk Mode Config” product from the listing, select the grey indicator next to the red traffic light for the product. The grey indicator turns green and the red indicator turns grey to indicate that the product is now active.
Kiosk mode XML file - mns.xml
<?xml version="1.0" encoding="UTF-8"?>
<customization_form>
<category name="application">
<module name="vive_kiosk_enabler">
<function name="enable_kiosk_mode">
<set name="single">
<!--
1:enable kiosk mode.
0: disable kiosk mode
-->
<item name="enabled" type="bool">1</item>
</set>
</function>
<function name="kiosk_mode_key">
<set name="single">
<!-- [TO DO] Enter a passcode to leave kiosk mode. Needs to be a 4 digit number. Empty means no passcode to leave Kiosk mode -->
<item name="key" type="int">0000</item>
</set>
</function>
<!-- allow BT connection or not -->
<function name="allow_bt_connection">
<set name="single">
<item name="enabled" type="bool">1</item>
</set>
</function>
<!-- allow headset screen casting not -->
<function name="enable_screen_casting">
<set name="single">
<item name="enabled" type="bool">1</item>
</set>
</function>
<!-- allow screen capture or not -->
<function name="kiosk_screen_captured_enable">
<set name="single">
<item name="enabled" type="bool">1</item>
</set>
</function>
<!-- allow USB file transfer or not -->
<function name="allow_usb_transfer">
<set name="single">
<item name="enabled" type="bool">1</item>
</set>
</function>
<!-- setup application in kiosk mode -->
<function name="kiosk_mode_apps">
<set name="plenty">
<item name="app_name">XR Hub</item>
<item name="app_package_name">com.vmware.xr.xrhub.wavevr</item>
</set>
</function>
<!-- kiosk mode type
"1" for Single app
"2" for Multiple app
-->
<function name="kiosk_mode_type">
<set name="single">
<item name="enabled" type="int">1</item>
</set>
</function>
<!-- Network permission under kiosk mode
"1" for Offline
"2" for Pre-defined Wifi
"3" for Allow to any Wifi
-->
<function name="allow_network_permission">
<set name="single">
<item name="mode" type="int">3</item>
</set>
</function>
<!-- require sign in mandatory when entering kiosk mode -->
<function name="enable_kiosk_mode_signin">
<set name="single">
<item name="enabled" type="bool">0</item>
</set>
</function>
<!-- Interaction method
"1" for hand only
"2" for controller only
"3" for controller & hand
-->
<function name="kiosk_InteractionMode">
<set name="single">
<item name="mode" type="int">3</item>
</set>
</function>
<!-- play tutorial when re-start kiosk mode -->
<function name="kiosk_auto_play_tutorial">
<set name="single">
<item name="mode" type="bool">0</item>
</set>
</function>
<!-- play opening video when re-start kiosk mode -->
<function name="kiosk_cinematic_playback">
<set name="single">
<item name="mode" type="bool">0</item>
</set>
</function>
<!-- play wearing guide when re-start kiosk mode -->
<function name="kiosk_auto_play_wearing_guide">
<set name="single">
<item name="mode" type="bool">0</item>
</set>
</function>
</module>
</category>
</customization_form>
Kiosk mode can be configured on Pico devices by pushing a configuration file to the device.
Navigate to Devices > Provisioning > Components > Files/Actions.
a. Select the ADD FILES/ACTIONS button at the top of the page and Select Android.
b. Configure the General Tab
| Setting | Value |
|---|---|
| Name | Download HTC XMl Config |
| Description | Optional description |
| Managed By | Prepopulated with the correct OG. |
c. Move to the Files tab and select the +ADD FILES button. Select Choose Files and upload a text file called config.txt with the following contents, then select Save.
open_guide:1
------
home_pkg:com.vmware.xr.xrhub.picovr
------
$internal$/VMware, then select the Save button.In the Workspace ONE UEM console, navigate to Devices > Provisioning > Product List View.
a. Select the ADD PRODUCT button at the top of the page and select Android.
b. Configure the General tab
| Setting | Value |
|---|---|
| Name | PICO Kiosk Mode Config |
| Description | Optional description. |
| Managed By | Prepopulated with the correct OG. |
| Smart Groups | Enter the Smart Group(s) that the product is applied to. |
c. Move to the Manifest tab and select the +ADD button to add a manifest using these settings.
| Setting | Value |
|---|---|
| Actions(s) to Perform | File/Action - Install |
| Files/Actions | Select the File/Action created in step 2 above. |
d. Select the Save button to save the product. If ready to activate Kiosk Mode, select the Activate button to give the product an active status.
If you want to activate the product later, navigate to the Product List View page, locate the “PICO Kiosk Mode Config” product from the listing, select the grey indicator next to the red traffic light for the product. The grey indicator turns green and the red indicator turns grey to indicate that the product is now active.
Reboot the device for it to take effect
At time of writing, native Kiosk mode is not available for Meta Quest devices. VMware implements some of the typical Kiosk mode functionality into XR Hub but the following limitations should be noted.
Give XR Hub delegated administration rights via a device profile.
Enter the following in the Custom Settings text field:
<characteristic uuid="ee0cdec3-e7c3-4aa6-a8c0-3f3b12fde2sc" type="com.airwatch.android.androidwork.delegatedScopes">
<parm name="delegationAppRestrictions" value="True" />
<parm name="delegationAppRestrictionsAppName" value="XR Hub" type="string" />
<parm name="delegationAppRestrictionsAppId" value="com.vmware.xr.xrhub.quest" type="string" />
<parm name="delegationPermissionGrant" value="True" />
<parm name="delegationPermissionGrantAppName" value="XR Hub" type="string" />
<parm name="delegationPermissionGrantAppId" value="com.vmware.xr.xrhub.quest" type="string" />
<parm name="delegationPackageAccess" value="True" />
<parm name="delegationPackageAccessAppName" value="XR Hub" type="string" />
<parm name="delegationPackageAccessAppId" value="com.vmware.xr.xrhub.quest" type="string" />
</characteristic>
Select Next
Run ADB commands to allow Kiosk Mode
The Meta Quest device must be in developer mode, see https://techzone.vmware.com/resource/extended-reality-xr-device-management-vmware-workspace-one-uem.
After XR Hub is installed and the device is in developer mode, run the following ADB commands to allow XR Hub to run as a kiosk mode application.
adb -d shell pm grant com.vmware.xr.xrhub.quest android.permission.SYSTEM_ALERT_WINDOW
adb -d shell pm grant com.vmware.xr.xrhub.quest android.permission.READ_LOGS
Ensure the setting Enable Kiosk Mode (Meta Quest 2 Consumer) is enabled in the XR Hub application configuration.
After Enabling Kiosk Mode: - Ensure the device is set up with Wi-Fi network access prior to launching XR Hub. - XR Hub must be launched at least once, to recieve the kiosk mode configuration, and trigger the kiosk mode functionality. - On reboot, XR Hub launches automatically and prevents the user from accessing the Quest Home, system settings, or other applications. - To disable Kiosk Mode, disable the Kiosk Mode setting in the XR Hub application configuration and push to the device.
Workspace ONE UEM can push files to XR devices using the Product Provisioning functionality. “Product” in this case is referring to the files/actions that are grouped together with deployment rules.
Note: For Android 11+ based devices, some file system locations may be inaccessible to either Workspace ONE Intelligent Hub (which places the files on the device) or to the application that is attempting to read these files. For example, Android 12 based devices (Meta Quest) restrict access to application folders such as Android/data and Android/obb. Ensure that you grant All File Access permission to the Workspace ONE Intelligent Hub client. For more information, see https://techzone.vmware.com/resource/extended-reality-xr-device-management-vmware-workspace-one-uem.
Navigate to Devices > Provisioning > Components > Files/Actions and select the Add Files/Actions button followed by Android as the platform. The Add Files/Actions screen displays.
a. Complete the General tab.
| Setting | Value |
|---|---|
| Name | Descriptive name of the file being sent to the device. |
| Description | Optional description of the file being sent to the device. |
| Managed By | Prepopulated with the correct OG. |
b. Move to the Files tab.
c. Select the Add Files button. The Add Files window displays.
d. Select Choose Files and browse for the file you want to deploy.
e. Select Save to upload the selected file(s).
f. Specify the Download Path such as $internal$/VMware/foldername and click Save.
Note: When pushing custom files for XR Hub to a device, you must ensure that the XR Hub application configuration is pointing to the corresponding location of any custom file. For example, ensure that any custom model, artwork etc is configured in the XR Hub application configuration to point to the location where the custom file is deployed. We recommend pushing files to the following location:
/$internal$/vmware/folder/filename
Note: - If you selected multiple files, you can specify a distinct Download Path for each file. - If the path entered does not exist on the device, the installation creates the folder structure. - If you support more than one model headset, then you must create separate File-Actions attached to separate products, one for each model. - If you have at least one file uploaded, you do not require a Manifest Action.
Navigate to Devices > Provisioning > Product List View and select the Add Product button followed by Android as the platform.
a. In the General tab, apply the following settings.
| Setting | Value |
|---|---|
| Name | Provide a name for the product that you can recognize and pick from a list later on. |
| Description | Optional description. |
| Managed By | Prepopulated with the correct OG. |
| Smart Groups | Enter the Smart Group(s) that the product applies to. |
c. In the Manifest tab, select the +ADD button and configure the manifest with the following settings.
| Setting | Value |
|---|---|
| Actions(s) to Perform | Select “File/Action - Install”. |
| Files/Actions | Select the File/Action created in step 2 above. |
d. Select the Save button to save the manifest to the product.
e. Select the Save button to save the product. If ready to activate Kiosk Mode, select the Activate button to give the product an active status.
If you want to activate a saved product later, navigate to the Product List View page, locate the name of the product (from step 3a above) from the listing, select the grey indicator next to the red traffic light for the product. The grey indicator turns green and the red indicator turns grey to indicate that the product is now active.
If using XR Hub with devices enrolled as multi-user (shared devices) or single-user staging accounts, Workspace ONE UEM automatically attempts to install and launch Workspace ONE Launcher. However, Launcher interferes with the operation of XR Hub, so it is important to block Launcher from running.
Add an Application Group to disable the default Workspace ONE launcher. This prevents Launcher from launching when booting a shared device.
Navigate to Groups & Settings > Groups > App Groups and select Add Group. The Add Application Group screen displays.
For Type, select Denylist.
Select the +Add Application link.
a. Under Application Name, enter “Launcher”
b. Under Application ID, enter com.airwatch.lockdown.launcher
Select Next. The Assignment tab displays.
