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

Squashed commit of the following:

Browse Source 
commit dca2a868af8d1c1baedcc0acecff617a91fe481a
Merge: d6ec703 4a71f17
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Nov 15 07:05:40 2016 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit d6ec7035c3ae80e0f5c24851017e3d1882988fb8
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Nov 14 13:45:52 2016 -0800

    format note

commit da0405941ddbedbed827761ece9c7a7c0983116c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Nov 14 13:31:36 2016 -0800

    fix index

commit 200976c83059378e952a678c91cbce8186d020a9
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Nov 14 12:25:00 2016 -0800

    fix note

commit 4260d50e1a1d962e96a1e5597273ac588fce1959
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Nov 14 12:04:01 2016 -0800

    password change

commit 57cad860cf903a642767c18faaab71f5e0d2d094
Merge: 1b3b23c 01ec7e8
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Nov 14 11:57:35 2016 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 1b3b23c8339569bf51336467602a9a65af2a5701
Merge: feee3be ea87bea
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Nov 7 07:21:53 2016 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit feee3be7e77e33ba8c28df3bc232c1aa3e7b61d5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Nov 7 07:21:20 2016 -0800

    fix dev mode note

commit 1eff5227eddf3f191b99fe6c01b322f18d73bc39
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Nov 4 17:33:51 2016 -0700

    Xerxes feedback

commit 93bd803abe9f37f1d5ec1ed206ee6b4a5f47748e
Merge: 70bf588 0945bb5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Nov 4 17:26:13 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 70bf58825b7a4b1d33aa4b9ac0991193854cb840
Merge: 96eaa74 46d5daa
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Nov 3 07:07:50 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 96eaa74b799d38856aad2307323247b513ad7b54
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 14:11:49 2016 -0700

    tweak

commit 0b83d41bb461bdb2e448312230383b835b207473
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 13:58:19 2016 -0700

    universal app install

commit 32a236a770f4d44706c1ff6ccf42ad5356c72e17
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 13:56:29 2016 -0700

    store apps

commit 4b4740c7b1cb059a866002f2efeb59a741b3943f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 13:52:51 2016 -0700

    fix

commit 0c59a0748834abc6a4e6891d46bb8278c539c38e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 13:46:55 2016 -0700

    para

commit ec14c0bb9831ef0244aeb15315e7101b9d0398e4
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 13:42:21 2016 -0700

    provpkg

commit 95415738289b0aaaafc82bec086da02c210d11ad
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 13:14:33 2016 -0700

    setup complete

commit 4fae558cf3e43e03057d4803c3f61bc588d20611
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 12:18:40 2016 -0700

    dev mode

commit 757ddd1571f5a85137a5c886523241a5a0f3a38a
Merge: 54df2f7 e483298
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 11:57:55 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 54df2f7925623e0e34f96ddca27708b9c30bf9c6
Merge: 716c9c4 6bf039a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 11:43:26 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 716c9c4acb1f81b0ea26f6eb432fcb7771f2f797
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 11:42:02 2016 -0700

    fix bookmark links

commit b209765c03ad8512d72dd17ce360de0f5514e268
Merge: 7dd01fa 4bbc613
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 10:55:50 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 7dd01faa42f4c212289ad831068b93142f3af812
Merge: 8741dac 3a4201f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Nov 2 10:55:28 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

    # Conflicts:
    #	windows/manage/waas-wufb-group-policy.md

commit 8741dac33c4d49464a35061cb14108e735855061
Merge: 666383e 28f2065
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 31 07:20:09 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 666383eaf9840b0c5fb44d58270958048b7628d2
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 28 13:25:34 2016 -0700

    tweak html

commit 6f1fe823f090398ef6b8fe1d92b7a08fc6c77fe3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 28 13:09:24 2016 -0700

    fix link

commit 1090466385bb02a78498414a123c02b7b9eb0b75
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 28 12:58:28 2016 -0700

    fix html

commit 7c94bcca2aec19a7f5452661128f1de5b4359c9c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 28 12:24:45 2016 -0700

    cell width

commit 9edb64b028026604a643d7e803473ba046ca9efa
Merge: 1edd610 4a02ada
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 28 12:23:44 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 1edd610774f8037c15f40a2f0aa4201461c8aa3f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 28 11:58:50 2016 -0700

    revise

commit dc5515b42826697ce6495c2e44d3a70ea7144de2
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 28 11:15:53 2016 -0700

    updates

commit 1e5b4bd762a8148e21c61bb8b55d612cd5fcaef8
Merge: da29a85 339f8ae
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 28 11:04:14 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit da29a857837477afea4c7645e1fda0fcfffb29b4
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 27 10:09:43 2016 -0700

    sync

commit a155a1550d026fb911ccde7ca8f06f213302a24c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 27 09:59:53 2016 -0700

    sync

