Please provide your feedback in this short Flings' survey.
fling logo of Workspace ONE ConQuest

Workspace ONE ConQuest

version 2 — November 09, 2022

Contributors 4

View All

Comments 1

  • profile picture of joel_prefontaine
View All

Summary

ConQuest configures Meta Quest 2 VR consumer devices and enrolls the device into Workspace ONE UEM. ConQuest is available as a GUI or CLI application for Microsoft Windows. It can be run once a Meta Quest 2 device is set to developer mode and connected to the Windows device via USB.

Running ConQuest will install Workspace ONE Intelligent Hub App as device owner so that the device can be enrolled into Workspace ONE UEM. ConQuest will launch Intelligent Hub App and automatically enroll the device into Workspace ONE UEM using credentials supplied.

There are two versions of ConQuest. ConQuestGUI, which will run as an application from the desktop on Windows. ConQuestCLI, which will run from the command line on Windows. You only need one of these applications as both perform the same actions on the headset.

ConQuest should not be used on Oculus for Business or Quest for Business registered devices.

Requirements

  • Meta Quest 2 Consumer Edition – Firmware v40+
  • Windows Laptop / PC
  • USB-C Cable

Instructions

Initial Setup

Make sure your device is charged and that both controllers have batteries and are charged

Ideally, the device should have not been previously setup. If so, factory reset the device using the Oculus Mobile App.

Before enrolling the device into Workspace ONE UEM, the Meta Quest 2 device must be connected to the Oculus Mobile App. Follow these instructions to do so.

If you're new to Meta, or using Meta Quest, a Facebook or Oculus Test account (https://developer.oculus.com/resources/test-users/) is required to use your device, apps and the app store. Setup a Facebook or Oculus Test account before using the device.

Download and install the Oculus Mobile App to your iOS or Android device. Login with your Facebook or Oculus Test Account credentials.

Your user will need to be registered as a developer in order to enroll devices using ConQuest. You can register as a developer by joining an existing organisation or creating a new one.


To join an existing organization, follow these steps:

  1. You’ll need to request access to the existing organization from the admin.
  2. You’ll receive an email invite. Once accepted, you’ll be a member of the organization.

To create a new organization, follow these steps:

  1. Go to https://developer.oculus.com/manage/organizations/create/
  2. Fill in the appropriate information.

Device Setup and Configuration

To setup your device for Workspace ONE UEM enrollment follow these steps:

  1. Download Workspace ONE ConQuest from here https://flings.vmware.com/workspace-one-conquest
  2. Connect the Meta Quest 2 to PC using USB Cable (may need to use a phone USB-C cable)
  3. Power on your device and press the Oculus button on both controllers to wake them
  4. Follow instructions in Oculus Mobile App to pair your headset with the Mobile app.
  5. Once paired, in the Mobile App, select Menu, Devices and select your headset in the dropdown.
  6. Configure a Wi-Fi using the Oculus Mobile App
  7. Under Headset Settings, select Developer Mode and toggle on Developer Mode.
  8. If you cannot enable Developer Mode, put on the headset and go through Meta device setup until 1 of 2 updates are applied by Meta. Then continue with ConQuest.
  9. Put on the headset and Allow Connections to PC (in the Oculus Headset)
  10. Note, make sure to authorize USB debugging in the headset when prompted (you maybe asked to do this several times)
  11. If the Quest does not offer the 'Allow USB Debugging' prompt after turning on Developer Mode and connecting the USB cable; ADB may need to be restarted. Running 'adb kill-server' and 'adb start-server' at the commandline may solve the issue. ADB can be found in the 'ConQuest/ADB' folder of the ConQuest download.
  12. Extract the ConQuest zip (or install the ConQuest for MacOS) and run the ConQuest (ConQuestConsole) executable
  13. The ConQuestConsole executable will need to be given executable permissions on macOS/Linux (chmod +x)
  14. If you encounter warnings about running a downloaded app on macOS, these can be bypassed by downloading ConQuest to a different machine and then transferring the zip to the Mac via a USB storage device
  15. If necessary configure ConQuest to use a different version of ADB or Intelligent Hub App
  16. Click Check Device to ensure ConQuest can see the connected device
  17. Configure UEM credentials for enrollment. You may skip this (so that the user has to enter credentials), use a credentials.bin file (created via the UEM Sideload Staging Wizard) or enter credentials.
  18. Click Next and Run
  19. ConQuest should quickly go through a process to configure the headset and launch Intelligent Hub App and auto enroll the device using the credentials supplied.
  20. Monitor progress in the connected headset.
  21. Accounts may be detected and automatic removal of those accounts will be attempted.
  22. If ConQuest gets stuck on removing accounts, you will need to stop ConQuest and re run it. Ensure that when the Quest Accounts Settings UI pops up that you use the controller to select an account(s) and remove it manually.
  23. Workspace ONE ConQuest is complete when the headset is at the privacy statement to click through, click the agreement and device setup will take a few minutes to complete.
  24. From the Customer or Child OG, within the Workspace ONE UEM Console, navigate to Devices > List View. You should see your device enrolled into the Workspace ONE UEM Console. You should now be able to manage these devices using Android Enterprise based profiles.

Changelog

Version 2

  • New GUI to support Windows

Similar Flings

Mar 22, 2021
fling logo of Workspace ONE App Analyzer for macOS

Workspace ONE App Analyzer for macOS

version 1.2.1

The Workspace ONE macOS App Analyzer will determine any Privacy Permissions, Kernel Extensions, or System Extensions needed by an installed macOS application, and can be used to automatically create profiles in Workspace ONE UEM to approve list those same settings when deploying apps to managed devices.To connect to your
Workspace ONE UEM environment:

Mar 03, 2021
fling logo of Workspace ONE Mobileconfig Importer

Workspace ONE Mobileconfig Importer

version 1.1

The Workspace ONE mobileconfig Importer gives you the ability to import existing mobileconfig files directly into a Workspace ONE UEM environment as a Custom Settings profile, import app preference plist files in order to created managed preference profiles, and to create new Custom Settings profiles from scratch.

Oct 08, 2021
fling logo of Workspace ONE Policy Analyzer for Windows

Workspace ONE Policy Analyzer for Windows

version 1.0

Workspace ONE Policy Analyzer for Windows aids in the management of profiles and baselines for Windows 10 devices. Policy Analyzer uses the Workspace ONE UEM API to review the status of profiles and baselines assigned to a specified Windows 10 device.