From e5e0e83b89d02681d4315027d890f7321d38a040 Mon Sep 17 00:00:00 2001 From: Evan Miller Date: Tue, 24 Aug 2021 10:46:27 -0700 Subject: [PATCH 1/2] place steps in policy --- .../mdm/policy-csp-mixedreality.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-mixedreality.md b/windows/client-management/mdm/policy-csp-mixedreality.md index cdf909411f..7f7e8ae961 100644 --- a/windows/client-management/mdm/policy-csp-mixedreality.md +++ b/windows/client-management/mdm/policy-csp-mixedreality.md @@ -40,20 +40,6 @@ manager: dansimp -Steps to use this policy correctly: - -1. Create a device configuration profile for kiosk targeting Azure AD groups and assign it to HoloLens device(s). -1. Create a custom OMA URI based device configuration that sets this policy value to desired number of days (> 0) and assign it to HoloLens device(s). - 1. The URI value should be entered in OMA-URI text box as ./Vendor/MSFT/Policy/Config/MixedReality/AADGroupMembershipCacheValidityInDays - 1. The value can be between min / max allowed. -1. Enroll HoloLens devices and verify both configurations get applied to the device. -1. Let Azure AD user 1 sign-in when internet is available. Once the user signs-in and Azure AD group membership is confirmed successfully, cache will be created. -1. Now Azure AD user 1 can take HoloLens offline and use it for kiosk mode as long as policy value allows for X number of days. -1. Steps 4 and 5 can be repeated for any other Azure AD user N. The key point here is that any Azure AD user must sign-in to device using Internet at least once. Then we can determine that they are member of Azure AD group to which Kiosk configuration is targeted. - -> [!NOTE] -> Until step 4 is performed for a Azure AD user will experience failure behavior mentioned similar to “disconnected” environments. -
@@ -79,6 +65,20 @@ Steps to use this policy correctly: +Steps to use this policy correctly: + +1. Create a device configuration profile for kiosk targeting Azure AD groups and assign it to HoloLens device(s). +1. Create a custom OMA URI based device configuration that sets this policy value to desired number of days (> 0) and assign it to HoloLens device(s). + 1. The URI value should be entered in OMA-URI text box as ./Vendor/MSFT/Policy/Config/MixedReality/AADGroupMembershipCacheValidityInDays + 1. The value can be between min / max allowed. +1. Enroll HoloLens devices and verify both configurations get applied to the device. +1. Let Azure AD user 1 sign-in when internet is available. Once the user signs-in and Azure AD group membership is confirmed successfully, cache will be created. +1. Now Azure AD user 1 can take HoloLens offline and use it for kiosk mode as long as policy value allows for X number of days. +1. Steps 4 and 5 can be repeated for any other Azure AD user N. The key point here is that any Azure AD user must sign-in to device using Internet at least once. Then we can determine that they are member of Azure AD group to which Kiosk configuration is targeted. + +> [!NOTE] +> Until step 4 is performed for a Azure AD user will experience failure behavior mentioned similar to “disconnected” environments. +
From 5c4750b396c242154e643b8204b6bc02b6752e8d Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 24 Aug 2021 12:56:06 -0700 Subject: [PATCH 2/2] fix links --- windows/deployment/TOC.yml | 2 ++ windows/deployment/index.yml | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index d61509c788..967f57f92e 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -271,6 +271,8 @@ href: update/how-windows-update-works.md - name: Windows 10 upgrade paths href: upgrade/windows-10-upgrade-paths.md + - name: Windows 10 edition upgrade + href: upgrade/windows-10-edition-upgrades.md - name: Deploy Windows 10 with Microsoft 365 href: deploy-m365.md - name: Understand the Unified Update Platform diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index d938c4922b..1bb703d0bf 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -67,7 +67,7 @@ landingContent: - text: What's new in Windows deployment url: deploy-whats-new.md - text: Windows 11 overview - url: /windows/whats-new/windows-11.md + url: /windows/whats-new/windows-11 - text: Windows client deployment scenarios url: windows-10-deployment-scenarios.md - text: Basics of Windows updates, channels, and tools