commit 6360103ba43b7a8a68410050e189f26ab745dc94
Merge: ddd71d7 72bcd0a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 27 08:27:05 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit ddd71d7bb1f75840c81128ea391415e9f9413d4e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 26 14:38:26 2016 -0700

    sync

commit 07df18e231fba558063b30848cb9a42172c9548b
Merge: bb053cf 4a15c27
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 26 10:09:25 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit bb053cf30bcec726edf3895358a044cbda9b97e5
Merge: 17038fa 1e0ba5e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 26 10:07:49 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 17038fae368e915ef6fd4e9eeb3f2bf400ff1f10
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 26 10:07:21 2016 -0700

    sync

commit a959cafb2f43fa3816b8ee7fc967d4d0d6e0737b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 25 13:01:22 2016 -0700

    sync

commit 2e225a12f714c977668fdb90b57d830d33fe348e
Merge: 0e9ef0d 7202a3b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 25 13:00:59 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 0e9ef0d0f572a21e6a648a47fd3ea97e5942cc16
Merge: 61b78c5 0eb189b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 25 09:58:55 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 61b78c5024971ff91e0ac73d8d43fafed36c7bac
Merge: 539ce55 0ff1977
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 25 07:37:48 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 539ce55b3d3d8461cde7a5ae12dc5d5cd3f3aca9
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 24 14:21:55 2016 -0700

    branch change

commit 9d05f9819076fbd7e77cf27cf81565cc28c248ea
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 13:47:11 2016 -0700

    fix link

commit a4bc18a1d4fe605b1d994ca36e629c6c4e05d879
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 13:43:40 2016 -0700

    ADD COMMENT

commit 5d3a83ffaf4ce9f4445975342ec0c3f2281bdcae
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 13:34:34 2016 -0700

    sync

commit fa1186dda46569ff44e4acf7819f24fd9df22c18
Merge: f90732d b247f88
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 10:22:23 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit f90732de71110d9fe817a00b88cc3bbd4a6aa1e5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 10:21:30 2016 -0700

    upgrade topic

commit 0ec13a885eafe0a3f8453a10cba6c47fda8edae5
Merge: 3db6056 8103e45
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 09:05:26 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 3db605640c2cbfef4f26512f3fa1ea6e78ee6647
Merge: 6f40a43 bbea844
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 06:57:40 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 6f40a437b66124c736c5dbcc2de24af15069a61a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 06:57:12 2016 -0700

    sync

commit 59da16c0f4b4021affc8f1fb364e8147ea3edd72
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 14:49:10 2016 -0700

    sync

commit 2e910e8deda5594b2118b0ea3d7654cf4d25b425
Merge: 3dfbb71 79efa7d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 14:49:00 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 3dfbb71cb94a5e832da0c70d287dde1d58c4547d
Merge: fef4624 2c7daec
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 12:53:29 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit fef4624e7cd1d6157e18f9e404b149d735d30bc2
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 09:50:18 2016 -0700

    sync stage

commit b6af358216d2dad1a2a4abbb58e39bb0a46611a3
Merge: a92c574 d726120
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 09:43:02 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

    # Conflicts:
    #	devices/hololens/hololens-checklist.md

commit a92c57403254b15c3b8315702a2a38416d69a0e9
Merge: 4818d5c eb3fd1d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 10:53:32 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 4818d5ccf8b03970a89a2d2caa2aca1e2bfe2bbe
Merge: c67824e c62434c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 10:12:36 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit c67824e7df9bd3f86bf07c69777752f021ba8ad0
Merge: 768e547 e7f5095
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 09:26:56 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 768e5475a31af3e1422fbc9cb431dbe974f11d8d
Merge: af05ea0 464227c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 08:22:59 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit af05ea072d45358265fed6e2f6449bbb2ecad88c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 07:51:14 2016 -0700

    force sync

commit 8221eaf2d1ddb8bed06a76e508f8f51701dccc92
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 14:45:31 2016 -0700

    start prov

commit 04ca41f40a904e15e29b13270656991a18d51617
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 14:35:26 2016 -0700

    sync

commit 1e775a00990941f4a8d378441e4ad1b0e9166196
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 14:31:01 2016 -0700

    fix title

commit 39fa1400846d07fa2fdd6ce1a49193ad8c56e7eb
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 14:28:26 2016 -0700

    resync

commit c76746075fa5b9c373654b105d928bbe0db678f3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 13:55:42 2016 -0700

    install apps

commit f6c6d341953fd64ccc23c6a27a853fcbbb485fd5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 13:51:22 2016 -0700

    new topic

commit 103ae1c9bf9f1715bfd60041e50277b903d00241
Merge: fc9cc9b 25be0d1
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 13:45:27 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit fc9cc9b89f7d945b59c154dadd0dccc7403f47d4
Merge: 339f2fc b86882f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 13:27:36 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 339f2fc40b8dc6deeb753ad5e27e3fd50de293b0
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 13:26:31 2016 -0700

    kiosk

