Oculus for Business casting functionality is incompatible with Google Chrome v.98.0.4758.102 or later. Use older versions of Google Chrome to continue casting with your Oculus for Business headset. For instructions on how to downgrade your Chrome version, please refer to this Google support page.
If the user removes an app from the headset though ITAP, the app will not be removed from the app library until an update has been applied while in admin mode.
AUI V1 with the bubbled environment might be displayed after provisioning a headset. To resolve this, the user must enable admin mode and select the "Check for Updates" button.
If the user adjusts their guardian while in a kiosk app, the environment might be displayed as all black. Reboot the headset or attempt to set the guardian again to recover.
Casting might fail to re-continue on a second attempt after the headset has been sitting idle for 15 seconds. To recover, reboot the headset and attempt to cast again.
If hand tracking is enabled in ITAP, the user will see the "Switch to Controllers" prompt after attempting to restart the app while using controllers. Select the "Continue" button using controllers to dismiss the prompt and continue the app experience.
Te in-headset experience is still seen after the headset has been removed from the user's head. The black casting screen will be seen after 15 seconds.
Users will be unable to dismiss the switch to controllers prompt from within an ingested kiosk app If hand tracking is enabled. Dismiss the prompt using controllers to continue the in-app experience.
If a user leaves their guardian while pass-through on demand is enabled, they will see an all-black environment. Reboot headset to recover.
If an app has been paused and the Wi-Fi panel has been launched, the AUI will disappear. Press the Oculus button on the right controller to display it again.
Non-ingested focus aware apps will display the oculus logo as a pause screen placeholder.
Users are unable to scroll through the storage manager drop-down using controllers.
USB debugging is enabled on headsets when it is displayed as disabled in ITAP.
If Guardian is disabled, pass-through will not be displayed while pairing controllers.
It is possible for a user to link to the wrong 3P MDM on the Apps page of Device Manager. As of v29, Device Manager will display a status of "Setting device owner failure".
The confirmation prompt for powering off or restarting the headset will now be displayed if the power button is pressed and held during enrolment.
The prompts for "Allow access to data" and "Allow USB debugging" will now be displayed if selected during enrolment.
The MDM panel will now automatically be launched on first boot of the headset after deploying the 3P MDM.
Apps added to a headset from the third-party MDM will no longer be blocked if the user had disabled "Enable sideloaded apps" in Device Manager.
The Wi-Fi panel will now be displayed if selected during enrolment.
The prompt for "Allow USB debugging" will only be displayed once now.
The Workspace ONE app will no longer force-close when the User selects "Done" after selecting the type of lock screen notification.
If the headset is moved into a different ITAP group during PIN selection, the user will no longer be left in a black environment.
Users can now adjust the guardian if they have not completed enrolment.
If you're experiencing a known issue listed below for Workspace ONE, please reboot the headset:
Directed to a panel about "Data sharing" after enrolling a headset. Click a button labelled "Agree" to continue. At this point, they may find themselves stuck on a loading screen.
Unable to launch an application after enrolling in Workspace ONE.
Stuck on a loading screen after the Workspace ONE app has been relaunched before an Internet connection is established.
Stuck in a dark environment after choosing "Yes" on the "You will need to start over and re-enter your information if you cancel" panel while enrolling.
Stuck on a blank Workspace ONE panel after clicking the One Hub app in the App Library while the app is already open.
Login fails or gets stuck after closing the login screen.
The message "Android recovery" error was displayed in the headset while the headset was updating, MDM Authority was changed for the headset in Device Manager. Press Vol-and Vol+ button to navigate the menu. Highlight Factory reset and press the power button to select the option.
Using 3P MDM on a private network that requires certificates instead of a SSID/password combination is possible but not supported. If you do attempt this, please check with your Security/IT department to verify that the username is valid and has the correct level of permissions.
A headset may disappear from Device Manager when switching from a third-party MDM back to Oculus Device Manager as the MDM. This will occur during provisioning. If this happens, please use the Oculus for Business Android app to provision the device again. It should re-appear in Device Manager.
Backing out of the Setup notifications screen after setting a PIN takes the user to the 3P MDM home screen, not the start of the set PIN flow. If you need to set/reset the PIN of a device managed by a 3P MDM, we suggest that you use the web console for the 3P MMD you used.
3P MDM applications are not seen in the App Library. This can occur when a headset that is enrolled in a 3P MDM is moved to a group with Device Manager that has sideloaded apps disabled. Set sideloaded apps to enabled.
If Admin mode is enabled, a user will be able to launch other apps before enrolment of the headset in a third-party MDM is complete.
Even though a user is enrolled and has set a device pin, they are redirected back to the device pin setup panel within the headset. The main cause of this is when a headset is moved from "All devices" to a group or vice versa. Re-enter the device PIN of choice. Try not to move devices between groups unless necessary.
Quest 2 devices are reported as "Quest" in the Device details of the MobileIron Go app.
During enrolment, the lock screen notification text may appear very dark for entries other than "Don't show notifications". Please select "Don't show notifications".
In some situations, the status of a headset will not display "Setting device owner failure" when a 3P MDM has been set to the wrong app. If you are having trouble setting a 3P MDM as the MDM authority, please check that you have linked the correct app in Device Manager on the Apps page.
The "Continue" button is not appearing on the enrolment page of MobileIron Go. Use the joystick on the controller to scroll down.
In some situations, the headset PIN does not change when changed from the Workspace ONE web console. If this happens, lock the headset from the web console then have the user don the headset and unlock it. At that point, it should start accepting a PIN change from the web console.
When moving a headset that is enrolled in WorkSpace ONE into and out of groups in Device Manager, the device lock pin can sometimes get stuck. Use the WorkSpace ONE web console to change the device pin of the headset.
After unenrolling the headset from Workspace ONE, the user in the headset will be in a completely dark environment with three dots floating in front of them. The user should press the Oculus button on the right controller. This should return the user to the proper environment.
In some situations, the status under Mobile Device Manager for a headset in Device Manager does not appear as "Installed" after a third-party MDM has been assigned. If this happens, try the following:
Try to provision the headset again with the Oculus for Business app.
Make sure that you refresh the Device Manager page as the status does not update without a refresh.
Take a look in the headset and verify that it is not stuck on a "Setting up" message.
If the message for the status mentions a failure or it still does not say Installed, set MDM authority back to Oculus Device Manager. Then, verify in the headset that Enterprise UX loads completely. Once Oculus Device Manager has been verified as working, change MDM Authority to the 3P MDM and try to enrol.
In the latest build, the Workspace ONE App panel automatically opens in dark mode. If the user does not like this, it may be disabled from settings after enrolment.
We're investigating the following issues and are working to resolve them in future updates:
"Setup incomplete" error showing during device provisioning. If this happens, wait a few hours to see if it goes away. If it doesn't:
Factory reset the headset.
When the device has been turned off, press and hold the volume down and power buttons until you see a menu appear.
Select the factory reset option.
Once the device has reset, put the headset on and connect to your available Wi-Fi connection.
Once you've connected to Wi-Fi, the Oculus Introduction video will begin. During the video, your headset will reset and install the Enterprise software.
Home screen environment appears black if an app is closed after leaving and returning to the Guardian area. If this happens, relaunch the closed app.
Fixed an issue where it was difficult to pair the second controller when selecting "Next controller" during controller pairing. If this happens, pair the second controller separately.
If the headset is left idle while casting and goes into sleep mode, the screen may be black when casting resumes. If this happens, reboot the headset.
Sideloaded apps deleted from the headset do not appear as deleted. If this happens, let the headset idle and then awaken it from sleep mode.
Apps removed from Device Manager still appear in the headset. If this happens, reboot the headset.
Switching from an app that supports hand tracking to an app that doesn't causes the "Switch to hands" prompt to appear. If this happens, fully close both apps before relaunching the app that doesn't support hand tracking.
Pausing focus overlay-enabled app shows an Oculus placeholder image on the pause panel instead of an in-app screenshot or thumbnail.
Drawing a large guardian area causes the tool to function unexpectedly.
Apps installed in Device Manager appear in App Library instead of Unknown sources.
Pass-through not displayed when pairing controllers if Guardian is disabled.
Hand tracking tutorial audio does not play when tutorial is launched.
Apps with long names block the "Quit" button in VR.