Deploy HoloLens in a commercial environment
You can deploy and configure HoloLens at scale in a commercial setting. This article provides instructions for deploying HoloLens devices in a commercial environment. This guide assumes basic familiarity with HoloLens. Follow the get started guide to set up HoloLens for the first time.
This document also assumes that the HoloLens has been evaluated by security teams as safe to use on the corporate network.
Overview of Deployment Steps
- Determine what features you need
- Determine what licenses you need
- Configure your network for HoloLens.
- This section includes bandwidth requirements, URL, and ports that need to be allowed on your firewall; Azure AD guidance; Mobile Device Management (MDM) Guidance; app deployment/management guidance; and certificate guidance.
- (Optional) Configure HoloLens using a provisioning package
- Enroll Device
- Set up ring based updates for HoloLens
- Enable Bitlocker device encryption for HoloLens
Step 1. Determine what you need
Before deploying the HoloLens in your environment, it is important to first determine what features, apps, and type of identities are needed. It is also important to ensure that your security team has approved of the use of the HoloLens on the company's network. Please see HoloLens2 security for additional security information.
Type of Identity
Determine the type of identity that will be used to sign into the device.
- Local Accounts: This account is local to the device (like a local admin account on a windows PC). This will allow only 1 user to log into the device.
- MSA: This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device.
- Azure Active Directory (Azure AD) accounts: This is an account created in Azure AD. This grants your corporation the ability to manage the HoloLens device. This will allow multiple users to log into the HoloLens 1st Gen Commercial Suite/the HoloLens 2 device.
For more detailed information about identity types, please visit our HoloLens Identity article.
Type of Features
Your feature requirements will determine which HoloLens you need. One popular feature that we see deployed in customer environments frequently is Kiosk Mode. A list of HoloLens key features, and the editions of HoloLens that support them, can be found here.
What is Kiosk Mode?
Kiosk mode is a way to restrict the apps that a user has access to. This means that users will only be allowed to access certain apps.
What Kiosk Mode do I require?
There are two types of Kiosk Modes: Single app and multi-app. Single app kiosk mode allows user to only access one app while multi-app kiosk mode allows users to access multiple, specified apps. To determine which kiosk mode is right for your corporation, the following two questions need to be answered:
- Do different users require different experiences/restrictions? Consider the following example: User A is a field service engineer who only needs access to Remote Assist. User B is a trainee who only needs access to Guides.
- If yes, you will require the following:
- Azure AD Accounts as the method of signing into the device.
- Multi-app kiosk mode.
- If no, continue to question two
- If yes, you will require the following:
- Do you require a multi-app experience?
- If yes, Multi-app kiosk is mode is needed
- If your answer to question 1 and 2 are both no, single-app kiosk mode can be used
How to Configure Kiosk Mode:
There are two main ways (provisioning packages and MDM) to deploy kiosk mode for HoloLens. These options will be discussed later in the document; however, you can use the links above to jump to the respective sections in this doc.
Apps and App Specific Scenarios
The majority of the steps found in this document will also apply to the following apps:
|App||App Specific Scenarios|
|Remote Assist||Cross Tenant Communication|
|Custom Apps||Coming Soon|
Determine your enrollment method
- Bulk enrollment with a security token in a provisioning package.
Pros: this is the most automated approach
Cons: takes initial server-side setup
- Auto-enroll on user sign in.
Pros: easiest approach
Cons: users will need to complete set up after the provisioning package has been applied
- not recommended - Manually enroll post-setup.
Pros: possible to enroll after set up
Cons: most manual approach and devices aren't centrally manageable until they're manually enrolled.
More information can be found here
Determine if you need to create a provisioning package
There are two methods to configure a HoloLens device (Provisioning packages and MDMs). We suggest using your MDM to configure you HoloLens device. However, there are some scenarios where using a provisioning package is the better choice:
- You want to configure the HoloLens to skip the Out of Box Experience (OOBE)
- You are having trouble deploying certificate in a complex network. The majority of the time you can deploy certificates using MDM (even in complex environments). However, some scenarios require certificates to be deployed through the provisioning package.
Some of the HoloLens configurations you can apply in a provisioning package:
- Apply certificates to the device
- Set up a Wi-Fi connection
- Pre-configure out of box questions like language and locale
- (HoloLens 2) bulk enroll in mobile device management
- (HoloLens v1) Apply key to enable Windows Holographic for Business
If you decide to use provisioning packages, follow this guide.
Get support through the Microsoft support site.