commit 1609802453fec1ba246582a9f940e47dd982b9ae
Merge: 9627728 ef8a533
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Oct 18 09:38:09 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo

commit 96277287c335ff2e26aa303ca62b5132f06a82cb
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 15:02:54 2016 -0700

    sync

commit 9a0053a9c55e2668a884f18ff8dc3959dfc610d6
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 14:46:12 2016 -0700

    sync

commit 8a13a2a71bcd745a4ecb1452d198539c9a69bbb3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 14:37:05 2016 -0700

    sync

commit d98591c6eb55bfdddea427648808cb759279a64f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 14:13:12 2016 -0700

    initial staging-skeleton
This commit is contained in:
jdeckerMS
2016-11-15 07:07:26 -08:00
parent 5266e29186
commit 21a4d0aac8
25 changed files with 560 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
devices/hololens/TOC.md
View File

@ -1 +1,8 @@
# [Placeholder](index.md)
# [Microsoft HoloLens](index.md)
## [HoloLens in the enterprise: requirements](hololens-requirements.md)
## [Set up HoloLens](hololens-setup.md)
## [Upgrade to Windows Holographic Enterprise](hololens-upgrade-enterprise.md)
## [Enroll HoloLens in MDM](hololens-enroll-mdm.md)
## [Set up HoloLens in kiosk mode](hololens-kiosk.md)
## [Configure HoloLens using a provisioning package](hololens-provisioning.md)
## [Install apps on HoloLens](hololens-install-apps.md)

30
devices/hololens/hololens-checklist.md
View File

