mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-23 10:47:22 +00:00
Edits
This commit is contained in:
parent
f3c67ba59e
commit
2cef09d82b
@ -1,37 +1,39 @@
|
|||||||
---
|
---
|
||||||
title: Unlock Windows Holographic for Business features (HoloLens)
|
title: Unlock Windows Holographic for Business features
|
||||||
description: HoloLens provides extra features designed for business when you upgrade to Windows Holographic for Business.
|
description: When you upgrade to Windows Holographic for Business, HoloLens provides extra features that are designed for business.
|
||||||
ms.prod: hololens
|
ms.prod: hololens
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
author: dansimp
|
author: dansimp
|
||||||
ms.author: dansimp
|
ms.author: dansimp
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 07/09/2018
|
ms.date: 9/16/2019
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: dansimp
|
manager: jarrettr
|
||||||
|
appliesto:
|
||||||
|
- HoloLens (1st gen)
|
||||||
---
|
---
|
||||||
|
|
||||||
# Unlock Windows Holographic for Business features
|
# Unlock Windows Holographic for Business features
|
||||||
|
|
||||||
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](hololens-commercial-features.md), which provides extra features designed for business.
|
Microsoft HoloLens is available in the *Development Edition*, which runs Windows Holographic (an edition of Windows 10 that is designed for HoloLens), and in the [Commercial Suite](hololens-commercial-features.md), which provides extra features that are designed for business.
|
||||||
|
|
||||||
When you purchase the Commercial Suite, you receive a license that upgrades Windows Holographic to Windows Holographic for Business. 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).
|
When you purchase the Commercial Suite, you receive a license that upgrades Windows Holographic to Windows Holographic for Business. You can apply this license to the device either by using the organization's [mobile device management (MDM) provider](#edition-upgrade-using-mdm) or a [provisioning package](#edition-upgrade-using-a-provisioning-package).
|
||||||
|
|
||||||
> [!TIP]
|
> [!TIP]
|
||||||
> In Windows 10, version 1803, you can tell that the HoloLens has been upgraded to the business edition in **Settings** > **System**.
|
> In Windows 10, version 1803, you can tell that the HoloLens has been upgraded to the business edition by selecting **Settings** > **System**.
|
||||||
|
|
||||||
## Edition upgrade using MDM
|
## Edition upgrade by 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.
|
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.
|
||||||
|
|
||||||
For step-by-step instructions for upgrading HoloLens using Microsoft Intune, see [Upgrade devices running Windows Holographic to Windows Holographic for Business](https://docs.microsoft.com/intune/holographic-upgrade).
|
For step-by-step instructions for upgrading HoloLens by using Microsoft Intune, see [Upgrade devices running Windows Holographic to Windows Holographic for Business](https://docs.microsoft.com/intune/holographic-upgrade).
|
||||||
|
|
||||||
On other MDM providers, the specific steps for setting up and deploying the policy might vary.
|
On other MDM providers, the specific steps for setting up and deploying the policy might vary.
|
||||||
|
|
||||||
## Edition upgrade using a provisioning package
|
## Edition upgrade by using a provisioning package
|
||||||
|
|
||||||
Provisioning packages are files created by the Windows Configuration Designer tool that apply a specified configuration to a device.
|
Provisioning packages are files that are created by the Windows Configuration Designer tool that apply a specified configuration to a device.
|
||||||
|
|
||||||
### Create a provisioning package that upgrades the Windows Holographic edition
|
### Create a provisioning package that upgrades the Windows Holographic edition
|
||||||
|
|
||||||
@ -45,45 +47,45 @@ Provisioning packages are files created by the Windows Configuration Designer to
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> You can configure [additional settings in the provisioning package](hololens-provisioning.md).
|
> You can configure [additional settings in the provisioning package](hololens-provisioning.md).
|
||||||
|
|
||||||
1. On the **File** menu, click **Save**.
|
1. On the **File** menu, select **Save**.
|
||||||
|
|
||||||
1. Read the warning that project files may contain sensitive information, and click **OK**.
|
1. Read the warning that project files may contain sensitive information, and click **OK**.
|
||||||
|
|
||||||
> [!IMPORTANT]
|
> [!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.
|
> 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.
|
||||||
|
|
||||||
1. On the **Export** menu, click **Provisioning package**.
|
1. On the **Export** menu, select **Provisioning package**.
|
||||||
|
|
||||||
1. 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**.
|
1. Change **Owner** to **IT Admin**, which sets the precedence of this provisioning package to be higher than that of provisioning packages that are applied to this device from other sources, and then select **Next**.
|
||||||
|
|
||||||
1. Set a value for **Package Version**.
|
1. Set a value for **Package Version**.
|
||||||
|
|
||||||
> [!TIP]
|
> [!TIP]
|
||||||
> You can make changes to existing packages and change the version number to update previously applied packages.
|
> You can make changes to existing packages and change the version number to update previously applied packages.
|
||||||
|
|
||||||
1. On the **Select security details for the provisioning package**, click **Next**.
|
1. On **Select security details for the provisioning package**, select **Next**.
|
||||||
|
|
||||||
1. 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.
|
1. Select **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.
|
Optionally, you can select **Browse** to change the default output location.
|
||||||
|
|
||||||
1. Click **Next**.
|
1. Select **Next**.
|
||||||
|
|
||||||
1. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.
|
1. Select **Build** to start building the package. The build page displays the project information, and the progress bar indicates the build status.
|
||||||
|
|
||||||
1. When the build completes, click **Finish**.
|
1. When the build completes, select **Finish**.
|
||||||
|
|
||||||
### Apply the provisioning package to HoloLens
|
### 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 the initial setup experience (the first page with the blue box). HoloLens will show up as a device in File Explorer on the PC.
|
1. Using the USB cable, connect the device to a PC. Start the device, but do not continue past the **fit** page of the initial setup experience (the first page with the blue box). On the PC, HoloLens shows up as a device in File Explorer.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> If the HoloLens device is running Windows 10, version 1607 or earlier, briefly press and release the **Volume Down** and **Power** buttons simultaneously to open File Explorer.
|
> If the HoloLens device is running Windows 10, version 1607 or earlier, open File Explorer by briefly pressing and releasing the **Volume Down** and **Power** buttons simultaneously on the device.
|
||||||
|
|
||||||
1. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.
|
1. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.
|
||||||
|
|
||||||
1. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the **fit** page.
|
1. While HoloLens is still non the **fit** page, briefly press and release the **Volume Down** and **Power** buttons simultaneously again.
|
||||||
|
|
||||||
1. The device will ask you if you trust the package and would like to apply it. Confirm that you trust the package.
|
1. HoloLens asks you if you trust the package and would like to apply it. Confirm that you trust the package.
|
||||||
|
|
||||||
1. 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 device setup.
|
1. You will see whether the package was applied successfully or not. If it was not applied successfully, you can fix your package and try again. If it succeeded, proceed with device setup.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user