top of page
  • Writer's pictureMark Cullens

A guide to preparing a fleet of Meta Quest Headsets

Introduction to the challenge

Setting up a Meta Quest headset isn’t a particularly challenging task and is actually quite a slick, well-organised process.  But here's the catch.  Setting up 20 or x0 headsets and the process isn’t quite as pleasant.  This article covers the initial Meta set-up stage and goes onto explore using mobile device management software to provision the devices.

1.       Setting up device accounts

2.       Switching on the headsets and adding to the wifi

3.       Creating a Meta account & device pairing

4.       Developer Accounts Invites

5.       Logging into the device developer account

6.       Setting Two Factor Authentication

7.       Completing the device set-up

8.       Downloading content from the Meta Store (optional)

9.       Mobile Device Management

a.       Option 1- Headset enrolment and push content over WiFi.

b.       Option 2- Create an installation package and push it to the headsets over USB

10.  Device Enrolment


Meta Quest 2 VR headset
Meta Quest Headset

There is nothing particularly technical or challenging, but it is a tedious process.  I have captured the best way that I’ve found, but if others have suggestions, I would love to see them in the comments, and I will be happy to refresh the article.  This article assumes that you have made the decision NOT to purchase the paid-for Meta Quest fleet management software.  Aside from the cost, why would that be? Well, maybe you have a mix of devices and want to manage them in one place with an r MDM like ManageXR or ArborXR. 


Step 1- Device Accounts

Each headset requires a unique email address.  Let's assume we are configuring a batch of 20 headsets.  If you are using Google Mail, I would set up one email for the batch and 20 email aliases.  If you are using an enterprise mailbox, create the 20 emails, for example, XXMeta01@yourdomain.com, etc., but have them forward all to a single email address.  This approach will mean that you only need to be logged into the single master email to receive the security codes from Meta. 


If you wish to cast the headsets over USB or install MDM you will definitely need to put the devices into developer mode.  You will need to create a new developer account for the organisation by following the steps on the first login.  I recommend keeping the developer account on screen in a separate browser. 

 

Step 2- Switching on the devices and adding to the WIFI

If you can, have 2 or 3 mobile phones or tablets with the Meta app downloaded. Note that you can start the process of registration using the new emails on a desktop, but it can’t be completed, so I’ve found the best way is to do the whole thing on mobile. 


Switch on the first 5 or 6 six headsets and wait for the intro video to play.  Otherwise, I can use some electrical tape over the light sensor or watch it x 20.  When asked, add the device to the WiFi, and it will run updates.  The headset will likely reboot itself and update the controllers.  Lots of buzzing and beeping.  I find batching them through the process is the easiest to keep track of progress.  At this stage, I normally label the headsets and controllers with a label printer.  I lay out the headsets in sequence from left to right and the mobile device in front of the headset

 

Step 3- Creating the Meta Account and Device Pairing

Each headset will now be looking to pair with a mobile device and will show a code to enter into the mobile device.  They should pair.  If not, force close the app and re-open ensuring you are not logged into an existing profile.   


On each of the mobile devices, tap login and use the appropriate device-numbered email that we created in Step 1.  Meta will recognise that there isn’t an account for this email address and will offer to create a new Meta account.  Typically, my clients want to keep data anonymous, so I use a generic name and the same birthday for each profile.  I use the same password for each device but that’s a decision for you.   This is where the benefit of alias or account forwarding comes in.  The emails with confirmation codes will start coming from Meta for each device.  Having one email to keep refreshing is the best way I’ve found. 


Once you add your name to the Meta app, it will offer up suggested Meta profile names that are available.  Pick one, but take note now.  I typically keep all this information in a Google sheet.  Go through the various steps induction steps, accepting or not to create an avatar or share data () on the app, and skip the credit card registration.  Let the device take you through the familiarisation videos, clicking the Oculus button when prompted, etc. 


Screen Grab of the Meta App
Meta Quest App


Step 4.  Developer Accounts Invites- Create a Developer Account | Oculus

Go to the browser that is logged into the developer account, and on the left-hand side, you will see “invite member”.  Cut and paste the new Meta account(s) and select the account role.  By default, there’s only Admin, but you can create different roles. 

 

Step 5. Logging the device email into the Developer account

