mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
fixing more warnings and conflicts
This commit is contained in:
Greg Lindsay
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Frequently asked questions about HoloLens and holograms
|
||||
title: Frequently asked questions about HoloLens devices and holograms
|
||||
description: Do you have a quick question about HoloLens or interacting with holograms? This article provides a quick answer and more resources.
|
||||
keywords: hololens, faq, known issue, help
|
||||
ms.prod: hololens
|
||||
@ -9,129 +9,134 @@ ms.author: v-tea
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/30/2019
|
||||
ms.date: 02/27/2020
|
||||
ms.reviewer:
|
||||
ms.custom:
|
||||
- CI 114606
|
||||
- CSSTroubleshooting
|
||||
manager: jarrettr
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# HoloLens and holograms: Frequently asked questions
|
||||
# Frequently asked questions about HoloLens devices and holograms
|
||||
|
||||
Here are some answers to questions you might have about using HoloLens, placing holograms, working with spaces, and more.
|
||||
This article answers some questions that you may have about how to use HoloLens, including how to place holograms, work with spaces, and more.
|
||||
|
||||
Any time you're having problems, make sure HoloLens is [charged up](https://support.microsoft.com/help/12627/hololens-charge-your-hololens). Try [restarting it](hololens-restart-recover.md) to see if that fixes things. And please use the Feedback app to send us info about the issue—you'll find it on the [**Start** menu](holographic-home.md).
|
||||
Any time that you have problems, make sure that HoloLens is [charged up](https://support.microsoft.com/help/12627/hololens-charge-your-hololens). Try [restarting it](hololens-restart-recover.md) to see whether that fixes things. And please use the Feedback app to send us information about the issue. You'll find the Feedback app on the [**Start** menu](holographic-home.md).
|
||||
|
||||
For tips about wearing your HoloLens, see [HoloLens fit and comfort: FAQ](https://support.microsoft.com/help/13405/hololens-fit-and-comfort-faq).
|
||||
For tips about hwo to wear your HoloLens, see [HoloLens (1st gen) fit and comfort frequently asked questions](hololens1-fit-comfort-faq.md).
|
||||
|
||||
This FAQ addresses the following questions and issues:
|
||||
This article addresses the following questions and issues:
|
||||
<a id="list"></a>
|
||||
|
||||
- [My holograms don't look right or are moving around](#my-holograms-dont-look-right-or-are-moving-around)
|
||||
- [I see a message that says "Finding your space"](#i-see-a-message-that-says-finding-your-space)
|
||||
- [I'm not seeing the holograms I expect to see in my space](#im-not-seeing-the-holograms-i-expect-to-see-in-my-space)
|
||||
- [I can't place holograms where I want](#i-cant-place-holograms-where-i-want)
|
||||
- [I'm not seeing the holograms that I expect to see in my space](#im-not-seeing-the-holograms-that-i-expect-to-see-in-my-space)
|
||||
- [I can't place holograms where I want to](#i-cant-place-holograms-where-i-want-to)
|
||||
- [Holograms disappear or are encased in other holograms or objects](#holograms-disappear-or-are-encased-in-other-holograms-or-objects)
|
||||
- [I can see holograms that are on the other side of a wall](#i-can-see-holograms-that-are-on-the-other-side-of-a-wall)
|
||||
- [When I place a hologram on a wall, it seems to float](#when-i-place-a-hologram-on-a-wall-it-seems-to-float)
|
||||
- [When I place a hologram on a wall, the hologram seems to float](#when-i-place-a-hologram-on-a-wall-the-hologram-seems-to-float)
|
||||
- [Apps appear too close to me when I'm trying to move them](#apps-appear-too-close-to-me-when-im-trying-to-move-them)
|
||||
- [I'm getting a low disk space error](#im-getting-a-low-disk-space-error)
|
||||
- [HoloLens doesn't respond to my gestures](#hololens-doesnt-respond-to-my-gestures)
|
||||
- [HoloLens doesn't respond to my voice](#hololens-doesnt-respond-to-my-voice)
|
||||
- [I'm having problems pairing or using a Bluetooth device](#im-having-problems-pairing-or-using-a-bluetooth-device)
|
||||
- [I'm having problems with the HoloLens clicker](#im-having-problems-with-the-hololens-clicker)
|
||||
- [HoloLens Settings lists devices as available, but the devices don’t work](#hololens-settings-lists-devices-as-available-but-the-devices-dont-work)
|
||||
- [I'm having problems using the HoloLens clicker](#im-having-problems-using-the-hololens-clicker)
|
||||
- [I can't connect to Wi-Fi](#i-cant-connect-to-wi-fi)
|
||||
- [My HoloLens isn't running well, is unresponsive, or won't start](#my-hololens-isnt-running-well-is-unresponsive-or-wont-start)
|
||||
- [HoloLens Management Questions](#hololens-management-questions)
|
||||
- [I can't sign in to a HoloLens device because it was previously set up for someone else](#i-cant-sign-in-to-a-hololens-device-because-it-was-previously-set-up-for-someone-else)
|
||||
- [Questions about managing HoloLens devices](#questions-about-managing-hololens-devices)
|
||||
- [Questions about securing HoloLens devices](#questions-about-securing-hololens-devices)
|
||||
- [How do I delete all spaces?](#how-do-i-delete-all-spaces)
|
||||
- [I cannot find or use the keyboard to type in the HoloLens 2 Emulator](#i-cannot-find-or-use-the-keyboard-to-type-in-the-hololens-2-emulator)
|
||||
- [I can't log in to a HoloLens because it was previously set up for someone else](#i-cant-log-in-to-a-hololens-because-it-was-previously-set-up-for-someone-else)
|
||||
|
||||
## My holograms don't look right or are moving around
|
||||
|
||||
If your holograms don't look right (for example, they're jittery or shaky, or you see black patches on top of them), try one of these fixes:
|
||||
|
||||
- [Clean your device visor](hololens1-hardware.md#care-and-cleaning) and make sure nothing is blocking the sensors.
|
||||
- Make sure you're in a well-lit room without a lot of direct sunlight.
|
||||
- Try walking around and gazing at your surroundings so HoloLens can scan them more completely.
|
||||
- Make sure that you're in a well-lit room that does not have a lot of direct sunlight.
|
||||
- Try walking around and gazing at your surroundings so that HoloLens can scan them more completely.
|
||||
- If you've placed a lot of holograms, try removing some.
|
||||
|
||||
If you're still having problems, trying running the Calibration app, which calibrates your HoloLens just for you, to help keep your holograms looking their best. Go to **Settings **>** System **>** Utilities**. Under Calibration, select **Open Calibration**.
|
||||
If you're still having problems, trying running the Calibration app. This app calibrates your HoloLens just for you to help keep your holograms looking their best. To do this, go to **Settings** > **System** > **Utilities**. Under **Calibration**, select **Open Calibration**.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I see a message that says Finding your space
|
||||
## I see a message that says "Finding your space"
|
||||
|
||||
When HoloLens is learning or loading a space, you might see a brief message that says "Finding your space." If this message continues for more than a few seconds, you'll see another message under the Start menu that says "Still looking for your space."
|
||||
When HoloLens is learning or loading a space, you may see a brief message that says "Finding your space." If this message displays for more than a few seconds, you'll see another message under the Start menu that says "Still looking for your space."
|
||||
|
||||
These messages mean that HoloLens is having trouble mapping your space. When this happens, you'll be able to open apps, but you won't be able to place holograms in your environment.
|
||||
These messages mean that HoloLens is having trouble mapping your space. When this happens, you can open apps, but you can't place holograms in your environment.
|
||||
|
||||
If you see these messages often, try the following:
|
||||
If you see these messages often, try one or more of the following fixes:
|
||||
|
||||
- Make sure you're in a well-lit room without a lot of direct sunlight.
|
||||
- Make sure your device visor is clean. [Learn how](hololens1-hardware.md#care-and-cleaning).
|
||||
- Make sure you have a strong Wi-Fi signal. If you enter a new environment that has no Wi-Fi or a weak signal, HoloLens won't be able find your space. Check your Wi-Fi connection by going to **Settings **> **Network & Internet** >** Wi-Fi**.
|
||||
- Make sure that you're in a well-lit room that does not have a lot of direct sunlight.
|
||||
- Make sure that your device visor is clean. [Learn how to clean your visor](hololens1-hardware.md#care-and-cleaning).
|
||||
- Make sure that you have a strong Wi-Fi signal. If you enter a new environment that has no Wi-Fi or a weak Wi-Fi signal, HoloLens won't be able find your space. Check your Wi-Fi connection by going to **Settings** > **Network & Internet** > **Wi-Fi**.
|
||||
- Try moving more slowly.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I'm not seeing the holograms I expect to see in my space
|
||||
## I'm not seeing the holograms that I expect to see in my space
|
||||
|
||||
If you don't see holograms you placed, or you're seeing some you don't expect, try the following:
|
||||
If you don't see the holograms that you placed, or if you're seeing some that you don't expect, try one or more of the following fixes:
|
||||
|
||||
- Try turning on some lights. HoloLens works best in a well-lit space.
|
||||
- Remove holograms you don't need by going to **Settings** > **System** > **Holograms** > **Remove nearby holograms**. Or, if needed, select **Remove all holograms**.
|
||||
- Turn on some lights. HoloLens works best in a well-lit space.
|
||||
- Remove holograms that you don't need by going to **Settings** > **System** > **Holograms** > **Remove nearby holograms**. Or, if needed, select **Remove all holograms**.
|
||||
|
||||
> [!NOTE]
|
||||
> If the layout or lighting in your space changes significantly, your device might have trouble identifying your space and showing your holograms.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I can't place holograms where I want
|
||||
## I can't place holograms where I want to
|
||||
|
||||
Here are some things to try if you're having trouble placing holograms:
|
||||
|
||||
- Stand about 1 to 3 meters from where you're trying to place the hologram.
|
||||
- Stand between one and three meters from where you're trying to place the hologram.
|
||||
- Don't place holograms on black or reflective surfaces.
|
||||
- Make sure you're in a well-lit room without a lot of direct sunlight.
|
||||
- Make sure that you're in a well-lit room that does not have a lot of direct sunlight.
|
||||
- Walk around the rooms so HoloLens can rescan your surroundings. To see what's already been scanned, air tap to reveal the mapping mesh graphic.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## Holograms disappear or are encased in other holograms or objects
|
||||
|
||||
If you get too close to a hologram, it will temporarily disappear—just move away from it. Also, if you've placed a lot of holograms close together, some may disappear. Try removing a few.
|
||||
If you get too close to a hologram, it will temporarily disappear—to restore the hologram, just move away from it. Also, if you've placed several holograms close together, some may disappear. Try removing a few.
|
||||
|
||||
Holograms can also be blocked or encased by other holograms or by objects such as walls. If this happens, try one of the following:
|
||||
Holograms can also be blocked or encased by other holograms or by objects such as walls. If this happens, try one of the following fixes:
|
||||
|
||||
- If the hologram is encased in another hologram, move it to another location: select **Adjust**, then tap and hold to position it.
|
||||
- If the hologram is encased in another hologram, move the encased hologram to another location. To do this, select **Adjust**, then tap and hold to position it.
|
||||
- If the hologram is encased in a wall, select **Adjust**, then walk toward the wall until the hologram appears. Tap and hold, then pull the hologram forward and out of the wall.
|
||||
- If you can't move the hologram with gestures, use your voice to remove it. Gaze at the hologram, then say "Remove." Then reopen it and place it in a new location.
|
||||
- If you can't move the hologram by using gestures, use your voice to remove it. Gaze at the hologram, then say "Remove." Then reopen the hologram and place it in a new location.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I can see holograms that are on the other side of a wall
|
||||
|
||||
If you're very close to a wall, or if HoloLens hasn't scanned the wall yet, you'll be able to see holograms that are in the next room. Stand 1 to 3 meters from the wall and gaze to scan it.
|
||||
If you're very close to a wall, or if HoloLens hasn't scanned the wall yet, you can see holograms that are in the next room. To scan the wall, stand between one and three meters from the wall and gaze at it.
|
||||
|
||||
If HoloLens has problems scanning the wall, it might be because there's a black or reflective object nearby (for example, a black couch or a stainless steel refrigerator). If there is, scan the other side of the wall.
|
||||
A black or reflective object (for example, a black couch or a stainless steel refrigerator) near the wall may cause problems when HoloLens tries to scan the wall. If there is such an object, scan the other side of the wall.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## When I place a hologram on a wall, it seems to float
|
||||
## When I place a hologram on a wall, the hologram seems to float
|
||||
|
||||
Holograms placed on walls will appear to be an inch or so away from the wall. If they appear farther away, try the following:
|
||||
A hologram that you place on a wall typically appears to be an inch or so away from the wall. If it appears to be farther away, try one or more of the following fixes:
|
||||
|
||||
- Stand 1 to 3 meters from the wall when you place a hologram and face the wall straight on.
|
||||
- Air tap the wall to reveal the mapping mesh graphic. Make sure the mesh is lined up with the wall. If it isn't, remove the hologram, rescan the wall, and try again.
|
||||
- When you place a hologram on a wall, stand between one and three meters from the wall and face the wall straight on.
|
||||
- Air tap the wall to reveal the mapping mesh graphic. Make sure that the mesh aligns with the wall. If it doesn't, remove the hologram, rescan the wall, and then try again.
|
||||
- If the issue persists, run the Calibration app. You'll find it in **Settings** > **System** > **Utilities**.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## Apps appear too close to me when I'm trying to move them
|
||||
|
||||
Try walking around and looking at the area where you're placing the app so HoloLens will scan it from different angles. [Cleaning your device visor](hololens1-hardware.md#care-and-cleaning) may also help.
|
||||
Try walking around and looking at the area where you're placing the app so that HoloLens scans the area from different angles. [Cleaning your device visor](hololens1-hardware.md#care-and-cleaning) may also help.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
@ -139,21 +144,36 @@ Try walking around and looking at the area where you're placing the app so HoloL
|
||||
|
||||
Free up some storage space by doing one or more of the following:
|
||||
|
||||
- Remove some of the holograms you've placed, or remove some saved data from within apps. [How do I find my data?](holographic-data.md)
|
||||
- Remove some of the holograms that you've placed, or remove some saved data from within apps. [How do I find my data?](holographic-data.md)
|
||||
- Delete some pictures and videos in the Photos app.
|
||||
- Uninstall some apps from your HoloLens. In the All apps list, tap and hold the app you want to uninstall, then select **Uninstall**. (This will also delete any of the app's data stored on the device.)
|
||||
- Uninstall some apps from your HoloLens. In the **All apps** list, tap and hold the app you want to uninstall, then select **Uninstall**. (Uninstalling the app also deletes any data that the app stores on the device.)
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## HoloLens doesn't respond to my gestures
|
||||
|
||||
To make sure HoloLens can see your gestures, keep your hand in the gesture frame, which extends a couple of feet on either side of you. HoloLens can also best see your hand when you hold it about 18 inches in front of your body (though you don't have to be precise about this). When HoloLens can see your hand, the cursor will change from a dot to a ring. Learn more about [using gestures in HoloLens 2](hololens2-basic-usage.md) or [using gestures in HoloLens (1st gen)](hololens1-basic-usage.md).
|
||||
To make sure that HoloLens can see your gestures, keep your hand in the gesture frame. The gesture frame extends a couple of feet on either side of you. HoloLens can also best see your hand when you hold it about 18 inches in front of your body (though you don't have to be precise about this). When HoloLens can see your hand, the cursor changes from a dot to a ring. Learn more about [using gestures in HoloLens 2](hololens2-basic-usage.md) or [using gestures in HoloLens (1st gen)](hololens1-basic-usage.md).
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## HoloLens doesn't respond to my voice
|
||||
|
||||
If Cortana isn't responding to your voice, make sure Cortana is on. In the **All apps** list, select **Cortana** > **Menu** > **Notebook** > **Settings** to make changes. To learn more about what you can say, see [Use your voice with HoloLens](hololens-cortana.md).
|
||||
HoloLens (1st gen) and HoloLens 2 have built-in speech recognition, and also support Cortana (online speech recognition).
|
||||
|
||||
### Built-in voice commands do not work
|
||||
|
||||
On HoloLens (1st gen), built-in speech recognition is not configurable. It is always turned on. On HoloLens 2, you can choose whether to turn on both speech recognition and Cortana during device setup.
|
||||
|
||||
If your HoloLens 2 is not responding to your voice, make sure Speech recognition is turned on. Go to **Start** > **Settings** > **Privacy** > **Speech** and turn on **Speech recognition**.
|
||||
|
||||
### Cortana doesn't work
|
||||
|
||||
If Cortana isn't responding to your voice, make sure Cortana is turned on. Go to **Start** > **Settings** > **Privacy** > **Speech** and verify the **Online speech recognition** settings. Then do one of the following to verify that Cortana itself is turned on:
|
||||
|
||||
- In **All apps**, select **Cortana** > select **Menu** > **Notebook** > **Settings** to make changes.
|
||||
- On HoloLens 2, select the **Speech settings** button or say "Speech settings."
|
||||
|
||||
To learn more about what you can say, see [Use your voice with HoloLens](hololens-cortana.md).
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
@ -161,42 +181,46 @@ If Cortana isn't responding to your voice, make sure Cortana is on. In the **All
|
||||
|
||||
If you're having problems [pairing a Bluetooth device](hololens-connect-devices.md), try the following:
|
||||
|
||||
- Go to **Settings** > **Devices** and make sure Bluetooth is turned on. If it is, try turning if off and on again.
|
||||
- Make sure your Bluetooth device is fully charged or has fresh batteries.
|
||||
- If you still can't connect, [restart your HoloLens](hololens-recovery.md).
|
||||
|
||||
If you're having trouble using a Bluetooth device, make sure it's a supported device. Supported devices include:
|
||||
|
||||
- English-language QWERTY Bluetooth keyboards, which can be used anywhere you use the holographic keyboard.
|
||||
- Bluetooth mice.
|
||||
- The [HoloLens clicker](hololens1-clicker.md).
|
||||
|
||||
Other Bluetooth HID and GATT devices can be paired, but they might require a companion app from Microsoft Store to work with HoloLens.
|
||||
|
||||
HoloLens doesn't support Bluetooth audio profiles. Bluetooth audio devices, such as speakers and headsets, may appear as available in HoloLens settings, but they aren't supported.
|
||||
- Go to **Settings** > **Devices**, and make sure that Bluetooth is turned on. If it is, turn it off and on again.
|
||||
- Make sure that your Bluetooth device is fully charged or has fresh batteries.
|
||||
- If you still can't connect, [restart the HoloLens](hololens-recovery.md).
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I'm having problems with the HoloLens clicker
|
||||
## HoloLens Settings lists devices as available, but the devices don’t work
|
||||
|
||||
Use the [clicker](hololens1-clicker.md) to select, scroll, move, and resize holograms. Additional clicker gestures may vary from app to app.
|
||||
HoloLens doesn't support Bluetooth audio profiles. Bluetooth audio devices, such as speakers and headsets, may appear as available in HoloLens settings, but they aren't supported.
|
||||
|
||||
If you're having trouble using the clicker, make sure its charged and paired with your HoloLens. If the battery is low, the indicator light will blink amber. To see if its paired, go to **Settings** > **Devices** and see if it shows up there. [Pair the clicker](hololens-connect-devices.md#pair-the-clicker).
|
||||
If you're having trouble using a Bluetooth device, make sure that it's a supported device. Supported devices include the following:
|
||||
|
||||
- English-language QWERTY Bluetooth keyboards (you can use these anywhere that you use the holographic keyboard).
|
||||
- Bluetooth mice.
|
||||
- The [HoloLens clicker](hololens1-clicker.md).
|
||||
|
||||
You can pair other Bluetooth HID and GATT devices together with your HoloLens. However, you may have to install corresponding companion apps from Microsoft Store to actually use the devices.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I'm having problems using the HoloLens clicker
|
||||
|
||||
Use the [clicker](hololens1-clicker.md) to select, scroll, move, and resize holograms. Individial apps may support additional clicker gestures.
|
||||
|
||||
If you're having trouble using the clicker, make sure that it's charged and paired with your HoloLens. If the battery is low, the indicator light blinks amber. To verify that the clicker is paired, go to **Settings** > **Devices** and see if it shows up there. For more information, see [Pair the clicker](hololens-connect-devices.md#pair-the-clicker).
|
||||
|
||||
If the clicker is charged and paired and you're still having problems, reset it by holding down the main button and the pairing button for 15 seconds. Then pair the clicker with your HoloLens again.
|
||||
|
||||
If that doesn't help, see [Restart or recover the HoloLens clicker](hololens1-clicker.md#restart-or-recover-the-clicker).
|
||||
If resetting the clicker doesn't help, see [Restart or recover the HoloLens clicker](hololens1-clicker.md#restart-or-recover-the-clicker).
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I can't connect to Wi-Fi
|
||||
|
||||
Here are some things to try if you can't connect to Wi-Fi on HoloLens:
|
||||
Here are some things to try if you can't connect your HoloLens to a Wi-Fi network:
|
||||
|
||||
- Make sure Wi-Fi is turned on. Bloom to go to Start, then select **Settings** > **Network & Internet** > **Wi-Fi** to check. If Wi-Fi is on, try turning it off and on again.
|
||||
- Make sure that Wi-Fi is turned on. To check, use the Start gesture, then select **Settings** > **Network & Internet** > **Wi-Fi**. If Wi-Fi is on, try turning it off and then on again.
|
||||
- Move closer to the router or access point.
|
||||
- Restart your Wi-Fi router, then [restart HoloLens](hololens-recovery.md). Try connecting again.
|
||||
- If none of these things work, check to make sure your router is using the latest firmware. You can find this information on the manufacturers website.
|
||||
- If none of these things work, check to make sure that your router is using the latest firmware. You can find this information on the manufacturer website.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
@ -206,29 +230,53 @@ If your device isn't performing properly, see [Restart, reset, or recover HoloLe
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I can't sign in to a HoloLens device because it was previously set up for someone else
|
||||
|
||||
## I can't log in to a HoloLens because it was previously set up for someone else
|
||||
If your device was previously set up for someone else, either for a client or for a former employee, and you don't have their password to unlock the device, you can do one of the following:
|
||||
|
||||
If your device was previously set up for someone else, either a client or former employee and you don't have their password to unlock the device there are two solutions.
|
||||
- If your device is MDM managed by Intune then you can remotely [Wipe](https://docs.microsoft.com/intune/remote-actions/devices-wipe) the device and it'll reflash itself. Make sure to leave **Retain enrollment state and user account** unchecked.
|
||||
- If you have the device with you then you can put the device into **Flashing Mode** and use Advanced Recovery Companion to [recover](https://docs.microsoft.com/hololens/hololens-recovery) the device.
|
||||
- For a device that is enrolled in Intune mobile device management (MDM), you can use Intune to remotely [wipe](https://docs.microsoft.com/intune/remote-actions/devices-wipe) the device. The device then re-flashes itself.
|
||||
> [!IMPORTANT]
|
||||
> When you wipe the device, make sure to leave **Retain enrollment state and user account** unchecked.
|
||||
- For a non-MDM device, you can [put the device into **Flashing Mode** and use Advanced Recovery Companion](hololens-recovery.md#re-install-the-operating-system) to recover the device.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## HoloLens Management Questions
|
||||
## Questions about managing HoloLens devices
|
||||
|
||||
1. **Can I use SCCM to manage the HoloLens?**
|
||||
1. No. An MDM must be used to manage the HoloLens
|
||||
1. **Can I use Active Directory to manage HoloLens user accounts?**
|
||||
1. No, Azure AD must be used to manage user accounts.
|
||||
1. **Is the HoloLens capable of ADCS auto enrollment?**
|
||||
1. No
|
||||
1. **Can the HoloLens participate in WNA/IWA?**
|
||||
1. No
|
||||
1. **Does the HoloLens support branding?**
|
||||
1. No. However, one work around is to create a custom app and enable Kiosk mode. The custom app can have branding which can then launch other apps (such as Remote Assist). Another option is to change all of the users profile pictures in AAD to your company logo. (However, this may not be desirable for all scenarios)
|
||||
1. **What logging capabilities are available on HL1 and HL2?**
|
||||
1. Logging is limited to traces captured in developer/troubleshooting scenarios or telemetry sent to Microsoft servers.
|
||||
### Can I use System Center Configuration Manager (SCCM) to manage HoloLens devices?
|
||||
|
||||
No. You have to use an MDM system to manage HoloLens devices.
|
||||
|
||||
### Can I use Active Directory Domain Services (AD DS) to manage HoloLens user accounts?
|
||||
|
||||
No. You have to use Azure Active Directory (AAD) to manage user accounts for HoloLens devices.
|
||||
|
||||
### Is HoloLens capable of Automated Data Capture Systems (ADCS) auto-enrollment?
|
||||
|
||||
No.
|
||||
|
||||
### Can HoloLens participate in WNA or Integrated Windows Authentication?
|
||||
|
||||
No.
|
||||
|
||||
### Does HoloLens support branding?
|
||||
|
||||
No. However, you can work around this issue by using one of the following approaches:
|
||||
|
||||
- Create a custom app, and then [enable Kiosk mode](hololens-kiosk.md). The custom app can have branding, and can launch other apps (such as Remote Assist).
|
||||
- Change all of the user profile pictures in AAD to your company logo. However, this may not be desirable for all scenarios.
|
||||
|
||||
### What logging capabilities do HoloLens (1st gen) and HoloLens 2 offer?
|
||||
|
||||
Logging is limited to traces that can be captured in development or troubleshooting scenarios, or telemetry that the devices send to Microsoft servers.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## Questions about securing HoloLens devices
|
||||
|
||||
See [frequently asked questions about securing HoloLens devices](hololens-faq-security.md).
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## How do I delete all spaces?
|
||||
|
||||
@ -241,4 +289,3 @@ If your device was previously set up for someone else, either a client or former
|
||||
*Coming soon*
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
|
||||
@ -65,8 +65,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.
|
||||
> [!NOTE]
|
||||
> This step is only necessary if your company plans on managing the HoloLens.
|
||||
|
||||
1. Ensure that you have an Azure AD License.
|
||||
Please [HoloLens Licenses Requirements](hololens-licenses-requirements.md) for additional information.
|
||||
@ -100,8 +100,9 @@ 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 to manage the HoloLens.
|
||||
> [!NOTE]
|
||||
> This step is only necessary if your company plans to manage the HoloLens.
|
||||
|
||||
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. A list of CSPs for HoloLens can be found [here](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices).
|
||||
@ -151,8 +152,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).
|
||||
|
||||
@ -163,6 +164,8 @@ Directions for upgrading to the commercial suite can be found [here](https://doc
|
||||
1. Check your app settings
|
||||
1. Log into your Microsoft Store Business account
|
||||
1. **Manage > Products and Services > Apps and Software > Select the app you want to sync > Private Store Availability > Select “Everyone” or “Specific Groups”**
|
||||
>[!NOTE]
|
||||
>If you don't see the app you want, you will have to "get" the app by searching the store for your app. **Click the "Search" bar in the upper right-hand corner > type in the name of the app > click on the app > select "Get"**.
|
||||
1. If you do not see your apps in **Intune > Client Apps > Apps** , you may have to [sync your apps](https://docs.microsoft.com/intune/apps/windows-store-for-business#synchronize-apps) again.
|
||||
|
||||
1. [Create a device profile for Kiosk mode](https://docs.microsoft.com/intune/configuration/kiosk-settings#create-the-profile)
|
||||
|
||||
@ -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
|
||||
|
||||
|
||||
@ -45,8 +45,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
|
||||
|
||||
@ -61,7 +61,7 @@ Here's a quick summary of what's new:
|
||||
- Support for FIDO2 Security Keys to enable secure and easy authentication for shared devices
|
||||
- Seamlessly apply a provisioning package from a USB drive to your HoloLens
|
||||
- Use a provisioning packages to enroll your HoloLens to your Mobile Device Management system
|
||||
- Use Windows AutoPilot to set up and pre-configure new devices, quickly getting them ready for productive use. Send a note to hlappreview@service.microsoft.com to join the preview.
|
||||
- Use Windows AutoPilot to set up and pre-configure new devices, quickly getting them ready for productive use. Send a note to hlappreview@microsoft.com to join the preview.
|
||||
- Dark Mode - many Windows apps support both dark and light modes, and now HoloLens customers can choose the default mode for apps that support both color schemes! Based on customer feedback, with this update we are setting the default app mode to "dark," but you can easily change this setting at any time. Navigate to Settings > System > Colors to find "Choose your default app mode."
|
||||
- Support for additional system voice commands
|
||||
- Hand Tracking improvements to reduce the tendency to close the index finger when pointing. This should make button pressing and 2D slate usage feel more accurate
|
||||
|
||||
@ -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()
|
||||
{
|
||||
|
||||
@ -54,6 +54,12 @@ You can also confirm you are connected to a Wi-Fi network by checking the Wi-Fi
|
||||
1. Open the **Start** menu.
|
||||
1. Look at the top left of the **Start** menu for Wi-Fi status. The state of Wi-Fi and the SSID of the connected network will be shown.
|
||||
|
||||
## Troubleshooting your connection to Wi-Fi
|
||||
|
||||
If you experience problems connecting to Wi-Fi, see [I can't connect to Wi-Fi](./hololens-faq.md#i-cant-connect-to-wi-fi).
|
||||
|
||||
When you sign into an enterprise or organizational account on the device, it may also apply Mobile Device Management (MDM) policy, if the policy is configured by your IT administrator.
|
||||
|
||||
## Disabling Wi-Fi on HoloLens (1st gen)
|
||||
|
||||
### Using the Settings app on HoloLens
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -33,6 +33,14 @@ This document also assumes that the HoloLens has been evaluated by security team
|
||||
|
||||
Before deploying the HoloLens in your environment, it is important to first determine what features, apps, and type of identities are needed. It is also important to ensure that your security team has approved of the use of the HoloLens on the company's network. Please see [Frequently ask security questions](hololens-faq-security.md) for additional security information.
|
||||
|
||||
### Type of identity
|
||||
|
||||
Determine the type of identity that will be used to sign into the device.
|
||||
|
||||
1. **Local Accounts:** This account is local to the device (like a local admin account on a windows PC). This will allow only 1 user to log into the device.
|
||||
2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device.
|
||||
3. **Azure Active Directory (Azure AD) accounts:** This is an account created in Azure AD. This grants your corporation the ability to manage the HoloLens device. This will allow multiple users to log into the HoloLens 1st Gen Commercial Suite/the HoloLens 2 device.
|
||||
|
||||
### Type of Features
|
||||
|
||||
Your feature requirements will determine which HoloLens you need. One popular feature that we see deployed in customer environments frequently is Kiosk Mode. A list of HoloLens key features, and the editions of HoloLens that support them, can be found [here](hololens-commercial-features.md).
|
||||
@ -66,18 +74,10 @@ The majority of the steps found in this document will also apply to the followin
|
||||
2. Guides
|
||||
3. Customer Apps
|
||||
|
||||
### Type of identity
|
||||
|
||||
Determine the type of identity that will be used to sign into the device.
|
||||
|
||||
1. **Local Accounts:** This account is local to the device (like a local admin account on a windows PC). This will allow only 1 user to log into the device.
|
||||
2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device.
|
||||
3. **Azure Active Directory (Azure AD) accounts:** This is an account created in Azure AD. This grants your corporation the ability to manage the HoloLens device. This will allow multiple users to log into the HoloLens 1st Gen Commercial Suite/the HoloLens 2 device.
|
||||
|
||||
### Determine your enrollment method
|
||||
|
||||
1. Bulk enrollment with a security token in a provisioning package.
|
||||
Pros: this is the most automated approach
|
||||
Pros: this is the most automated approach\
|
||||
Cons: takes initial server-side setup
|
||||
1. Auto-enroll on user sign in.
|
||||
Pros: easiest approach
|
||||
|
||||
@ -67,10 +67,10 @@ To go back to a previous version of HoloLens (1st gen), follow these steps:
|
||||
> [!NOTE]
|
||||
> If the WDRT doesn't detect your HoloLens, try restarting your PC. If that doesn't work, select **My device was not detected**, select **Microsoft HoloLens**, and then follow the instructions.
|
||||
|
||||
# Use policies to manage updates to HoloLens
|
||||
## 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:
|
||||
|
||||
|
||||
@ -45,12 +45,13 @@ appliesto:
|
||||
| Topic | Description |
|
||||
| --- | --- |
|
||||
| [What's new in HoloLens](hololens-whats-new.md) | Discover new features in the latest updates via HoloLens release notes. |
|
||||
| [Install and manage applications on HoloLens](hololens-install-apps.md) | Install and manage important applications on HoloLens at scale. |
|
||||
| [Install and manage applications on HoloLens](hololens-install-apps.md) | Install and manage important applications on HoloLens at scale. |
|
||||
| [HoloLens update management](hololens-updates.md) | Use mobile device management (MDM) policies to configure settings for updates. |
|
||||
| [HoloLens user management](hololens-multiple-users.md) | Multiple users can shared a HoloLens device by using their Azure Active Directory accounts. |
|
||||
| [HoloLens user management](hololens-multiple-users.md) | Multiple users can share a HoloLens device by using their Azure Active Directory accounts. |
|
||||
| [HoloLens application access management](hololens-kiosk.md) | Manage application access for different user groups. |
|
||||
| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) | Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary. |
|
||||
| [Get support](https://support.microsoft.com/products/hololens) | Connect with Microsoft support resources for HoloLens in enterprise. |
|
||||
| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) | Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary. |
|
||||
| [Contact Support](https://support.microsoft.com/supportforbusiness/productselection) | Create a new support request for the business support team. |
|
||||
| [More support options](https://support.microsoft.com/products/hololens) | Connect with Microsoft support resources for HoloLens in the enterprise. |
|
||||
|
||||
## Related resources
|
||||
|
||||
|
||||
@ -42,6 +42,7 @@
|
||||
### [Save your BitLocker key](save-bitlocker-key-surface-hub.md)
|
||||
### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md)
|
||||
### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md)
|
||||
### [Update pen firmware on Surface Hub 2S](surface-hub-2s-pen-firmware.md)
|
||||
|
||||
## Secure
|
||||
### [Secure and manage Surface Hub 2S with SEMM and UEFI](surface-hub-2s-secure-with-uefi-semm.md)
|
||||
|
||||
BIN
devices/surface-hub/images/sh2-pen-1.png
Normal file
BIN
devices/surface-hub/images/sh2-pen-1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 50 KiB |
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows updates (Surface Hub)
|
||||
description: You can manage Windows updates on your Microsoft Surface Hub by setting the maintenance window, deferring updates, or using Windows Server Update Services (WSUS).
|
||||
title: Manage Windows updates on Surface Hub
|
||||
description: You can manage Windows updates on your Microsoft Surface Hub or Surface Hub 2S by setting the maintenance window, deferring updates, or using Windows Server Update Services (WSUS).
|
||||
ms.assetid: A737BD50-2D36-4DE5-A604-55053D549045
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
@ -13,7 +13,7 @@ ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Windows updates (Surface Hub)
|
||||
# Manage Windows updates on Surface Hub
|
||||
|
||||
New releases of the Surface Hub operating system are published through Windows Update, just like releases of Windows 10. There are a couple of ways you can manage which updates are installed on your Surface Hubs, and the timing for when updates are applied.
|
||||
- **Windows Update for Business** - New in Windows 10, Windows Update for Business is a set of features designed to provide enterprises additional control over how and when Windows Update installs releases, while reducing device management costs. Using this method, Surface Hubs are directly connected to Microsoft’s Windows Update service.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: greglin
|
||||
manager: laurawi
|
||||
audience: Admin
|
||||
ms.topic: article
|
||||
ms.date: 11/13/2019
|
||||
ms.date: 02/24/2020
|
||||
ms.localizationpriority: Medium
|
||||
---
|
||||
|
||||
@ -129,6 +129,7 @@ You can connect the following accessories to Surface Hub-2S using Bluetooth:
|
||||
- Keyboards
|
||||
- Headsets
|
||||
- Speakers
|
||||
- Surface Hub 2 pens
|
||||
|
||||
> [!NOTE]
|
||||
> After you connect a Bluetooth headset or speaker, you might need to change the default microphone and speaker settings. For more information, see [**Local management for Surface Hub settings**](https://docs.microsoft.com/surface-hub/local-management-surface-hub-settings).
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: greglin
|
||||
manager: laurawi
|
||||
audience: Admin
|
||||
ms.topic: article
|
||||
ms.date: 06/20/2019
|
||||
ms.date: 02/28/2020
|
||||
ms.localizationpriority: Medium
|
||||
---
|
||||
|
||||
@ -24,7 +24,7 @@ Surface Hub 2S allows IT administrators to manage settings and policies using a
|
||||
1. Sign in as a local administrator on Surface Hub 2S and open the **Settings** app. Select **Surface Hub** > **Device management** and then select **+** to add.
|
||||
2. After authenticating, the device will automatically register with Intune.
|
||||
|
||||
<br>
|
||||
<br>
|
||||
|
||||
### Auto registration — Azure Active Directory Affiliated
|
||||
|
||||
@ -44,17 +44,31 @@ For additional supported CSPs, see [Surface Hub CSPs in Windows 10](https://docs
|
||||
|
||||
## Quality of Service (QoS) settings
|
||||
|
||||
To ensure optimal video and audio quality on Surface Hub 2S, add the following QoS settings to the device. The settings are identical for Skype for Business and Teams.
|
||||
To ensure optimal video and audio quality on Surface Hub 2S, add the following QoS settings to the device.
|
||||
|
||||
### Microsoft Teams QoS settings
|
||||
|
||||
|**Name**|**Description**|**OMA-URI**|**Type**|**Value**|
|
||||
|:------ |:------------- |:--------- |:------ |:------- |
|
||||
|**Audio Ports**| Audio Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/SourcePortMatchCondition | String | 50000-50019 |
|
||||
|**Audio Ports**| Audio Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/DestinationPortMatchCondition | String | 3478-3479 |
|
||||
|**Audio DSCP**| Audio ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/DSCPAction | Integer | 46 |
|
||||
|**Video Ports**| Video Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubVideo/SourcePortMatchCondition | String | 50020-50039 |
|
||||
|**Video Ports**| Video Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubVideo/DestinationPortMatchCondition | String | 3480 |
|
||||
|**Video DSCP**| Video ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubVideo/DSCPAction | Integer | 34 |
|
||||
|
||||
|
||||
### Skype for Business QoS settings
|
||||
|
||||
| Name | Description | OMA-URI | Type | Value |
|
||||
| ------------------ | ------------------- | ------------------------------------------------------------------------ | ------- | ------------------------------ |
|
||||
| Audio Ports | Audio Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/SourcePortMatchCondition | String | 50000-50019 |
|
||||
| Audio DSCP | Audio ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/DSCPAction | Integer | 46 |
|
||||
| Audio Media Source | Skype App name | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/AppPathNameMatchCondition | String | Microsoft.PPISkype.Windows.exe |
|
||||
| Video Ports | Video Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubVideo/SourcePortMatchCondition | String | 50020-50039 |
|
||||
| Video DSCP | Video ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubVideo/DSCPAction | Integer | 34 |
|
||||
| Video Media Source | Skype App name | ./Device/Vendor/MSFT/NetworkQoSPolicy/HubVideo/AppPathNameMatchCondition | String | Microsoft.PPISkype.Windows.exe |
|
||||
|
||||
> [!NOTE]
|
||||
> These are the default port ranges. Administrators may change the port ranges in the Skype for Business and Teams control panel.
|
||||
> Both tables show default port ranges. Administrators may change the port ranges in the Skype for Business and Teams control panel.
|
||||
|
||||
## Microsoft Teams Mode settings
|
||||
|
||||
|
||||
@ -26,12 +26,6 @@ $ExchSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUr
|
||||
Import-PSSession $ExchSession
|
||||
```
|
||||
|
||||
```PowerShell
|
||||
$ExchServer = Read-Host "Please Enter the FQDN of your Exchange Server"
|
||||
$ExchSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://$ExchServer/PowerShell/ -Authentication Kerberos -Credential (Get-Credential)
|
||||
Import-PSSession $ExchSession
|
||||
```
|
||||
|
||||
## Create the device account
|
||||
|
||||
```PowerShell
|
||||
|
||||
67
devices/surface-hub/surface-hub-2s-pen-firmware.md
Normal file
67
devices/surface-hub/surface-hub-2s-pen-firmware.md
Normal file
@ -0,0 +1,67 @@
|
||||
---
|
||||
title: "Update pen firmware on Surface Hub 2S"
|
||||
description: "This page describes how to update firmware for the Surface Hub 2 pen."
|
||||
keywords: separate values with commas
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
manager: laurawi
|
||||
audience: Admin
|
||||
ms.topic: article
|
||||
ms.date: 02/26/2020
|
||||
ms.localizationpriority: Medium
|
||||
---
|
||||
|
||||
# Update pen firmware on Surface Hub 2S
|
||||
|
||||
You can update firmware on Surface Hub 2 pen from Windows Update for Business or by downloading the firmware update to a separate PC. Updated firmware is available from Windows Update beginning February 26, 2020.
|
||||
|
||||
## Update pen firmware using Windows Update for Business
|
||||
|
||||
This section describes how to update pen firmware via the automated maintenance cycles for Windows Update, configured by default to occur nightly at 3 a.m. You will need to plan for two maintenance cycles to complete before applying the update to the Surface Hub 2 pen. Alternately, like any other update, you can use Windows Server Update Services (WSUS) to apply the pen firmware. For more information, see [Managing Windows updates on Surface Hub](manage-windows-updates-for-surface-hub.md).
|
||||
|
||||
1. Ensure the Surface Hub 2 pen is paired to Surface Hub 2S: Press and hold the **top** button until the white indicator LED light begins to blink. <br>
|
||||
 <br>
|
||||
2. On Surface Hub, login as an Admin, open **Settings**, and then scan for new Bluetooth devices.
|
||||
3. Select the pen to complete the pairing process.
|
||||
4. Press the **top** button on the pen to apply the update. It may take up to two hours to complete.
|
||||
|
||||
## Update pen firmware by downloading to separate PC
|
||||
|
||||
You can update the firmware on Surface Hub 2 pen from a separate PC running Windows 10. This method also enables you to verify that the pen firmware has successfully updated to the latest version.
|
||||
|
||||
1. Pair the Surface Hub 2 pen to your Bluetooth-capable PC: Press and hold the **top** button until the white indicator LED light begins to blink. <br>
|
||||
 <br>
|
||||
2. On the PC, scan for new Bluetooth devices.
|
||||
3. Select the pen to complete the pairing process.
|
||||
4. Disconnect all other Surface Hub 2s pens before starting a new update.
|
||||
3. Download the [Surface Hub 2 Pen Firmware Update Tool](https://download.microsoft.com/download/8/3/F/83FD5089-D14E-42E3-AF7C-6FC36F80D347/Pen_Firmware_Tool.zip) to your PC.
|
||||
4. Run **PenCfu.exe.** The install progress is displayed in the tool. It may take several minutes to finish updating.
|
||||
|
||||
|
||||
## Check firmware version of Surface Hub 2 pen
|
||||
|
||||
1. Run **get_version.bat** and press the **top** button on the pen.
|
||||
2. The tool will report the firmware version of the pen. Example:
|
||||
- Old firmware is 468.2727.368
|
||||
- New firmware is 468.2863.369
|
||||
|
||||
## Command line options
|
||||
|
||||
You can run Surface Hub 2 Pen Firmware Update Tool (PenCfu.exe) from the command line.
|
||||
|
||||
1. Pair the pen to your PC and click the **top** button on the pen.
|
||||
2. Double click **PenCfu.exe** to initiate the firmware update. Note that the configuration file and the firmware image files must be stored in the same folder as the tool.
|
||||
3. For additional options, run **PenCfu.exe -h** to display the available parameters, as listed in the following table.
|
||||
- Example: PenCfu.exe -h
|
||||
4. Enter **Ctrl+C** to safely shut down the tool.
|
||||
|
||||
|
||||
|
||||
| **Command** | **Description** |
|
||||
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| -h help | Display tool command line interface help and exit. |
|
||||
| -v version | Display tool version and exit. |
|
||||
| -l log-filter | Set a filter level for the log file. Log messages have 4 possible levels: DEBUG (lowest), INFO, WARNING and ERROR (highest). Setting a log filter level filters log messages to only message with the same level or higher. For example, if the filter level is set to WARNING, only WARNING and ERROR messages will be logged. By default, this option is set to OFF, which disables logging. |
|
||||
| -g get-version | If specified, the tool will only get the FW version of the connected pen that matches the configuration file that is stored in the same folder as the tool.
|
||||
@ -530,7 +530,6 @@ This update to the Surface Hub includes quality improvements and security fixes.
|
||||
|
||||
## Related topics
|
||||
|
||||
* [Windows 10 feature roadmap](https://go.microsoft.com/fwlink/p/?LinkId=785967)
|
||||
* [Windows 10 release information](https://go.microsoft.com/fwlink/p/?LinkId=724328)
|
||||
* [Windows 10 November update: FAQ](https://windows.microsoft.com/windows-10/windows-update-faq)
|
||||
* [Microsoft Surface update history](https://go.microsoft.com/fwlink/p/?LinkId=724327)
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 169 KiB After Width: | Height: | Size: 134 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 54 KiB After Width: | Height: | Size: 69 KiB |
BIN
devices/surface/images/manage-surface-uefi-fig5-a.png
Normal file
BIN
devices/surface/images/manage-surface-uefi-fig5-a.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 90 KiB |
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Manage Surface UEFI settings (Surface)
|
||||
title: Manage Surface UEFI settings
|
||||
description: Use Surface UEFI settings to enable or disable devices or components, configure security settings, and adjust Surface device boot settings.
|
||||
keywords: firmware, security, features, configure, hardware
|
||||
ms.localizationpriority: medium
|
||||
@ -10,7 +10,7 @@ ms.pagetype: devices, surface
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 02/26/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
@ -61,7 +61,11 @@ You can find up-to-date information about the latest firmware version for your S
|
||||
|
||||
## UEFI Security page
|
||||
|
||||
The Security page allows you to set a password to protect UEFI settings. This password must be entered when you boot the Surface device to UEFI. The password can contain the following characters (as shown in Figure 2):
|
||||
|
||||
|
||||
*Figure 2. Configure Surface UEFI security settings*
|
||||
|
||||
The Security page allows you to set a password to protect UEFI settings. This password must be entered when you boot the Surface device to UEFI. The password can contain the following characters (as shown in Figure 3):
|
||||
|
||||
- Uppercase letters: A-Z
|
||||
|
||||
@ -75,19 +79,20 @@ The password must be at least 6 characters and is case sensitive.
|
||||
|
||||
|
||||
|
||||
*Figure 2. Add a password to protect Surface UEFI settings*
|
||||
*Figure 3. Add a password to protect Surface UEFI settings*
|
||||
|
||||
On the Security page you can also change the configuration of Secure Boot on your Surface device. Secure Boot technology prevents unauthorized boot code from booting on your Surface device, which protects against bootkit and rootkit-type malware infections. You can disable Secure Boot to allow your Surface device to boot third-party operating systems or bootable media. You can also configure Secure Boot to work with third-party certificates, as shown in Figure 3. Read more about [Secure Boot](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/secure-boot-overview) in the TechNet Library.
|
||||
On the Security page you can also change the configuration of Secure Boot on your Surface device. Secure Boot technology prevents unauthorized boot code from booting on your Surface device, which protects against bootkit and rootkit-type malware infections. You can disable Secure Boot to allow your Surface device to boot third-party operating systems or bootable media. You can also configure Secure Boot to work with third-party certificates, as shown in Figure 4. Read more about [Secure Boot](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/secure-boot-overview) in the TechNet Library.
|
||||
|
||||
|
||||
|
||||
*Figure 3. Configure Secure Boot*
|
||||
*Figure 4. Configure Secure Boot*
|
||||
|
||||
You can also enable or disable the Trusted Platform Module (TPM) device on the Security page, as shown in Figure 4. The TPM is used to authenticate encryption for your device’s data with BitLocker. Read more about [BitLocker](https://technet.microsoft.com/itpro/windows/keep-secure/bitlocker-overview) in the TechNet Library.
|
||||
Depending on your device, you may also be able to see if your TPM is enabled or disabled. If you do not see the **Enable TPM** setting, open tpm.msc in Windows to check the status, as shown in Figure 5. The TPM is used to authenticate encryption for your device’s data with BitLocker. To learn more, see [BitLocker overview](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview).
|
||||
|
||||
|
||||
|
||||
|
||||
*Figure 5. TPM console*
|
||||
|
||||
*Figure 4. Configure Surface UEFI security settings*
|
||||
|
||||
## UEFI menu: Devices
|
||||
|
||||
@ -107,11 +112,11 @@ The Devices page allows you to enable or disable specific devices and component
|
||||
|
||||
- Onboard Audio (Speakers and Microphone)
|
||||
|
||||
Each device is listed with a slider button that you can move to **On** (enabled) or **Off** (disabled) position, as shown in Figure 5.
|
||||
Each device is listed with a slider button that you can move to **On** (enabled) or **Off** (disabled) position, as shown in Figure 6.
|
||||
|
||||
|
||||
|
||||
*Figure 5. Enable and disable specific devices*
|
||||
*Figure 6. Enable and disable specific devices*
|
||||
|
||||
## UEFI menu: Boot configuration
|
||||
|
||||
@ -127,11 +132,11 @@ The Boot Configuration page allows you to change the order of your boot devices
|
||||
|
||||
You can boot from a specific device immediately, or you can swipe left on that device’s entry in the list using the touchscreen. You can also boot immediately to a USB device or USB Ethernet adapter when the Surface device is powered off by pressing the **Volume Down** button and the **Power** button simultaneously.
|
||||
|
||||
For the specified boot order to take effect, you must set the **Enable Alternate Boot Sequence** option to **On**, as shown in Figure 6.
|
||||
For the specified boot order to take effect, you must set the **Enable Alternate Boot Sequence** option to **On**, as shown in Figure 7.
|
||||
|
||||
|
||||
|
||||
*Figure 6. Configure the boot order for your Surface device*
|
||||
*Figure 7. Configure the boot order for your Surface device*
|
||||
|
||||
You can also turn on and off IPv6 support for PXE with the **Enable IPv6 for PXE Network Boot** option, for example when performing a Windows deployment using PXE where the PXE server is configured for IPv4 only.
|
||||
|
||||
@ -139,7 +144,7 @@ You can also turn on and off IPv6 support for PXE with the **Enable IPv6 for PXE
|
||||
The Management page allows you to manage use of Zero Touch UEFI Management and other features on eligible devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3.
|
||||
|
||||
|
||||
*Figure 7. Manage access to Zero Touch UEFI Management and other features*
|
||||
*Figure 8. Manage access to Zero Touch UEFI Management and other features*
|
||||
|
||||
|
||||
Zero Touch UEFI Management lets you remotely manage UEFI settings by using a device profile within Intune called Device Firmware Configuration Interface (DFCI). If you do not configure this setting, the ability to manage eligible devices with DFCI is set to **Ready**. To prevent DFCI, select **Opt-Out**.
|
||||
@ -151,11 +156,11 @@ For more information, refer to [Intune management of Surface UEFI settings](surf
|
||||
|
||||
## UEFI menu: Exit
|
||||
|
||||
Use the **Restart Now** button on the **Exit** page to exit UEFI settings, as shown in Figure 8.
|
||||
Use the **Restart Now** button on the **Exit** page to exit UEFI settings, as shown in Figure 9.
|
||||
|
||||
|
||||
|
||||
*Figure 8. Click Restart Now to exit Surface UEFI and restart the device*
|
||||
*Figure 9. Click Restart Now to exit Surface UEFI and restart the device*
|
||||
|
||||
## Surface UEFI boot screens
|
||||
|
||||
@ -163,44 +168,44 @@ When you update Surface device firmware, by using either Windows Update or manua
|
||||
|
||||
|
||||
|
||||
*Figure 9. The Surface UEFI firmware update displays a blue progress bar*
|
||||
*Figure 10. The Surface UEFI firmware update displays a blue progress bar*
|
||||
|
||||
|
||||
|
||||
*Figure 10. The System Embedded Controller firmware update displays a green progress bar*
|
||||
*Figure 11. The System Embedded Controller firmware update displays a green progress bar*
|
||||
|
||||
|
||||
|
||||
*Figure 11. The SAM Controller firmware update displays an orange progress bar*
|
||||
*Figure 12. The SAM Controller firmware update displays an orange progress bar*
|
||||
|
||||
|
||||
|
||||
*Figure 12. The Intel Management Engine firmware update displays a red progress bar*
|
||||
*Figure 13. The Intel Management Engine firmware update displays a red progress bar*
|
||||
|
||||
|
||||
|
||||
*Figure 13. The Surface touch firmware update displays a gray progress bar*
|
||||
*Figure 14. The Surface touch firmware update displays a gray progress bar*
|
||||
|
||||
|
||||
|
||||
*Figure 14. The Surface KIP firmware update displays a light green progress bar*
|
||||
*Figure 15. The Surface KIP firmware update displays a light green progress bar*
|
||||
|
||||
|
||||
|
||||
*Figure 15. The Surface ISH firmware update displays a light pink progress bar*
|
||||
*Figure 16 The Surface ISH firmware update displays a light pink progress bar*
|
||||
|
||||
|
||||
|
||||
*Figure 16. The Surface Trackpad firmware update displays a pink progress bar*
|
||||
*Figure 17. The Surface Trackpad firmware update displays a pink progress bar*
|
||||
|
||||
|
||||
|
||||
*Figure 17. The Surface TCON firmware update displays a light gray progress bar*
|
||||
*Figure 18. The Surface TCON firmware update displays a light gray progress bar*
|
||||
|
||||
|
||||
|
||||
|
||||
*Figure 18. The Surface TPM firmware update displays a purple progress bar*
|
||||
*Figure 19. The Surface TPM firmware update displays a purple progress bar*
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
@ -208,7 +213,7 @@ When you update Surface device firmware, by using either Windows Update or manua
|
||||
|
||||
|
||||
|
||||
*Figure 19. Surface boot screen that indicates Secure Boot has been disabled in Surface UEFI settings*
|
||||
*Figure 20. Surface boot screen that indicates Secure Boot has been disabled in Surface UEFI settings*
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Microsoft Surface Dock Firmware Update
|
||||
description: This article explains how to use Microsoft Surface Dock Firmware Update, newly redesigned to update Surface Dock firmware while running in the background on your Surface device.
|
||||
description: This article explains how to use Microsoft Surface Dock Firmware Update to update Surface Dock firmware. When installed on your Surface device, it will update any Surface Dock attached to your Surface device.
|
||||
ms.localizationpriority: medium
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -11,6 +11,7 @@ ms.topic: article
|
||||
ms.reviewer: scottmca
|
||||
manager: dansimp
|
||||
ms.audience: itpro
|
||||
ms.date: 02/07/2020
|
||||
---
|
||||
# Microsoft Surface Dock Firmware Update
|
||||
|
||||
@ -32,17 +33,19 @@ This section is optional and provides an overview of how to monitor installation
|
||||
To monitor the update:
|
||||
|
||||
1. Open Event Viewer, browse to **Windows Logs > Application**, and then under **Actions** in the right-hand pane click **Filter Current Log**, enter **SurfaceDockFwUpdate** next to **Event sources**, and then click **OK**.
|
||||
|
||||
2. Type the following command at an elevated command prompt:
|
||||
|
||||
```cmd
|
||||
Reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WUDF\Services\SurfaceDockFwUpdate\Parameters"
|
||||
```
|
||||
```cmd
|
||||
Reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WUDF\Services\SurfaceDockFwUpdate\Parameters"
|
||||
```
|
||||
3. Install the update as described in the [next section](#install-the-surface-dock-firmware-update) of this article.
|
||||
|
||||
4. Event 2007 with the following text indicates a successful update: **Firmware update finished. hr=0 DriverTelementry EventCode = 2007**.
|
||||
- If the update is not successful, then event ID 2007 will be displayed as an **Error** event rather than **Information**. Additionally, the version reported in the Windows Registry will not be current.
|
||||
- If the update is not successful, then event ID 2007 will be displayed as an **Error** event rather than **Information**. Additionally, the version reported in the Windows Registry will not be current.
|
||||
5. When the update is complete, updated DWORD values will be displayed in the Windows Registry, corresponding to the current version of the tool. See the [Versions reference](#versions-reference) section in this article for details. For example:
|
||||
- Component10CurrentFwVersion 0x04ac3970 (78395760)
|
||||
- Component20CurrentFwVersion 0x04915a70 (76634736)
|
||||
- Component10CurrentFwVersion 0x04ac3970 (78395760)
|
||||
- Component20CurrentFwVersion 0x04915a70 (76634736)
|
||||
|
||||
>[!TIP]
|
||||
>If you see "The description for Event ID xxxx from source SurfaceDockFwUpdate cannot be found" in event text, this is expected and can be ignored.
|
||||
@ -52,8 +55,8 @@ To monitor the update:
|
||||
This section describes how to install the firmware update.
|
||||
|
||||
1. Download and install [Microsoft Surface Dock Firmware Update](https://www.microsoft.com/download/details.aspx?id=46703).
|
||||
- The update requires a Surface device running Windows 10, version 1803 or later.
|
||||
- Installing the MSI file might prompt you to restart Surface. However, restarting is not required to perform the update.
|
||||
- The update requires a Surface device running Windows 10, version 1803 or later.
|
||||
- Installing the MSI file might prompt you to restart Surface. However, restarting is not required to perform the update.
|
||||
|
||||
2. Disconnect your Surface device from the Surface Dock (using the power adapter), wait ~5 seconds, and then reconnect. The Surface Dock Firmware Update will update the dock silently in background. The process can take a few minutes to complete and will continue even if interrupted.
|
||||
|
||||
@ -68,10 +71,10 @@ You can use Windows Installer commands (Msiexec.exe) to deploy Surface Dock Firm
|
||||
msiexec /i "\\share\folder\Surface_Dock_FwUpdate_1.42.139_Win10_17134_19.084.31680_0.msi" /quiet /norestart
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> A log file is not created by default. In order to create a log file, you will need to append "/l*v [path]". For example: Msiexec.exe /i \<path to msi file\> /l*v %windir%\logs\ SurfaceDockFWI.log"
|
||||
> [!NOTE]
|
||||
> A log file is not created by default. In order to create a log file, you will need to append "/l*v [path]". For example: Msiexec.exe /i \<path to msi file\> /l*v %windir%\logs\ SurfaceDockFWI.log"
|
||||
|
||||
For more information, refer to [Command line options](https://docs.microsoft.com/windows/win32/msi/command-line-options) documentation.
|
||||
For more information, refer to [Command line options](https://docs.microsoft.com/windows/win32/msi/command-line-options) documentation.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you want to keep your Surface Dock updated using any other method, refer to [Update your Surface Dock](https://support.microsoft.com/help/4023478/surface-update-your-surface-dock) for details.
|
||||
@ -96,11 +99,11 @@ Successful completion of Surface Dock Firmware Update results in new registry ke
|
||||
|
||||
1. Open Regedit and navigate to the following registry path:
|
||||
|
||||
- **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WUDF\Services\SurfaceDockFwUpdate\Parameters**
|
||||
- **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WUDF\Services\SurfaceDockFwUpdate\Parameters**
|
||||
|
||||
2. Look for the registry keys: **Component10CurrentFwVersion and Component20CurrentFwVersion**, which refer to the firmware that is currently on the device.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Verify the new registry key values match the updated registry key values listed in the Versions reference at the end of this document. If the values match, the firmware was updated successfully.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user