@ -1,30 +0,0 @@
---
title: Checklist for HoloLens in the enterprise (HoloLens)
description: tbd
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Checklist: HoloLens in the enterprise
[Introduction to configuration service providers (CSPs) for IT pros](https://technet.microsoft.com/itpro/windows/manage/how-it-pros-can-use-configuration-service-providers)
Windows Store for Business
Requirements
- IT Admins: Before you sign up for the Store for Business, at a minimum, you'll need an Azure Active Directory (AAD) account for your organization, and you'll need to be the global administrator for your organization. Once the Global Admin has signed in, they can give permissions to other employees.
- End Users: Need Azure AD account when they access Store for Business content from Windows-based devices.
[Getting started with Azure Active Directory Premium](https://azure.microsoft.com/en-us/documentation/articles/active-directory-get-started-premium/)
[Get started with Intune](https://docs.microsoft.com/en-us/intune/understand-explore/get-started-with-a-30-day-trial-of-microsoft-intune)
[Enroll devices for management in Intune](https://docs.microsoft.com/en-us/intune/deploy-use/enroll-devices-in-microsoft-intune#supported-device-platforms)
[Azure AD editions](https://azure.microsoft.com/en-us/documentation/articles/active-directory-editions/)

38
devices/hololens/hololens-enroll-mdm.md Normal file
View File

@ -0,0 +1,38 @@
---
title: Enroll HoloLens in MDM (HoloLens)
description: Enroll HoloLens in mobile device management (MDM) for easier management of multiple devices.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Enroll HoloLens in MDM
You can manage multiple HoloLens devices simultaneously using solutions like Microsoft InTune. You will be able to manage settings, select apps to install and set security configurations tailored to your organization's need.
>[!NOTE]
>Mobile device management (MDM) for Development Edition HoloLens does not include VPN, BitLocker, or kiosk mode. Those features are only available when you [upgrade to Windows Holographic Enterprise](hololens-upgrade-enterprise.md).
## Requirements
Your organization will need to have mobile device management (MDM) set up in order to manage HoloLens devices. Your MDM provider can be Microsoft Intune or a 3rd party provider that uses Microsoft MDM APIs.
## Auto-enrollment in MDM
If your organization uses Azure Active Directory (Azure AD) and an MDM solution that accepts an AAD token for authentication (currently, only supported in Microsoft Intune and Airwatch), your IT admin can configure Azure AD to automatically allow MDM enrollment after the user signs in with their Azure AD account. [Learn how to configure Azure AD enrollment.](https://docs.microsoft.com/intune/deploy-use/set-up-windows-device-management-with-microsoft-intune#azure-active-directory-enrollment)
When auto-enrollment is enabled, no additional manual enrollment is needed. When the user signs in with an Azure AD account, the device is enrolled in MDM after completing the first-run experience.
## Enroll through Settings app
When the device is not enrolled in MDM during the first-run experience, the user can manually enroll the device with the organization's MDM server using the Settings app.
1. Go to **Settings** > **Accounts** > **Work access**.
2. Select **Enroll into device management** and enter your organizational account. You will be redirected to your organization's sign in page.
4. Upon successful authentication to the MDM server, a success message is shown.
Your device is now enrolled with your MDM server. The device will need to restart to acquire policies, certificates, and apps. The Settings app will now reflect that the device is enrolled in device management.

86
devices/hololens/hololens-install-apps.md Normal file
View File

@ -0,0 +1,86 @@
---
title: Install apps on HoloLens (HoloLens)
description: The recommended way to install apps on HoloLens is to use Windows Store for Business.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Install apps on HoloLens
The recommended way to install Universal Windows Platform (UWP) apps on HoloLens is to use Windows Store for Business. You can make your own [line-of-business application](https://technet.microsoft.com/itpro/windows/manage/working-with-line-of-business-apps) available through Windows Store for Business.
You can also deploy apps using your mobile device management (MDM) provider or use the Windows Device Portal to install apps, if you enable **Developer Mode** on the HoloLens device.
>[!IMPORTANT]
>When you set up HoloLens to use the Device Portal, you must enable **Developer Mode** on the device.** Developer Mode** on a device that has been upgraded to Windows Holographic Enterprise enables side-loading of apps, which risks the installation of apps that have not been certified by the Microsoft Store. Administrators can block the ability to enable **Developer Mode** using the **ApplicationManagement/AllowDeveloper Unlock** setting in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). [Learn more about Developer Mode.](https://msdn.microsoft.com/windows/uwp/get-started/enable-your-device-for-development#developer-mode)
## Use Windows Store for Business to deploy apps to HoloLens
Windows Store for Business is a private Windows Store for your enterprise. People in your organization can open the Store app and select your private Store to install apps that you have made available to them.
![How Windows Store for Business appears in Store app](images/wsfb-private.png)
In your Windows Store for Business dashboard, you can also download apps to distribute to devices that aren't connected to the Internet, plus add line-of-business (LOB) apps for distribution.
### Requirements
- You need to be a global administrator for your Azure Active Directory (Azure AD) tenant.
>[!TIP]
>You can create an Azure AD account and tenant as part of the Store for Business sign-up process.
- End users need Azure AD accounts when they access Store for Business content from Windows-based devices.
### Windows Store for Business process
1. [Sign up for Windows Store for Business.](https://technet.microsoft.com/itpro/windows/manage/sign-up-windows-store-for-business)
2. [Assign roles and permissions for managing your Store for Business.](https://technet.microsoft.com/itpro/windows/manage/roles-and-permissions-windows-store-for-business)
3. (Optional) [Configure Windows Store for Business to work with your MDM provider.](https://technet.microsoft.com/itpro/windows/manage/configure-mdm-provider-windows-store-for-business)
3. [Get apps for your Store for Business.](https://technet.microsoft.com/itpro/windows/manage/acquire-apps-windows-store-for-business)
4. [Distribute apps to your employees.](https://technet.microsoft.com/itpro/windows/manage/distribute-apps-to-your-employees-windows-store-for-business)
### Install apps on HoloLens from Windows Store for Business
The method that you use to install an app from your Windows Store for Business on HoloLens depends on the the distribution method that you choose.
| Distribution method | To install on HoloLens|
| --- | --- |
| Using private store | Open the Store app and select the tab for your organization to choose from available apps. |
| Using MDM | [You can configure MDM to synchronize your Store for Business inventory.](https://technet.microsoft.com/itpro/windows/manage/distribute-apps-with-management-tool) |
## Use MDM to deploy apps to HoloLens
You can deploy UWP apps to HoloLens using your MDM provider. For Intune instructions, see [Deploy apps in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/add-apps).
Using Intune, you can also [monitor your app deployment](https://docs.microsoft.com/intune/deploy-use/monitor-apps-in-microsoft-intune).
## Use the Windows Device Portal to install apps on HoloLens.
1. [Set up the HoloLens to use the Windows Device Portal](https://developer.microsoft.com/windows/holographic/using_the_windows_device_portal#setting_up_hololens_to_use_windows_device_portal). The Device Portal is a web server on your HoloLens that you can connect to from a web browser on your PC.
2. On a PC, connect to the HoloLens using [Wi-Fi](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#connecting_over_wi-fi) or [USB](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#connecting_over_usb).
3. [Create a user name and password](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#creating_a_username_and_password) if this is the first time you connect to the Windows Device Portal, or enter the user name and password that you previously set up.
>[!TIP]
>If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#security_certificate).
4. In the Windows Device Portal, click **Apps**.
![App Manager](images/apps.png)
5. In **Install app**, select an **app package** from a folder on your computer or network. If the app package requires additional software, click **Add dependency**.
6. In **Deploy**, click **Go** to deploy the app package and added dependencies to the connected HoloLens.

37
devices/hololens/hololens-kiosk.md Normal file
View File

@ -0,0 +1,37 @@
---
title: Set up HoloLens in kiosk mode (HoloLens)
description: Kiosk mode limits the user's ability to launch new apps or change the running app.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Set up HoloLens in kiosk mode
Kiosk mode limits the user's ability to launch new apps or change the running app. When kiosk mode is enabled for HoloLens, the bloom gesture and Cortana are disabled, and placed apps aren't shown in the user's surroundings.
1. [Set up the HoloLens to use the Windows Device Portal](https://developer.microsoft.com/windows/holographic/using_the_windows_device_portal#setting_up_hololens_to_use_windows_device_portal). The Device Portal is a web server on your HoloLens that you can connect to from a web browser on your PC.
>[!IMPORTANT]
>When you set up HoloLens to use the Device Portal, you must enable **Developer Mode** on the device. **Developer Mode** on a device that has been upgraded to Windows Holographic Enterprise enables side-loading of apps, which risks the installation of apps that have not been certified by the Microsoft Store. Administrators can block the ability to enable **Developer Mode** using the **ApplicationManagement/AllowDeveloper Unlock** setting in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). [Learn more about Developer Mode.](https://msdn.microsoft.com/windows/uwp/get-started/enable-your-device-for-development#developer-mode)
2. On a PC, connect to the HoloLens using [Wi-Fi](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#connecting_over_wi-fi) or [USB](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#connecting_over_usb).
3. [Create a user name and password](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#creating_a_username_and_password) if this is the first time you connect to the Windows Device Portal, or enter the user name and password that you previously set up.
>[!TIP]
>If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#security_certificate).
4. In the Windows Device Portal, click **Kiosk Mode**.
![Kiosk Mode](images/kiosk.png)
>[!NOTE]
>The kiosk mode option will be available if the device is [enrolled in device management](hololens-enroll-mdm.md) and has an [Enterprise license](hololens-upgrade-enterprise.md).
5. Select **Enable Kiosk Mode**, choose an app to run when the device starts, and click **Save**.

120
devices/hololens/hololens-provisioning.md Normal file
View File

@ -0,0 +1,120 @@
---
title: Configure HoloLens using a provisioning package (HoloLens)
description: Windows provisioning makes it easy for IT administrators to configure end-user devices without imaging.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Configure HoloLens using a provisioning package
Windows provisioning makes it easy for IT administrators to configure end-user devices without imaging. The Windows Assessment and Deployment Kit (ADK) for Windows 10 includes the Imaging and Configuration Designer (ICD), a tool for configuring images and runtime settings which are then built into provisioning packages.
Some of the HoloLens configurations that you can apply in a provisioning package:
- Upgrade to Windows Holographic Enterprise
- Set up a local account
- Set up a Wi-Fi connection
- Apply certificatess to the device
To install Windows ICD and create provisioning packages, you must [install the Windows Assessment and Deployment Kit (ADK) for Windows 10](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
When you run ADKsetup.exe for Windows 10, version 1607, select **Configuration Designer** from the **Select the features you want to install** dialog box.
![Choose Configuration Designer](images/adk-install.png)
> [!NOTE]
> In previous versions of the Windows 10 ADK, you had to install additional features for Windows ICD to run. Starting in version 1607, you can install Windows ICD without other ADK features.
## Create a provisioning package for HoloLens
>[!NOTE]
>Settings in a provisioning package will only be applied if the provisioning package includes an edition upgrade license to Windows Holographic Enterprise or if [the device has already been upgraded to Windows Holographic Enterprise](hololens-upgrade-enterprise.md).
1. On the Windows ICD start page, select **Advanced provisioning**.
2. In the **Enter project details** window, specify a name for your project and the location for your project. Optionally, enter a brief description to describe your project.
3. Click **Next**.
4. In the **Choose which settings to view and configure** window, select **Windows 10 Holographic**, and then click **Next**.
6. Click **Finish**.
7. Expand **Runtime settings** and customize the package with any of the settings [described below](#what-you-can-configure).
>[!IMPORTANT]
>If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. If the user account is locked out, you must [perform a full device recovery](https://developer.microsoft.com/windows/holographic/reset_or_recover_your_hololens#perform_a_full_device_recovery).
8. On the **File** menu, click **Save**.
4. Read the warning that project files may contain sensitive information, and click **OK**.
>[!IMPORTANT]
>When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
3. On the **Export** menu, click **Provisioning package**.
4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources, and then select **Next**.
5. Set a value for **Package Version**.
>[!TIP]
>You can make changes to existing packages and change the version number to update previously applied packages.
6. On the **Select security details for the provisioning package**, click **Next**.
7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.
Optionally, you can click Browse to change the default output location.
8. Click **Next**.
9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.
10. When the build completes, click **Finish**.
## Apply a provisioning package to HoloLens
1. Connect the device via USB to a PC and start the device, but do not continue past the **fit** page of OOBE (the first page with the blue box).
2. Briefly press and release the **Volume Down** and **Power** buttons simultaneously.
3. HoloLens will show up as a device in File Explorer on the PC.
4. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.
5. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the **fit** page.
6. The device will ask you if you trust the package and would like to apply it. Confirm that you trust the package.
7. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with OOBE.
>[!NOTE]
>If the device was purchased before August 2016, you will need to sign into the device with aa Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.
## What you can configure
Provisioning packages make use of configuration service providers (CSPs). If you're not familiar with CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](https://technet.microsoft.com/itpro/windows/manage/how-it-pros-can-use-configuration-service-providers).
In Windows ICD, when you create a provisioning package for Windows Holographic, the settings in **Available customizations** are based on [CSPs that are supported in Windows Holographic](https://msdn.microsoft.co/library/windows/hardware/dn920025.aspx#HoloLens). The following table describes settings that you might want to configure for HoloLens.
![Common runtime settings for HoloLens](images/icd-settings.png)
| Setting | Description |
| --- | --- |
| **Accounts** | Create a local account. HoloLens currently supports a single user only. Creating multiple local accounts in a provisioning package is not supported. <br><br>**IMPORTANT**<br>If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. If the user account is locked out, you must [perform a full device recovery](https://developer.microsoft.com/windows/holographic/reset_or_recover_your_hololens#perform_a_full_device_recovery). |
| **Certificates** | Deploy a certificate to HoloLens. |
| **ConnectivityProfiles** | Deploy a Wi-Fi profile to HoloLens. |
| **EditionUpgrade** | [Upgrade to Windows Holographic Enterprise.](hololens-upgrade-enterprise.md) |
| **Policies** | Allow or prevent developer mode on HoloLens. |
>[!NOTE]
>App installation (**UniversalAppInstall**) using a provisioning package is not currently supported for HoloLens.

54
devices/hololens/hololens-requirements.md Normal file
View File

@ -0,0 +1,54 @@
---
title: HoloLens in the enterprise requirements (HoloLens)
description: Requirements for general use, Wi-Fi, and device management for HoloLens in the enterprise.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Microsoft HoloLens in the enterprise: requirements
When you develop for HoloLens, there are [system requirements and tools](https://developer.microsoft.com/windows/holographic/install_the_tools) that you need. In an enterprise environment, there are also a few requirements to use and manage HoloLens which are listed below.
## General use
- Microsoft account or Azure Active Directory (Azure AD) account
- Wi-Fi network to set up HoloLens
>[!NOTE]
>After you set up HoloLens, you can use it offline [with some limitations](https://support.microsoft.com/help/12645/hololens-use-hololens-offline).
## Supported wireless network EAP methods
- PEAP-MS-CHAPv2
- PEAP-TLS
- TLS
- TTLS-CHAP
- TTLS-CHAPv2
- TTLS-MS-CHAPv2
- TTLS-PAP
- TTLS-TLS
## Device management
- Users have Azure AD accounts with [Intune license assigned](https://docs.microsoft.com/intune/get-started/start-with-a-paid-subscription-to-microsoft-intune-step-4)
- Wi-Fi network
- Intune or a 3rd party mobile device management (MDM) provider that uses Microsoft MDM APIs
## Upgrade to Windows Holographic Enterprise
- HoloLens Enterprise license XML file
## Related resources
[Getting started with Azure Active Directory Premium](https://azure.microsoft.com/en-us/documentation/articles/active-directory-get-started-premium/)
[Get started with Intune](https://docs.microsoft.com/en-us/intune/understand-explore/get-started-with-a-30-day-trial-of-microsoft-intune)
[Enroll devices for management in Intune](https://docs.microsoft.com/en-us/intune/deploy-use/enroll-devices-in-microsoft-intune#supported-device-platforms)
[Azure AD editions](https://azure.microsoft.com/en-us/documentation/articles/active-directory-editions/)

43
devices/hololens/hololens-setup.md Normal file
View File

@ -0,0 +1,43 @@
---
title: Set up HoloLens (HoloLens)
description: The first time you set up HoloLens, you'll need a Wi-Fi network and either a Microsoft or Azure Active Directory account.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Set up HoloLens
Before you get started setting up your HoloLens, make sure you have a Wi-Fi network and a Microsoft account or an Azure Active Directory (Azure AD) account.
## Network connectivity requirements
The first time you use your HoloLens, you'll be guided through connecting to a Wi-Fi network. You need to connect HoloLens to a Wi-Fi network with Internet connectivity so that the user account can be authenticated.
- It can be an open Wi-Fi or password-protected Wi-Fi network.
- The Wi-Fi network cannot require you to navigate to a webpage to connect.
- The Wi-Fi network cannot require certificates to connect.
- The Wi-Fi network does not need to provide access to enterprise resources or intranet sites.
## HoloLens setup
The HoloLens setup process combines a quick tutorial on using HoloLens with the steps needed to connect to the network and add an account.
1. Be sure your HoloLens is [charged](https://support.microsoft.com/help/12627), then [adjust it](https://support.microsoft.com/help/12632) for a comfortable fit.
2. [Turn on HoloLens](https://support.microsoft.com/help/12642). You will be guided through a calibration procedure and how to perform [the gestures](https://support.microsoft.com/help/12644/hololens-use-gestures) that you will use to operate HoloLens.
3. Next, you'll be guided through connecting to a Wi-Fi network.
4. After HoloLens connects to the Wi-Fi network, you select between **My work or school owns it** and **I own it**.
- When you choose **My work or school owns it**, you sign in with an Azure AD account. If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens will be enrolled in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available, so you will need to [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
1. Enter your organizational account.
2. Accept privacy statement.
3. Sign in using your Azure AD credentials. This may redirect to your organization's sign-in page.
4. Continue with device setup.
- When you choose **I own it**, you sign in with a Microsoft account. After setup is complete, you can [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
1. Enter your Microsoft account.
2. Enter your password. If your Microsoft account requires [two-step verification (2FA)](https://blogs.technet.microsoft.com/microsoft_blog/2013/04/17/microsoft-account-gets-more-secure/), complete the verification process.
5. The device sets your time zone based on information obtained from the Wi-Fi network.
6. Next, you learn how to perform the bloom gesture and how to select and place the Start screen. After you place the Start screen, setup is complete and you can begin using HoloLens.

136
devices/hololens/hololens-upgrade-enterprise.md Normal file
View File

@ -0,0 +1,136 @@
---
title: Upgrade to Windows Holographic Enterprise (HoloLens)
description: HoloLens provides extra features designed for business when you upgrade to Windows Holographic Enterprise.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Upgrade to Windows Holographic Enterprise
Microsoft HoloLens is available in the *Development Edition*, which runs Windows Holographic (an edition of Windows 10 designed for HoloLens), and in the [Commercial Suite](https://developer.microsoft.com/windows/holographic/release_notes#introducing_microsoft_hololens_commercial_suite), which provides extra features designed for business.
When you purchase the Commercial Suite, you receive a license that upgrades Windows Holographic to Windows Holographic Enterprise. This license can be applied to the device either through the organization's [mobile device management (MDM) provider](#edition-upgrade-using-mdm) or a [provisioning package](#edition-upgrade-using-a-provisioning-package).
>[!TIP]
>You can tell that the HoloLens has been upgraded to the Enterprise edition in **Settings** > **Network & Internet**. The **VPN** option is only available in Windows Holographic Enterprise.
## Edition upgrade using MDM
The enterprise license can be applied by any MDM provider that supports the [WindowsLicensing configuration service provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn904983.aspx). The latest version of the Microsoft MDM API will support WindowsLicensing CSP.
**Overview**
1. Set up the edition upgrade policy.
2. Deploy the policy.
3. [Enroll the device through the Settings app](hololens-enroll-mdm.md).
The procedures in this topic use Microsoft Intune as an example. On other MDM providers, the specific steps for setting up and deploying the policy might vary.
### Set up the Edition Upgrade policy
1. Sign into the Intune Dashboard with your Intune admin account.
2. In the **Policy** workspace, select **Configuration Policies** and then **Add**.
![Click Add](images/intune1.png)
3. In **Create a new policy**, select the **Edition Upgrade Policy (Windows 10 Holographic and later** template, and click **Create Policy**.
![Select template](images/intune2.png)
4. Enter a name for the policy.
5. In the **Edition Upgrade** section, in **License File**, browse to and select the XML license file that was provided when you purchased the Commercial Suite.
![Enter the XML file name](images/intune3.png)
5. Click **Save Policy**.
### Deploy the Edition Upgrade policy
Next, you will assign the Edition Upgrade policy to selected groups.
1. In the **Policy** workspace, select the Edition upgrade policy that you created, and then choose **Manage Deployment**.
2. In the **Manage Deployment** dialog box, select one or more groups to which you want to deploy the policy, and then choose **Add** > **OK**.
When these users enroll their devices in MDM, the Edition Upgrade policy will be applied.
For more information about groups, see [Use groups to manage users and devices in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/use-groups-to-manage-users-and-devices-with-microsoft-intune).
## Edition upgrade using a provisioning package
Provisioning packages are files created by the Windows Imaging and Configuration Designer (ICD) tool that apply a specified configuration to a device.
### Create a provisioning package that upgrades the Windows Holographic edition
1. [Create a provisioning package for HoloLens.](hololens-provisioning.md#create-a-provisioning-package-for-hololens)
2. Go to **Runtime settings** > **EditionUpgrade**, and select **EditionUpgradeWithLicense**.
![Upgrade edition with license setting selected](images/icd1.png)
2. Browse to and select the XML license file that was provided when you purchased the Commercial Suite.
>[!NOTE]
>You can configure [additional settings in the provisioning package](hololens-provisioning.md).
3. On the **File** menu, click **Save**.
4. Read the warning that project files may contain sensitive information, and click **OK**.
>[!IMPORTANT]
>When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
3. On the **Export** menu, click **Provisioning package**.
4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources, and then select **Next**.
5. Set a value for **Package Version**.
>[!TIP]
>You can make changes to existing packages and change the version number to update previously applied packages.
6. On the **Select security details for the provisioning package**, click **Next**.
7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.
Optionally, you can click Browse to change the default output location.
8. Click **Next**.
9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.
10. When the build completes, click **Finish**.
### Apply the provisioning package to HoloLens
1. Connect the device via USB to a PC and start the device, but do not continue past the **fit** page of OOBE (the first page with the blue box).
2. Briefly press and release the **Volume Down** and **Power** buttons simultaneously.
3. HoloLens will show up as a device in File Explorer on the PC.
4. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.
5. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the **fit** page.
6. The device will ask you if you trust the package and would like to apply it. Confirm that you trust the package.
7. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with OOBE.
>[!NOTE]
>If the device was purchased before August 2016, you will need to sign into the device with aa Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.

BIN
devices/hololens/images/adk-install.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 65 KiB

BIN
devices/hololens/images/apps.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 91 KiB

BIN
devices/hololens/images/hololens.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 76 KiB

BIN
devices/hololens/images/icd-settings.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 12 KiB

BIN
devices/hololens/images/icd1.PNG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

BIN
devices/hololens/images/intune1.PNG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 23 KiB

BIN
devices/hololens/images/intune2.PNG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 44 KiB

BIN
devices/hololens/images/intune3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 147 KiB

BIN
devices/hololens/images/kiosk.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 64 KiB

BIN
devices/hololens/images/upgrade-flow.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 47 KiB

BIN
devices/hololens/images/uwp-dependencies.PNG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 19 KiB

BIN
devices/hololens/images/uwp-license.PNG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 11 KiB

BIN
devices/hololens/images/windows-device-portal-home-page.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 184 KiB

BIN
devices/hololens/images/wsfb-private.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 18 KiB

38
devices/hololens/index.md
View File

@ -1,3 +1,39 @@
---
redirect_url: https://developer.microsoft.com/windows/holographic/commercial_features
title: Microsoft HoloLens (HoloLens)
description: HoloLens provides extra features designed for business in the Commercial Suite.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: hololens, devices
ms.sitesec: library
author: jdeckerMS
---
# Microsoft HoloLens
<table><tbody>
<tr><td style="border: 0px;width: 75%;valign= top"><p>Microsoft HoloLens is the first fully self-contained holographic computer running Windows 10.</p><p> Microsoft HoloLens is available in the **Development Edition**, which runs Windows Holographic (an edition of Windows 10 designed for HoloLens), and in the **Commercial Suite**, which runs Windows Holographic Enterprise when you apply the Enterprise license file to the device.</p></td><td align="left" style="border: 0px">![Hololens](images/hololens.png)</td></tr>
</tbody></table>
## In this section
| Topic | Description |
| --- | --- |
| [HoloLens in the enterprise: requirements](hololens-requirements.md) | Lists requirements for general use, Wi-Fi, and device management |
| [Set up HoloLens](hololens-setup.md) | How to set up HoloLens for the first time |
| [Upgrade to Windows Holographic Enterprise](hololens-upgrade-enterprise.md) | How to upgrade your Development Edition HoloLens to Windows Holographic Enterprise|
| [Enroll HoloLens in MDM](hololens-enroll-mdm.md) | Manage multiple HoloLens devices simultaneously using solutions like Microsoft InTune |
| [Set up HoloLens in kiosk mode](hololens-kiosk.md) | Enable kiosk mode for HoloLens, which limits the user's ability to launch new apps or change the running app |
| [Configure HoloLens using a provisioning package](hololens-provisioning.md) | Provisioning packages make it easy for IT administrators to configure HoloLens devices without imaging |
| [Install apps on HoloLens](hololens-install-apps.md) | Use Windows Store for Business, mobile device management (MDM), or the Windows Device Portal to install apps on HoloLens|
## Related resources
- [Help for using HoloLens](https://support.microsoft.com/products/hololens)
- [Documentation for Holographic app development](https://developer.microsoft.com/windows/holographic/documentation)
- [HoloLens Commercial Suite](https://www.microsoft.com/microsoft-hololens/hololens-commercial)
- [HoloLens release notes](https://developer.microsoft.com/en-us/windows/holographic/release_notes)