Back in the master email, you will see an invite to join a developer account.   This is the tricky bit.  I find using different browsers (not tabs) helps.  It stops cookies from keeping you logged as you want to be logged into two different profiles at the same time.  So for example, if I’m logged into the main developer account on Safari, then use Chrome to login into the device developer account. 

 

Step 6.  Setting Two-factor Authentication

Login to the developer account on the desktop (and using the tip above).  On first login, you will be asked to set up two-factor authentication.  Our aim is to get the devices into developer mode, so you HAVE to use the phone method.  You can also use the authentication app to log into the developer account but to access (and stay in) developer mode; you must use the phone SMS method.  If you add it but later remove the phone number, it will remove the headset from developer mode.    


You will access the invite once you have set up the two-factor authentication in the bottom left corner.  Click and accept the invite to your installation. 

 


A screen grab from the Meta Developer App
Set up two factor authentication with a mobile phone

Step 7.  Completing the Headset

Returning to the Meta app you can will see that the headset is paired.  You may need to wake the device if it’s been sitting.  In the app, tap on the headset that is connected, and at the bottom of the page, tap “Device Settings”.  A list will appear. Click “Developer” and toggle the switch to turn on developer mode.  If you haven’t managed to follow the steps above, tapping in developer won’t do anything, and the toggle switch won’t appear.    

 

Step 8. Downloading Content from the Meta  Store (Optional)

You can use the app to select any AppStore content that you want on the headset from the library button.  For example,  First Steps or First Contact are a nice intro to VR for user orientation. 


But note, that you will have to go back into the headset to click install.  Once at this stage I typically pause and get all of my headsets to this stage. 


Tip: I like to place the headset upside down on the nose and volume buttons facing up so I can see visually how those headsets are at this stage. 

 

Step 9. Mobile Device Management

If you plan to use an MDM platform, there will be choices and nuances to the process.  You can access their website and help centres, but broadly speaking you have two options for enrolling devices. 


Option 1- Headset enrolment and push content over WiFi.

One option is to execute lots of single headset enrolments.  You can later have the device join a group to push and manage content.   This is straightforward forward, but as you add the devices to the group, the MDM will push the configuration from the cloud over WiF and, as a result, will use a good amount of data. 


Option 2- Create an installation package and push it to the headsets over USB.

Creating an installation package is easy.   You create a group within the MDM platform and upload any APKs or add the file paths for your AppStore packages (known as unmanaged apps) and add Wi-Fi configurations.  You might need to use SideQuest to find the file paths.  Depending on your MDM provider and your package features, you can customise menus and environments with your own 360 upload logos etc.  Once you have the group configured, select “Create installation package”, and the MDM will do their magic.  You will receive an email when the package is ready.  Download it.


Device Enrolment

Once you have selected your preferred approach, launch the MDM installer app on your desktop and plug in your headset(s) over USB.  You can use a USB hub to run this as a batch.  If you have been successful with developer mode, you will see the headsets appear with their serial numbers, etc., but they will be in red telling you to authorise access in the headset. 

Peek into the headset and click allow access over USB, and you will see the headset become available on the desktop.  If you are batching, this is a good time to rename the headset for the MDM to your naming convention XXMeta01@yourdomain , etc. 


The installer app will give you the option to “enrol a headset” or “enrol to a group” or “use a configuration package”.  If you choose to use a package, it will ask you to point it to the package files that you have downloaded. Click enrol and feel like a VR King!

 

Final thoughts

I recommend taking 2-3 headsets at a time through steps 1 to 8 at a time.  I have only given the key points: the headset will be on and off so many times, so if you have more than this on the go, it’s easy to forget the stage you are at.


Mid-workflow, it's important that you log out of the Meta account when you have finished setting up the two-factor authentication and accepted the invite.  It will ask you to confirm logout on the page.  If you just close the tab or window, there’s a good chance you will stay logged in and end up totally confused because your profile name isn’t front and centre. Also, you are going to 20 similar profile names. 


Keeping track of profile names, email addresses and password is vital.  I recommend a Google sheet. 


Good luck!


Our services

We offer complete device configuration and deployment services if you would like support in procuring and configuring devices.  We can supply and enrol your devices including using mobile device management to provision the devices and ongoing management of OS and app updates.   We offer full on-site training for both technical and non-technical staff.

Feel free to drop us a line for a quick chat. 

 

 

 

 

 

199 views0 comments

Comments


bottom of page