From eda883b7c0179d23f75b3f6e8113209f9cabdd4b Mon Sep 17 00:00:00 2001 From: Payge Winfield Date: Tue, 25 Feb 2020 11:21:19 -0800 Subject: [PATCH 1/5] Added FAQ security link to FAQ doc. Also added "Back to list" link to FAQ doc --- devices/hololens/hololens-FAQ.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/devices/hololens/hololens-FAQ.md b/devices/hololens/hololens-FAQ.md index 3a194dc014..03bed1bfc3 100644 --- a/devices/hololens/hololens-FAQ.md +++ b/devices/hololens/hololens-FAQ.md @@ -44,6 +44,7 @@ This FAQ addresses the following questions and issues: - [I can't connect to Wi-Fi](#i-cant-connect-to-wi-fi) - [My HoloLens isn't running well, is unresponsive, or won't start](#my-hololens-isnt-running-well-is-unresponsive-or-wont-start) - [HoloLens Management Questions](#hololens-management-questions) +- [HoloLens Security Questions](#hololens-security-questions) - [How do I delete all spaces?](#how-do-i-delete-all-spaces) - [I cannot find or use the keyboard to type in the HoloLens 2 Emulator](#i-cannot-find-or-use-the-keyboard-to-type-in-the-hololens-2-emulator) - [I can't log in to a HoloLens because it was previously set up for someone else](#i-cant-log-in-to-a-hololens-because-it-was-previously-set-up-for-someone-else) @@ -230,6 +231,14 @@ If your device was previously set up for someone else, either a client or former 1. **What logging capabilities are available on HL1 and HL2?** 1. Logging is limited to traces captured in developer/troubleshooting scenarios or telemetry sent to Microsoft servers. +[Back to list](#list) + +## HoloLens Security Questions + +Frequently asked security questions can be found [here](hololens-faq-security.md). + +[Back to list](#list) + ## How do I delete all spaces? *Coming soon* @@ -241,4 +250,3 @@ If your device was previously set up for someone else, either a client or former *Coming soon* [Back to list](#list) - From ec729d063856a6935252d4e065747504f92bda07 Mon Sep 17 00:00:00 2001 From: Payge Winfield Date: Tue, 25 Feb 2020 11:32:08 -0800 Subject: [PATCH 2/5] added additional instructional note to the infastructure doc --- devices/hololens/hololens-commercial-infrastructure.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/devices/hololens/hololens-commercial-infrastructure.md b/devices/hololens/hololens-commercial-infrastructure.md index 757084bb86..476398d791 100644 --- a/devices/hololens/hololens-commercial-infrastructure.md +++ b/devices/hololens/hololens-commercial-infrastructure.md @@ -163,6 +163,8 @@ Directions for upgrading to the commercial suite can be found [here](https://doc 1. Check your app settings 1. Log into your Microsoft Store Business account 1. **Manage > Products and Services > Apps and Software > Select the app you want to sync > Private Store Availability > Select “Everyone” or “Specific Groups”** + >[!NOTE] + >If you don't see the app you want, you will have to "get" the app by searching the store for your app. **Click the "Search" bar in the upper right-hand corner > type in the name of the app > click on the app > select "Get"**. 1. If you do not see your apps in **Intune > Client Apps > Apps** , you may have to [sync your apps](https://docs.microsoft.com/intune/apps/windows-store-for-business#synchronize-apps) again. 1. [Create a device profile for Kiosk mode](https://docs.microsoft.com/intune/configuration/kiosk-settings#create-the-profile) From 18c543b90f497387a57a8a83a76c3cd8515cabcc Mon Sep 17 00:00:00 2001 From: Payge Winfield Date: Tue, 25 Feb 2020 13:27:08 -0800 Subject: [PATCH 3/5] Rearranged order of steps in --- devices/hololens/hololens-requirements.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index 139648349b..cfc6da7a4d 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -33,6 +33,14 @@ This document also assumes that the HoloLens has been evaluated by security team 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 [Frequently ask security questions](hololens-faq-security.md) for additional security information. +### Type of identity + +Determine the type of identity that will be used to sign into the device. + +1. **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. +2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device. +3. **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. + ### 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](hololens-commercial-features.md). @@ -66,18 +74,10 @@ The majority of the steps found in this document will also apply to the followin 2. Guides 3. Customer Apps -### Type of identity - -Determine the type of identity that will be used to sign into the device. - -1. **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. -2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device. -3. **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. - ### Determine your enrollment method 1. Bulk enrollment with a security token in a provisioning package. - Pros: this is the most automated approach + Pros: this is the most automated approach k Cons: takes initial server-side setup 1. Auto-enroll on user sign in. Pros: easiest approach From 944a9af082de3b4b537f23350dbe7da062a39b59 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Tue, 25 Feb 2020 13:55:56 -0800 Subject: [PATCH 4/5] Deleted "k", hoping for a line break --- devices/hololens/hololens-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index cfc6da7a4d..b536f6426d 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -77,7 +77,7 @@ The majority of the steps found in this document will also apply to the followin ### Determine your enrollment method 1. Bulk enrollment with a security token in a provisioning package. - Pros: this is the most automated approach k + Pros: this is the most automated approach Cons: takes initial server-side setup 1. Auto-enroll on user sign in. Pros: easiest approach From f0128f599efe23a433e89d0b58653ae8109cd953 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Tue, 25 Feb 2020 14:19:07 -0800 Subject: [PATCH 5/5] Trying to fix a line break MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I don't know why the second and third item under "Determine your enrollment method" doesn't seem to need a line break to be specified, but the first item apparently needs one—added now. --- devices/hololens/hololens-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index b536f6426d..6c370939da 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -77,7 +77,7 @@ The majority of the steps found in this document will also apply to the followin ### Determine your enrollment method 1. Bulk enrollment with a security token in a provisioning package. - Pros: this is the most automated approach + Pros: this is the most automated approach\ Cons: takes initial server-side setup 1. Auto-enroll on user sign in. Pros: easiest approach