mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-21 17:57:22 +00:00
chore: MarkDown Note marker compatibility spacing
**Description:** - Hololens directory This PR is a standalone attempt to standardize the MarkDown Note bubbles by adding the recommended single space after the quote marker. MarkDown codestyle consistency is the main goal here. **Changes proposed:** - Add single space between the quote marker and the text [!NOTE] - Add the same spacing to the connected text lines in the same bubble - Do the same to other nearby notes [!TIP], [!WARNING], [!IMPORTANT] - Standardize on uppercase [!NOTE] instead of mixed casing ( [!Note] ) - Remove incorrect space in code block syntax highlighting **Ticket reference or closure:** None that I know of (at least not yet). **Additional notes:** I have split this modification chore into sub-folder sections to keep the number of files within a reasonably manageable amount.
This commit is contained in:
illfated
parent
8273da51ff
commit
533446960d
@ -64,8 +64,8 @@ Guides only require network access to download and use the app.
|
||||
|
||||
## Azure Active Directory Guidance
|
||||
|
||||
>[!NOTE]
|
||||
>This step is only necessary if your company plans on managing the HoloLens and mixed reality apps.
|
||||
> [!NOTE]
|
||||
> This step is only necessary if your company plans on managing the HoloLens and mixed reality apps.
|
||||
|
||||
1. Ensure that you have an Azure AD License.
|
||||
Please [HoloLens Licenses Requirements](hololens-licenses-requirements.md)for additional information.
|
||||
@ -99,8 +99,8 @@ These steps ensure that your company’s users (or a group of users) can add dev
|
||||
|
||||
### Ongoing device management
|
||||
|
||||
>[!NOTE]
|
||||
>This step is only necessary if your company plans on managing the HoloLens and mixed reality apps.
|
||||
> [!NOTE]
|
||||
> This step is only necessary if your company plans on managing the HoloLens and mixed reality apps.
|
||||
Ongoing device management will depend on your mobile device management infrastructure. Most have the same general functionality but the user interface may vary widely.
|
||||
|
||||
1. [CSPs (Configuration Service Providers)](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices) allows you to create and deploy management settings for the devices on your network. Some CSPs are supported by HoloLens devices. (See the list of CSPs for HoloLens [here](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices)).
|
||||
@ -150,8 +150,8 @@ Steps for SCEP can be found [here](https://docs.microsoft.com/intune/protect/cer
|
||||
|
||||
### How to Upgrade to Holographics for Business Commercial Suite
|
||||
|
||||
>[!NOTE]
|
||||
>Windows Holographics for Business (commercial suite) is only intended for HoloLens 1st gen devices. The profile will not be applied to HoloLens 2 devices.
|
||||
> [!NOTE]
|
||||
> Windows Holographics for Business (commercial suite) is only intended for HoloLens 1st gen devices. The profile will not be applied to HoloLens 2 devices.
|
||||
|
||||
Directions for upgrading to the commercial suite can be found [here](https://docs.microsoft.com/intune/configuration/holographic-upgrade).
|
||||
|
||||
|
||||
@ -36,8 +36,8 @@ Get around HoloLens faster with these basic commands. In order to use these you
|
||||
|
||||
Use these commands throughout Windows Mixed Reality to get around faster. Some commands use the gaze cursor, which you bring up by saying “select.”
|
||||
|
||||
>[!NOTE]
|
||||
>Hand rays are not supported on HoloLens (1st Gen).
|
||||
> [!NOTE]
|
||||
> Hand rays are not supported on HoloLens (1st Gen).
|
||||
|
||||
| Say this | To do this |
|
||||
| - | - |
|
||||
|
||||
@ -51,22 +51,22 @@ Provisioning packages are files created by the Windows Configuration Designer to
|
||||
1. Find the XML license file that was provided when you purchased the Commercial Suite.
|
||||
|
||||
1. 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).
|
||||
> [!NOTE]
|
||||
> You can configure [additional settings in the provisioning package](hololens-provisioning.md).
|
||||
|
||||
1. On the **File** menu, click **Save**.
|
||||
|
||||
1. Read the warning explaining 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 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 no longer needed.
|
||||
> [!IMPORTANT]
|
||||
> When you build a provisioning package, you may include sensitive information in the project files and 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 no longer needed.
|
||||
|
||||
1. On the **Export** menu, click **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. Set a value for **Package Version**.
|
||||
|
||||
>[!TIP]
|
||||
>You can make changes to existing packages and change the version number to update previously applied packages.
|
||||
> [!TIP]
|
||||
> 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. 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.
|
||||
@ -87,8 +87,8 @@ Provisioning packages are files created by the Windows Configuration Designer to
|
||||
1. The device will ask 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.
|
||||
|
||||
>[!NOTE]
|
||||
>If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.
|
||||
> [!NOTE]
|
||||
> If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.
|
||||
|
||||
## Verify device encryption
|
||||
|
||||
|
||||
@ -20,8 +20,8 @@ appliesto:
|
||||
|
||||
You can manage multiple Microsoft HoloLens devices simultaneously using solutions like [Microsoft Intune](https://docs.microsoft.com/intune/windows-holographic-for-business). You will be able to manage settings, select apps to install and set security configurations tailored to your organization's need. See [Manage devices running Windows Holographic with Microsoft Intune](https://docs.microsoft.com/intune/windows-holographic-for-business), the [configuration service providers (CSPs) that are supported in Windows Holographic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/configuration-service-provider-reference#hololens), and the [policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies).
|
||||
|
||||
>[!NOTE]
|
||||
>Mobile device management (MDM), including the VPN, Bitlocker, and kiosk mode features, is only available when you [upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
> [!NOTE]
|
||||
> Mobile device management (MDM), including the VPN, Bitlocker, and kiosk mode features, is only available when you [upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
|
||||
## Requirements
|
||||
|
||||
|
||||
@ -46,8 +46,8 @@ To opt out of Insider builds:
|
||||
|
||||
Please use [the Feedback Hub app](hololens-feedback.md) on your HoloLens to provide feedback and report issues. Using Feedback Hub ensures that all necessary diagnostics information is included to help our engineers quickly debug and resolve the problem. Issues with the Chinese and Japanese version of HoloLens should be reported the same way.
|
||||
|
||||
>[!NOTE]
|
||||
>Be sure to accept the prompt that asks whether you’d like Feedback Hub to access your Documents folder (select **Yes** when prompted).
|
||||
> [!NOTE]
|
||||
> Be sure to accept the prompt that asks whether you’d like Feedback Hub to access your Documents folder (select **Yes** when prompted).
|
||||
|
||||
## Note for developers
|
||||
|
||||
|
||||
@ -27,15 +27,15 @@ Kiosk mode | Voice and Bloom commands | Quick actions menu | Camera and video |
|
||||
Single-app kiosk |  |  |  | 
|
||||
Multi-app kiosk |  |  with **Home** and **Volume** (default)<br><br>Photo and video buttons shown in Quick actions menu if the Camera app is enabled in the kiosk configuration.<br><br>Miracast is shown if the Camera app and device picker app are enabled in the kiosk configuration. |  if the Camera app is enabled in the kiosk configuration. |  if the Camera app and device picker app are enabled in the kiosk configuration.
|
||||
|
||||
>[!NOTE]
|
||||
>Use the Application User Model ID (AUMID) to allow apps in your kiosk configuration. The Camera app AUMID is `HoloCamera_cw5n1h2txyewy!HoloCamera`. The device picker app AUMID is `HoloDevicesFlow_cw5n1h2txyewy!HoloDevicesFlow`.
|
||||
> [!NOTE]
|
||||
> Use the Application User Model ID (AUMID) to allow apps in your kiosk configuration. The Camera app AUMID is `HoloCamera_cw5n1h2txyewy!HoloCamera`. The device picker app AUMID is `HoloDevicesFlow_cw5n1h2txyewy!HoloDevicesFlow`.
|
||||
|
||||
The [AssignedAccess Configuration Service Provider (CSP)](https://docs.microsoft.com/windows/client-management/mdm/assignedaccess-csp) enables kiosk configuration.
|
||||
|
||||
>[!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.
|
||||
> [!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.
|
||||
>
|
||||
>Be aware that voice commands are enabled for kiosk mode configured in Microsoft Intune or provisioning packages, even if the Cortana app is not selected as a kiosk app.
|
||||
> Be aware that voice commands are enabled for kiosk mode configured in Microsoft Intune or provisioning packages, 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:
|
||||
- You can use [Microsoft Intune or other mobile device management (MDM) service](#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803) to configure single-app and multi-app kiosks.
|
||||
@ -48,15 +48,15 @@ For HoloLens devices running Windows 10, version 1607, you can [use the Windows
|
||||
|
||||
If you use [MDM, Microsoft Intune](#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803), or a [provisioning package](#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803) to configure a multi-app kiosk, the procedure requires a Start layout. Start layout customization isn't supported in Holographic for Business, so you'll need to use a placeholder Start layout.
|
||||
|
||||
>[!NOTE]
|
||||
>Because a single-app kiosk launches the kiosk app when a user signs in, there is no Start screen displayed.
|
||||
> [!NOTE]
|
||||
> Because a single-app kiosk launches the kiosk app when a user signs in, there is no Start screen displayed.
|
||||
|
||||
### Start layout file for MDM (Intune and others)
|
||||
|
||||
Save the following sample as an XML file. You can use this file when you configure the multi-app kiosk in Microsoft Intune (or in another MDM service that provides a kiosk profile).
|
||||
|
||||
>[!NOTE]
|
||||
>If you need to use a custom setting and full XML configuration to set up a kiosk in your MDM service, use the [Start layout instructions for a provisioning package](#start-layout-for-a-provisioning-package).
|
||||
> [!NOTE]
|
||||
> If you need to use a custom setting and full XML configuration to set up a kiosk in your MDM service, use the [Start layout instructions for a provisioning package](#start-layout-for-a-provisioning-package).
|
||||
|
||||
```xml
|
||||
<LayoutModificationTemplate
|
||||
@ -181,22 +181,22 @@ Use the following snippet in your kiosk configuration XML to enable the **Guest*
|
||||
|
||||
1. [Set up the HoloLens to use the Windows Device Portal](https://developer.microsoft.com/windows/mixed-reality/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 for Business 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)
|
||||
> [!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 for Business 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/mixed-reality/Using_the_Windows_Device_Portal.html#connecting_over_wi-fi) or [USB](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#connecting_over_usb).
|
||||
|
||||
3. [Create a user name and password](https://developer.microsoft.com/windows/mixed-reality/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/mixed-reality/Using_the_Windows_Device_Portal.html#security_certificate).
|
||||
> [!TIP]
|
||||
> If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#security_certificate).
|
||||
|
||||
4. In the Windows Device Portal, click **Kiosk Mode**.
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>The kiosk mode option will be available if the device is [enrolled in device management](hololens-enroll-mdm.md) and has a [license to upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
> [!NOTE]
|
||||
> The kiosk mode option will be available if the device is [enrolled in device management](hololens-enroll-mdm.md) and has a [license to upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
|
||||
5. Select **Enable Kiosk Mode**, choose an app to run when the device starts, and click **Save**.
|
||||
|
||||
@ -210,4 +210,4 @@ Use the following snippet in your kiosk configuration XML to enable the **Guest*
|
||||
## More information
|
||||
|
||||
Watch how to configure a kiosk in a provisioning package.
|
||||
>[!VIDEO https://www.microsoft.com/videoplayer/embed/fa125d0f-77e4-4f64-b03e-d634a4926884?autoplay=false]
|
||||
> [!VIDEO https://www.microsoft.com/videoplayer/embed/fa125d0f-77e4-4f64-b03e-d634a4926884?autoplay=false]
|
||||
|
||||
@ -19,8 +19,8 @@ This is the current list of known issues for HoloLens that affect developers. Ch
|
||||
|
||||
## Unable to connect and deploy to HoloLens through Visual Studio
|
||||
|
||||
>[!NOTE]
|
||||
>Last Update: 8/8 @ 5:11PM - Visual Studio has released VS 2019 Version 16.2 which includes a fix to this issue. We recommend updating to this newest version to avoid experiencing this error.
|
||||
> [!NOTE]
|
||||
> Last Update: 8/8 @ 5:11PM - Visual Studio has released VS 2019 Version 16.2 which includes a fix to this issue. We recommend updating to this newest version to avoid experiencing this error.
|
||||
|
||||
Visual Studio has released VS 2019 Version 16.2 which includes a fix to this issue. We recommend updating to this newest version to avoid experiencing this error.
|
||||
|
||||
@ -36,14 +36,14 @@ Our team is currently working on a fix. In the meantime, you can use the followi
|
||||
1. Give the project a name (such as "HoloLensDeploymentFix") and make sure the Framework is set to at least .NET Framework 4.5, then Select **OK**.
|
||||
1. Right-click on the **References** node in Solution Explorer and add the following references (select to the **Browse** section and select **Browse**):
|
||||
|
||||
``` CMD
|
||||
```CMD
|
||||
C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\Microsoft.Tools.Deploy.dll
|
||||
C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\Microsoft.Tools.Connectivity.dll
|
||||
C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\SirepInterop.dll
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>If you don't have 10.0.18362.0 installed, use the most recent version that you have.
|
||||
> [!NOTE]
|
||||
> If you don't have 10.0.18362.0 installed, use the most recent version that you have.
|
||||
|
||||
1. Right-click on the project in Solution Explorer and select **Add** > **Existing Item**.
|
||||
1. Browse to C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86 and change the filter to **All Files (\*.\*)**.
|
||||
@ -51,14 +51,14 @@ Our team is currently working on a fix. In the meantime, you can use the followi
|
||||
1. Locate and select both files in Solution Explorer (they should be at the bottom of the list of files) and change **Copy to Output Directory** in the **Properties** window to **Copy always**.
|
||||
1. At the top of the file, add the following to the existing list of `using` statements:
|
||||
|
||||
``` CMD
|
||||
```CMD
|
||||
using Microsoft.Tools.Deploy;
|
||||
using System.Net;
|
||||
```
|
||||
|
||||
1. Inside of `static void Main(...)`, add the following code:
|
||||
|
||||
``` PowerShell
|
||||
```PowerShell
|
||||
RemoteDeployClient client = RemoteDeployClient.CreateRemoteDeployClient();
|
||||
client.Connect(new ConnectionOptions()
|
||||
{
|
||||
|
||||
@ -31,7 +31,7 @@ The HoloLens wizard helps you configure the following settings in a provisioning
|
||||
|
||||
- Upgrade to the enterprise edition
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
> This should only be used for HoloLens 1st Gen devices. Settings in a provisioning package will only be applied if the provisioning package includes an edition upgrade license to Windows Holographic for Business or if [the device has already been upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
|
||||
- Configure the HoloLens first experience (OOBE)
|
||||
@ -41,8 +41,8 @@ The HoloLens wizard helps you configure the following settings in a provisioning
|
||||
- Enable Developer Mode
|
||||
- Configure kiosk mode. (Detailed instructions for configuring kiosk mode can be found [here](hololens-kiosk.md#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803)).
|
||||
|
||||
>[!WARNING]
|
||||
>You must run Windows Configuration Designer on Windows 10 to configure Azure Active Directory enrollment using any of the wizards.
|
||||
> [!WARNING]
|
||||
> You must run Windows Configuration Designer on Windows 10 to configure Azure Active Directory enrollment using any of the wizards.
|
||||
|
||||
Provisioning packages can include management instructions and policies, customization of network connections and policies, and more.
|
||||
|
||||
@ -88,8 +88,8 @@ After you're done, click **Create**. It only takes a few seconds. When the packa
|
||||
|
||||
### 3. Create a provisioning package for HoloLens using advanced provisioning
|
||||
|
||||
>[!NOTE]
|
||||
>Settings in a provisioning package will only be applied if the provisioning package includes an edition upgrade license to Windows Holographic for Business or if [the device has already been upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
> [!NOTE]
|
||||
> Settings in a provisioning package will only be applied if the provisioning package includes an edition upgrade license to Windows Holographic for Business or if [the device has already been upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
|
||||
1. On the Windows Configuration Designer 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.
|
||||
@ -102,15 +102,15 @@ After you're done, click **Create**. It only takes a few seconds. When the packa
|
||||
|
||||
7. Expand **Runtime settings** and customize the package with any of the settings [described below](#what-you-can-configure).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>(For Windows 10, version 1607 only) 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/mixed-reality/reset_or_recover_your_hololens#perform_a_full_device_recovery).
|
||||
> [!IMPORTANT]
|
||||
> (For Windows 10, version 1607 only) 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/mixed-reality/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.
|
||||
> [!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**.
|
||||
|
||||
@ -118,13 +118,13 @@ After you're done, click **Create**. It only takes a few seconds. When the packa
|
||||
|
||||
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.
|
||||
> [!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**.
|
||||
|
||||
>[!WARNING]
|
||||
>If you encrypt the provisioning package, provisioning the HoloLens device will fail.
|
||||
> [!WARNING]
|
||||
> If you encrypt the provisioning package, provisioning the HoloLens device will fail.
|
||||
|
||||
7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows Configuration Designer uses the project folder as the output location.
|
||||
|
||||
@ -154,13 +154,13 @@ After you're done, click **Create**. It only takes a few seconds. When the packa
|
||||
|
||||
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 a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.
|
||||
> [!NOTE]
|
||||
> If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.
|
||||
|
||||
### 4. Apply a provisioning package to HoloLens after setup
|
||||
|
||||
>[!NOTE]
|
||||
>Windows 10, version 1809 only
|
||||
> [!NOTE]
|
||||
> Windows 10, version 1809 only
|
||||
|
||||
On your PC:
|
||||
1. Create a provisioning package as described at [Create a provisioning package for HoloLens using the HoloLens wizard](hololens-provisioning.md).
|
||||
@ -189,7 +189,7 @@ In Windows Configuration Designer, when you create a provisioning package for Wi
|
||||
| **EditionUpgrade** | [Upgrade to Windows Holographic for Business.](hololens1-upgrade-enterprise.md) |
|
||||
| **Policies** | Allow or prevent developer mode on HoloLens. [Policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies) |
|
||||
|
||||
>[!NOTE]
|
||||
>App installation (**UniversalAppInstall**) using a provisioning package is not currently supported for HoloLens.
|
||||
> [!NOTE]
|
||||
> App installation (**UniversalAppInstall**) using a provisioning package is not currently supported for HoloLens.
|
||||
|
||||
## Next Step: [Enroll your device](hololens-enroll-mdm.md)
|
||||
|
||||
@ -74,8 +74,8 @@ If you’re still having problems, press the power button for 4 seconds, until a
|
||||
|
||||
## Reset to factory settings
|
||||
|
||||
>[!NOTE]
|
||||
>The battery needs at least 40 percent charge to reset.
|
||||
> [!NOTE]
|
||||
> The battery needs at least 40 percent charge to reset.
|
||||
|
||||
If your HoloLens is still experiencing issues after restarting, try resetting it to factory state. Resetting your HoloLens keeps the version of the Windows Holographic software that’s installed on it and returns everything else to factory settings.
|
||||
|
||||
@ -106,8 +106,8 @@ The Advanced Recovery Companion is a new app in Microsoft Store restore the oper
|
||||
5. On the **Device info** page, select **Install software** to install the default package. (If you have a Full Flash Update (FFU) image that you want to install instead, select **Manual package selection**.)
|
||||
6. Software installation will begin. Do not use the device or disconnect the cable during installation. When you see the **Installation finished** page, you can disconnect and use your device.
|
||||
|
||||
>[!TIP]
|
||||
>In the event that a HoloLens 2 gets into a state where Advanced Recovery Companion cannot recognize the device, and it does not boot, try forcing the device into Flashing Mode and recovering it with Advanced Recovery Companion:
|
||||
> [!TIP]
|
||||
> In the event that a HoloLens 2 gets into a state where Advanced Recovery Companion cannot recognize the device, and it does not boot, try forcing the device into Flashing Mode and recovering it with Advanced Recovery Companion:
|
||||
|
||||
1. Connect the HoloLens 2 to a PC with Advanced Recovery Companion installed.
|
||||
1. Press and hold the **Volume Up and Power buttons** until the device reboots. Release the Power button, but continue to hold the Volume Up button until the third LED is lit.
|
||||
|
||||
@ -69,8 +69,8 @@ To go back to a previous version of HoloLens (1st gen), follow these steps:
|
||||
|
||||
# Use policies to manage updates to HoloLens
|
||||
|
||||
>[!NOTE]
|
||||
>HoloLens (1st gen) devices must be [upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md) to manage updates.
|
||||
> [!NOTE]
|
||||
> HoloLens (1st gen) devices must be [upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md) to manage updates.
|
||||
|
||||
To configure how and when updates are applied, use the following policies:
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user