Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Permalink
public
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time
title description keywords author ms.author ms.reviewer ms.date ms.prod ms.topic ms.sitesec ms.localizationpriority audience manager appliesto
Deployment Guide – Cloud connected HoloLens 2 deployment at scale with Remote Assist - Configure
Learn how to set up configurations to enroll HoloLens devices over a Cloud Connected network at scale with Remote Assist.
HoloLens, management, cloud connected, Remote Assist, AAD, Azure AD, MDM, Mobile Device Management
evmill
millerevan
aboeger
12/04/2020
hololens
article
library
HoloLens
yannisle
HoloLens 2

Configure - Cloud connected Guide

In this section of the guide, we'll go over how to set up Auto Enrollment for your tenant, and how to apply licenses for both Intune and Remote Assist.

Azure Users and Groups

Azure, and Intune by that extension, uses users and groups to help assign configurations and licenses. For the sake of validating this deployment flow and being able to make a Remote Assist call from one user to another you'll need two user accounts.

We can make a single user group for the purpose of assigning licenses. We can join both users to the same group and apply a license for Intune and Remote Assist to that group.

If you don't already have access to two Azure AD accounts in a user group you can use; here are the quick start guides for:

Auto Enrollment on HoloLens 2

In order to have a smooth and seamless experience, setting up Azure Active Directory Join (AADJ) and Auto Enrollment to Intune for HoloLens 2 devices is the way to go. This will allow users to input their organization log-in credentials during OOBE and automatically register with Azure AD and enroll the device into MDM.

By using Microsoft Endpoint Manager, we can select services and navigate a few pages until we can select Get a Premium trial. You may notice there is Azure Active Directory Premium 1 and 2, for Automatic Enrollment P1 is sufficient. We can select Intune and select the user scope for automatic enrollment, and select the group that was previously created.

For full details and steps read the guide on how to enable auto enrollment for Intune.

Application Licenses

An application license allows a user to either install company purchased Apps or upgrade from a free trial to the full version of an app. Application licenses can be applied to either users, user groups, or device groups. You'll need Remote Assist licenses for users in your organization to use Remote Assist. For the purpose of this guide we'll assign Remote Assist licenses to the user group we created above in Azure Users and Groups.

The requirements for licenses can be different depending on if the user will be making the Remote Assist call from a device or will be a remote collaborator from Microsoft Teams. By default the Remote Assist and Teams check boxes are both marked. For the purposes of this guide, we suggest leaving the default boxes checked.

  1. Learn more about the different Licensing and product requirements per role. There are a few different types of Remote Assist licenses so be sure to get the correct ones for your needs.
  2. You'll need to acquire the license.
  3. Apply your licenses to the group.

Next step

[!div class="nextstepaction"] Cloud connected deployment - Deploy