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 ms.date manager ms.prod ms.sitesec author ms.author ms.reviewer ms.topic audience ms.localizationpriority appliesto
Common Scenarios – Near Offline or Restricted for HoloLens 2
Learn how to set up a secure, near offline, or restricted deployment and app deployment scenario with provisioning for HoloLens devices.
HoloLens, management, offline, offline secure
4/04/2022
sean.kerawala
hololens
library
tmilligan
tmilligan
mata
article
ITPro
HoloLens 2

Common Scenarios – Near Offline or isolated environments for HoloLens 2

Overview

This guide provides guidance for deploying HoloLens 2 in areas where networking is restricted. This could either be for secure environments or for areas where networking cannot be assured such as power plants, ships, or other areas.

This scenario is designed to deliver the best user and administrator experience. This scenario allows for the use of Azure AD, Intune, Windows updates and multiple user support with IRIS sign-in, whilst meeting the needs of organizations who have additional security or networking challenges.

[!NOTE] This scenario describes one possible approach. We expect each organization deploying in this scenario will have unique requirements, which can be mapped into this solution as required.

Offline Secure scenario.

Prepare

The cloud functionality of this guide matches the requirements for the Cloud Connected Scenario. The following decisions will need to be made with reference to both your infrastructure and security teams.

Determine level of cloud connectivity required

This guide assumes the following services are being used:

[!NOTE] If these services are already used within your organization, then your security team may be able to reuse any security assessments already completed.

Determine level of network connection during usage

Consider whether or not devices will be connected to a network during usage:

  • If devices are able to be connected, then more services can be used such as D365 Remote Assist or D365 Guides.
  • LOB applications can be developed to use local data storage either on device, or on a server contained within the organizations network.

Governance processes for User Enrollment and Updates

  • Users will need to make their initial sign into the device when connected to the network. After setting up their PIN and IRIS, they can sign in offline.
  • Devices should be reconnected at a regular schedule (once a month) to enable any MDM policy changes and Windows updates to be completed.

Network Configurations

Detailed network configurations are out of the scope of this article, and will vary depending on unique configuration needs.

  • Firewalls should support URL based filtering, as IP filtering may be difficult to manage.
  • Proxy Servers, with or without SSL inspection can be utilized, either in transparent mode or configured on the device.
  • Devices will need to be able to access the relevant endpoints listed in the tables below.

[!NOTE] It is likely that during initial configuration, a network engineer will need to validate the endpoints are accessible.

[!IMPORTANT] Read more about how to deploy your app with the Deployment Guide – Corporate connected HoloLens 2 with Dynamics 365 Guides - Prepare | Microsoft Docs.

Configure

The key configuration elements relate to the network restrictions. Following our Connected HoloLens 2 Deployment Guide – Cloud connected HoloLens 2 deployment at scale with Remote Assist - Configure | Microsoft Docs will allow for most cloud configurations to be completed.

The key endpoints to enable access on your network are:

Group Purpose
Near Offline Setup Initial OOBE
Azure AD MFA MFA Requests (Optional if not using Azure MFA)
Intune and MDM Configurations Intune Enrollment (Optional if not using Intune)
Certificates Check Microsoft Certificate Status
Device Metadata Device Information
Diagnostic Data Sending Telemetry to Microsoft (Strongly Recommended)
Licensing Validate software licensing
Network Connection Status Indicator Used to confirm whether the device has network access
Windows Defender Used to update Windows Defender Information
Windows Update Used for Windows Update
Settings Used in the Settings Application

[!TIP] These are the key endpoints to utilize Autopilot, complete OOBE and allow an AAD User to sign in with Windows Hello for Business. Your organization may require other endpoints to allow for the desired functionality.

Deploy and maintain

Deployment and Maintenance steps are identical to the Cloud connected guide. We've included basic suggestions here.

When the device is reconnected to the corporate network, we suggest you perform manual updates at-least once a month (ie. the 2nd Wednesday of the month) to ensure your device(s) are up-to-date and secure.

Manually update store apps

To update an app you installed from the Microsoft Store, you can update the app from the Microsoft Store app. For apps installed for the Microsoft Store for Business, you can also update those apps from the Microsoft Store for Business.

See how at Manually update apps.

Manually update OS

Check for updates anytime in settings. To see available updates:

  1. Open the Settings app.
  2. Navigate to Update & Security > Windows Update.
  3. Select Check for updates.

Read more at Update hololens.

Manually sync with MDM

Based on your specific needs, ensure that you perform updates and sync with MDM.

Read more at Using MDM to manage HoloLens devices.

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