deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 11:53:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

updates

Browse Source
This commit is contained in:
Jeanie Decker
2018-03-09 08:57:35 -08:00
parent 247cf1fec2
commit 3d8bd9ff5f
3 changed files with 35 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
devices/hololens/hololens-kiosk.md
View File

@ -22,6 +22,8 @@ Single-app kiosk mode starts the specified app when the user signs in, and restr
>[!WARNING] >[!WARNING]
>The assigned access feature which enables kiosk mode is intended for corporate-owned fixed-purpose devices. When the multi-app assigned access configuration is applied on the device, certain policies are enforced system-wide, and will impact other users on the device. Deleting the multi-app configuration will remove the assigned access lockdown profiles associated with the users, but it cannot revert all [the enforced policies](https://docs.microsoft.com/windows/configuration/lock-down-windows-10-to-specific-apps#policies-set-by-multi-app-kiosk-configuration). A factory reset is needed to clear all the policies enforced via assigned access. >The assigned access feature which enables kiosk mode is intended for corporate-owned fixed-purpose devices. When the multi-app assigned access configuration is applied on the device, certain policies are enforced system-wide, and will impact other users on the device. Deleting the multi-app configuration will remove the assigned access lockdown profiles associated with the users, but it cannot revert all [the enforced policies](https://docs.microsoft.com/windows/configuration/lock-down-windows-10-to-specific-apps#policies-set-by-multi-app-kiosk-configuration). A factory reset is needed to clear all the policies enforced via assigned access.
>
>Be aware that voice commands are enabled, even if the Cortana app is not selected as a kiosk app.
For HoloLens devices running Windows 10, version 1803, there are three methods that you can use to configure the device as a kiosk: For HoloLens devices running Windows 10, version 1803, there are three methods that you can use to configure the device as a kiosk:
- You can [use Microsoft Intune](#intune-kiosk), for HoloLens devices managed by Intune, to configure single-app and multi-app kiosks. - You can [use Microsoft Intune](#intune-kiosk), for HoloLens devices managed by Intune, to configure single-app and multi-app kiosks.
@ -212,6 +214,13 @@ Follow [the instructions for creating a kiosk configuration XML file for desktop
5. Select **Enable Kiosk Mode**, choose an app to run when the device starts, and click **Save**. 5. Select **Enable Kiosk Mode**, choose an app to run when the device starts, and click **Save**.
## Kiosk app recommendations
- You cannot select Microsoft Edge, Microsoft Store, or the Shell app as a kiosk app.
- We recommend that you do **not** select the Settings app and the File Explorer app as a kiosk app.
- You can select Cortana as a kiosk app.
- To enable photo or video capture, the HoloCamera app must be enabled as a kiosk app.
## More information ## More information
>[!VIDEO https://www.microsoft.com/videoplayer/embed/ce9992ab-9fea-465d-b773-ee960b990c4a?autoplay=false] >[!VIDEO https://www.microsoft.com/videoplayer/embed/ce9992ab-9fea-465d-b773-ee960b990c4a?autoplay=false]

48
devices/hololens/hololens-updates.md
View File

@ -14,39 +14,39 @@ ms.date: 04/01/2018
Windows 10, version 1803, is the first feature update to Windows Holographic for Business since its release in Windows 10, version 1607. As with desktop devices, administrators can manage updates to the HoloLens operating system using [Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb). Windows 10, version 1803, is the first feature update to Windows Holographic for Business since its release in Windows 10, version 1607. As with desktop devices, administrators can manage updates to the HoloLens operating system using [Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb).
## Use MDM policies to manage updates >[!NOTE]
>HoloLens devices must be [upgraded to Windows Holographic for Business](hololens-upgrade-enterprise.md) to manage updates.
mobile device management (MDM)
## Use Windows Server Update Service to update HoloLens Mobile device management (MDM) providers use the [Policy Configuration Service Provider (CSP)](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider) to enable update management.
Windows Server Update Service (WSUS) The Update policies supported for HoloLens are:
## sandbox - [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate)
- [Update/AllowMUUpdateService](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowmuupdateservice)
- [Update/AllowUpdateService](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowupdateservice)
- [Update/RequireDeferUpgrade](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-requiredeferupgrade)
- [Update/RequireUpdateApproval](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-requireupdateapproval)
- [Update/UpdateServiceUrl](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updateserviceurl)
For HoloLens, customers would configure update deferral settings in a general config policy and create a custom profile to point them to the WSUS server. If you use Microsoft Intune to manage HoloLens, you can configure the following Update policies as settings for [update rings](https://docs.microsoft.com/intune/windows-update-for-business-configure):
WSUS is not directly supported by Intune since Intune is pushing WUFB. You would need to go to the Custom OMA-DM URI route to set those unsupported policies as @Alvin Chardon descirbes below. - [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) is set in **Software Updates** > **Windows 10 Update Rings** > **Automatic update behavior**.
- - [Update/AllowMUUpdateService](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowmuupdateservice) is set in **Software Updates** > **Windows 10 Update Rings** > **Microsoft product updates**.
- [Update/RequireDeferUpgrade](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-requiredeferupgrade) is set in **Software Updates** > **Windows 10 Update Rings** > **Servicing channel**.
Below is policies HL supports and the mechanism you need to use in Intune. Typically, devices access Windows Update directly for updates. You can use the following update policies to configure devices to get updates from Windows Server Update Service (WSUS) instead:
• Update/AllowAutoUpdate – directly supported in UI. Software Updates > Windows 10 Update Rings > Automatic update behavior
• Update/AllowUpdateService - Custom OMA-DM URI
• Update/RequireDeferUpgrade -- directly supported in UI. Software Updates > Windows 10 Update Rings > Servicing channel
• Update/RequireUpdateApproval -- Custom OMA-DM URI
• Update/UpdateServiceUrl Custom OMA-DM URI
MDM can defer the update directly from Windows Update by setting Servicing Channel to semi-annual (not targeted). - [Update/AllowUpdateService](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowupdateservice)
- [Update/RequireUpdateApproval](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-requireupdateapproval)
- [Update/UpdateServiceUrl](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updateserviceurl)
Here is the general Intune documentation for Microsoft Update for Business: In Microsoft Intune, use [a custom profile](https://docs.microsoft.com/intune/custom-settings-windows-holographic) to configure devices to get updates from WSUS.
https://docs.microsoft.com/en-us/intune/windows-update-for-business-configure
Here is the Holographic-specific section of that article naming what features are supported:
https://docs.microsoft.com/en-us/intune/windows-update-for-business-configure#windows-holographic-for-business-support
For the settings Intune doesn’t offer UI, including WSUS, we recommended setting them through Custom OMA-DM Uris:
https://docs.microsoft.com/en-us/intune/custom-settings-windows-holographic
link dump:
https://docs.microsoft.com/en-us/intune/windows-update-for-business-configure
https://docs.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wufb ## Related topics
https://docs.microsoft.com/en-us/intune/custom-settings-windows-holographic
- [Manage software updates in Microsoft Intune](https://docs.microsoft.com/intune/windows-update-for-business-configure)

2
devices/hololens/hololens-whats-new.md
View File

@ -24,6 +24,8 @@ Windows 10, version 1803, is the first feature update to Windows Holographic for
- Previously, after you signed in to the device with an Azure Active Directory (AD) account, you then had to **Add work access** in **Settings** to get access to corporate resources. Now, you sign in with an Azure AD account and enrollment happens automatically. - Previously, after you signed in to the device with an Azure Active Directory (AD) account, you then had to **Add work access** in **Settings** to get access to corporate resources. Now, you sign in with an Azure AD account and enrollment happens automatically.
- Can change network before sign-in
- multi-user (AAD) - multi-user (AAD)
- multi transfer protocol (MTP) support - multi transfer protocol (MTP) support
- file explorer - file explorer