mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge branch 'master' into symantec-mdatp
This commit is contained in:
Denise Vangel-MSFT
@ -58,6 +58,7 @@
|
||||
# Update, troubleshoot, or recover HoloLens
|
||||
## [Update HoloLens](hololens-update-hololens.md)
|
||||
## [Restart, reset, or recover HoloLens](hololens-recovery.md)
|
||||
## [Restart, reset, or recover HoloLens 1st Gen](hololens1-recovery.md)
|
||||
## [Troubleshoot HoloLens issues](hololens-troubleshooting.md)
|
||||
## [Collect diagnostic information from HoloLens devices](hololens-diagnostic-logs.md)
|
||||
## [Known issues for HoloLens](hololens-known-issues.md)
|
||||
|
||||
@ -239,7 +239,7 @@ If your device was previously set up for someone else, either for a client or fo
|
||||
- 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.
|
||||
- For a non-MDM device, you can [put the device into **Flashing Mode** and use Advanced Recovery Companion](hololens-recovery.md#clean-reflash-the-device) to recover the device.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ While both devices need to calibrate for the best hologram viewing experience, t
|
||||
|
||||
## Calibrating your HoloLens 2
|
||||
|
||||
HoloLens 2 uses eye-tracking technology to improve your experience seeing and interacting with the virtual environment. Calibrating the HoloLens 2 ensures that it can accurately track your eyes (and the eyes of anyone else who uses the device). After calibration, holograms will appear correctly even as the visor shifts on your head.
|
||||
HoloLens 2 uses eye-tracking technology to improve your experience seeing and interacting with the virtual environment. Calibrating the HoloLens 2 ensures that it can accurately track your eyes (and the eyes of anyone else who uses the device). It also helps with user comfort, hologram alignment, and hand tracking. After calibration, holograms will appear correctly even as the visor shifts on your head.
|
||||
|
||||
HoloLens 2 prompts a user to calibrate the device under the following circumstances:
|
||||
|
||||
|
||||
@ -19,107 +19,99 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Restart, reset, or recover HoloLens
|
||||
# Reset and Recovery for HoloLens 2
|
||||
|
||||
If you're experiencing problems with your HoloLens you may want to try a restart, reset, or even re-flash with device recovery.
|
||||
## Charging the device
|
||||
|
||||
Here are some things to try if your HoloLens isn't running well. This article will guide you through the recommended recovery steps in succession.
|
||||
Before starting any troubleshooting procedure, if possible, ensure that your device is charged at least between 20% and 40%.
|
||||
|
||||
This article focuses on the HoloLens device and software, if your holograms don't look right, [this article](hololens-environment-considerations.md) talks about environmental factors that improve hologram quality.
|
||||
|
||||
## Restart your HoloLens
|
||||
|
||||
First, try restarting the device.
|
||||
|
||||
### Perform a safe restart by using Cortana
|
||||
|
||||
The safest way to restart the HoloLens is by using Cortana. This is generally a great first-step when experiencing an issue with HoloLens:
|
||||
|
||||
1. Put on your device
|
||||
1. Make sure it's powered on, a user is logged in, and the device is not waiting for a password to unlock it.
|
||||
1. Say "Hey Cortana, reboot" or "Hey Cortana, restart."
|
||||
1. When she acknowledges she will ask you for confirmation. Wait a second for a sound to play after she has finished her question, indicating she is listening to you and then say "Yes."
|
||||
1. The device will now restart.
|
||||
|
||||
### Perform a safe restart by using the power button
|
||||
|
||||
If you still can't restart your device, you can try to restart it by using the power button:
|
||||
|
||||
1. Press and hold the power button for five seconds.
|
||||
1. After one second, you will see all five LEDs illuminate, then slowly turn off from right to left.
|
||||
1. After five seconds, all LEDs will be off, indicating the shutdown command was issued successfully.
|
||||
1. Note that it's important to stop pressing the button immediately after all the LEDs have turned off.
|
||||
1. Wait one minute for the shutdown to cleanly succeed. Note that the shutdown may still be in progress even if the displays are turned off.
|
||||
1. Power on the device again by pressing and holding the power button for one second.
|
||||
|
||||
### Perform a safe restart by using Windows Device Portal
|
||||
Please ensure you are using the charger and the USB Type-C cables that come with the HoloLens2 device. In case they are not available ensure the charger available can support at least 15W of power.
|
||||
|
||||
> [!NOTE]
|
||||
> To do this, HoloLens has to be configured as a developer device.
|
||||
> Read more about [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal).
|
||||
> If possible, do not use a PC to charge the device over USB as this will provide a very slow charge.
|
||||
|
||||
If the previous procedure doesn't work, you can try to restart the device by using [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal). In the upper right corner, there is an option to restart or shut down the device.
|
||||
If the device is correctly booted and running there are three different ways of checking the charge of your battery.
|
||||
|
||||
### Perform an unsafe forced restart
|
||||
1. From the main menu of the HoloLens Device UI.
|
||||
2. Using the LED close to the power button (for 40% you should see at least two solid LEDS).
|
||||
3. On your Host PC open File Explorer window and look for your HoloLens 2 device on left side under “This PC”.
|
||||
|
||||
If none of the previous methods are able to successfully restart your device, you can force a restart. This method is equivalent to pulling the battery from the HoloLens. It is a dangerous operation which may leave your device in a corrupt state. If that happens, you'll have to flash your HoloLens.
|
||||
a. Right click on the name of the device and select properties. A dialog will appear showing the battery level for your device.
|
||||
|
||||
> [!WARNING]
|
||||
> This is a potentially harmful method and should only be used in the event none of the above methods work.
|
||||
|
||||
|
||||
1. Press and hold the power button for at least 10 seconds.
|
||||
If the device cannot be booted to the Startup Menu, please take note of the LEDs and enumeration on the host PC and follow the troubleshooting guide (https://docs.microsoft.com/hololens/hololens-troubleshooting). In case the state of the device does not fall in any of the states listed in the troubleshooting guide, execute the **hard reset procedure** without reconnecting the device to your host PC, but connect it instead to the power supply. Wait for at least one hour for the device to charge.
|
||||
|
||||
- It's okay to hold the button for longer than 10 seconds.
|
||||
- It's safe to ignore any LED activity.
|
||||
1. Release the button and wait for two or three seconds.
|
||||
1. Power on the device again by pressing and holding the power button for one second.
|
||||
If you're still having problems, press the power button for 4 seconds, until all of the battery indicators fade out and the screen stops displaying holograms. Wait 1 minute, then press the power button again to turn on the device.
|
||||
## Reset the device
|
||||
|
||||
## Reset to factory settings
|
||||
Under certain circumstances the customer may be required to manually reset the device without using the SW UI.
|
||||
|
||||
> [!NOTE]
|
||||
> The battery needs at least 40 percent charge to reset.
|
||||
### Standard procedure
|
||||
1. Disconnect the device from the power supply or the host PC by unplugging the Type-C cable.
|
||||
|
||||
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.
|
||||
2. Press and hold the power button for 15 seconds. All LEDs should be off.
|
||||
|
||||
If you reset your device, all your personal data, apps, and settings will be erased, including TPM reset. Resetting will only install the latest installed version of Windows Holographic and you will have to redo all the initialization steps (calibrate, connect to Wi-Fi, create a user account, download apps, and so forth).
|
||||
3. Wait 2-3 seconds and Short press the power button, the LEDs close to the power button will light up and the device will start to boot.
|
||||
|
||||
1. Launch the Settings app, and then select **Update** > **Reset**.
|
||||
1. Select the **Reset device** option and read the confirmation message.
|
||||
1. If you agree to reset your device, the device will restart and display a set of spinning gears with a progress bar.
|
||||
1. Wait about 30 minutes for this process to complete.
|
||||
1. The reset will complete and the device will restart into the out-of-the-box experience.
|
||||
4. Connect the device to the host PC, open Device Manager (for Windows 10 press the “Windows” key and then the “x” key and click on “Device Manager”) and make sure the device enumerates correctly as Microsoft HoloLens as shown in the pictures below:
|
||||
|
||||
## Re-install the operating system
|
||||
|
||||
|
||||
If the device is still having a problem after rebooting and resetting, you can use a recovery tool on your computer to reinstall the HoloLens' operating system and firmware.
|
||||
### Hard-reset procedure
|
||||
|
||||
HoloLens (1st gen) and HoloLens 2 use different tools but both tools will auto-detect your HoloLens and install new software.
|
||||
If the standard reset procedure does not work, you can use the hard-reset procedure.
|
||||
|
||||
All of the data HoloLens needs to reset is packaged in a Full Flash Update (ffu). This is similar to an iso, wim, or vhd. [Learn about FFU image file formats.](https://docs.microsoft.com/windows-hardware/manufacture/desktop/wim-vs-ffu-image-file-formats)
|
||||
1. Disconnect the device from the power supply or the host PC by unplugging the Type-C cable.
|
||||
|
||||
### HoloLens 2
|
||||
2. Hold volume down + power for 15 seconds.
|
||||
|
||||
The Advanced Recovery Companion is a new app in Microsoft Store restore the operating system image to your HoloLens 2 device. Advanced Recovery Companion erases all your personal data, apps, and settings, and resets TPM.
|
||||
3. The device will automatically reboot.
|
||||
|
||||
1. On your computer, get [Advanced Recovery Companion](https://www.microsoft.com/p/advanced-recovery-companion/9p74z35sfrs8?activetab=pivot:overviewtab) from Microsoft Store.
|
||||
2. Connect HoloLens 2 to your computer.
|
||||
3. Start Advanced Recovery Companion.
|
||||
4. On the **Welcome** page, select your device.
|
||||
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.
|
||||
4. Connect the device to the host PC, open Device Manager (for Windows 10 press the “Windows” key and then the “x” key and click on “Device Manager”) and make sure the device enumerates correctly as Microsoft HoloLens as shown in the pictures below.
|
||||
|
||||
#### Manual flashing mode
|
||||
|
||||
|
||||
> [!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:
|
||||
## Clean reflash the device
|
||||
|
||||
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.
|
||||
1. The device should be visible in **Device Manager** as a **Microsoft HoloLens Recovery** device.
|
||||
1. Launch Advanced Recovery Companion, and follow the on-screen prompts to reflash the OS to the HoloLens 2.
|
||||
In extraordinary situations you may be required to clean flash the device. There are two ways to reflash a HoloLens2 device. For all reflashing procedures you will be required to [install the Advanced Recovery Companion app from the Windows Store](https://www.microsoft.com/store/productId/9P74Z35SFRS8). If you reset your device, all your personal data, apps, and settings will be erased, including TPM reset.
|
||||
|
||||
#### Downloading ARC without using the app store
|
||||
Advanced Recovery Companion is currently set to download the feature release build for [Windows Holographic 2004](hololens-release-notes.md#windows-holographic-version-2004), if you would like to download the latest HoloLens 2 FFU to flash your device via Advanced Recovery Companion then you may download it from [here](https://aka.ms/hololens2download). This is kept up-to-date and will match the latest generally available build.
|
||||
|
||||
Before starting the flashing procedure make sure the app is installed and running on your Windows 10 PC and ready to detect the device.
|
||||
|
||||
|
||||
|
||||
### Normal procedure
|
||||
|
||||
1. While the HoloLens device is running, connect it to your Windows 10 PC where you previously launched the Advanced Recovery Companion App.
|
||||
|
||||
2. The device will automatically be detected and the Advanced Recovery Companion App UI will update as follows:
|
||||
|
||||
|
||||
|
||||
3. Select the HoloLens2 device in the Advanced Recovery Companion App UI and follow the instructions to complete the flashing.
|
||||
|
||||
### Manual procedure
|
||||
|
||||
If the device does not boot correctly you may need to put the HoloLens 2 device in Recovery mode.
|
||||
|
||||
1. Disconnect the device from the power supply or the host PC by unplugging the Type-C cable.
|
||||
|
||||
2. Press and hold the power button for 15 seconds. All LEDs should turn off.
|
||||
|
||||
3. While pressing the volume up button, press and release the power button to boot the device. Wait 10 seconds before releasing the volume up button. Out of the 5 LEDs on the device, only the middle LED will light up.
|
||||
|
||||
4. Connect the device to the host PC, open Device Manager (for Windows 10 press the “Windows” key and then the “x” key and click on “Device Manager”) and make sure the device enumerates correctly as Microsoft HoloLens as shown in the image below.
|
||||
|
||||
|
||||
|
||||
5. The device will be automatically detected, and the Advanced Recovery Companion app UI will update as follows:
|
||||
|
||||
|
||||
|
||||
6. Select the HoloLens 2 device in the Advanced Recovery Companion app UI and follow the instructions to complete the flashing.
|
||||
|
||||
## Downloading ARC without using the app store
|
||||
|
||||
If an IT environment prevents the use of the Windows Store app or limits access to the retail store, IT administrators can make this app available through other ‘offline’ deployment paths.
|
||||
|
||||
@ -151,18 +143,3 @@ Other resources:
|
||||
- https://docs.microsoft.com/windows-hardware/manufacture/desktop/dism-app-package--appx-or-appxbundle--servicing-command-line-options
|
||||
|
||||
|
||||
### HoloLens (1st gen)
|
||||
|
||||
If necessary, you can install a completely new operating system on your HoloLens (1st gen) with the Windows Device Recovery Tool.
|
||||
|
||||
Before you use this tool, determine if restarting or resetting your HoloLens fixes the problem. The recovery process may take some time. When you're done, the latest version of the Windows Holographic software approved for your HoloLens will be installed.
|
||||
|
||||
To use the tool, you'll need a computer running Windows 10 or later, with at least 4 GB of free storage space. Please note that you can't run this tool on a virtual machine.
|
||||
|
||||
To recover your HoloLens
|
||||
|
||||
1. Download and install the [Windows Device Recovery Tool](https://support.microsoft.com/help/12379/windows-10-mobile-device-recovery-tool-faq) on your computer.
|
||||
1. Connect the HoloLens (1st gen) to your computer using the Micro USB cable that came with your HoloLens.
|
||||
1. Run the Windows Device Recovery Tool and follow the instructions.
|
||||
|
||||
If the HoloLens (1st gen) isn't automatically detected, select **My device was not detected** and follow the instructions to put your device into recovery mode.
|
||||
|
||||
@ -20,7 +20,7 @@ appliesto:
|
||||
|
||||
# HoloLens 2 release notes
|
||||
|
||||
To ensure you have a productive experience with your HoloLens devices, we continue to release feature, bug and security updates. In this page you can learn about what’s new on HoloLens each month. If you would like to download the latest HoloLens 2 FFU to flash your device via [Advanced Recovery Companion](hololens-recovery.md#re-install-the-operating-system) then you may download it from [here](https://aka.ms/hololens2download). This is kept up-to-date and will match the latest generally available build.
|
||||
To ensure you have a productive experience with your HoloLens devices, we continue to release feature, bug and security updates. In this page you can learn about what’s new on HoloLens each month. If you would like to download the latest HoloLens 2 FFU to flash your device via [Advanced Recovery Companion](hololens-recovery.md#clean-reflash-the-device) then you may download it from [here](https://aka.ms/hololens2download). This is kept up-to-date and will match the latest generally available build.
|
||||
|
||||
HoloLens Emulator Release Notes can be found [here](https://docs.microsoft.com/windows/mixed-reality/hololens-emulator-archive).
|
||||
|
||||
|
||||
127
devices/hololens/hololens1-recovery.md
Normal file
127
devices/hololens/hololens1-recovery.md
Normal file
@ -0,0 +1,127 @@
|
||||
---
|
||||
title: Restart, reset, or recover HoloLens 1
|
||||
ms.reviewer: Both basic and advanced instructions for rebooting or resetting your HoloLens.
|
||||
description: How to use Windows Device Recovery Tool to flash an image to HoloLens 1st Gen.
|
||||
keywords: how-to, reboot, reset, recover, hard reset, soft reset, power cycle, HoloLens, shut down, wdrt, windows device recovery tool
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
author: evmill
|
||||
ms.author: v-evmill
|
||||
ms.date: 06/01/2020
|
||||
ms.custom:
|
||||
- CI 111456
|
||||
- CSSTroubleshooting
|
||||
ms.topic: article
|
||||
ms.localizationpriority: high
|
||||
manager: yannisle
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
---
|
||||
|
||||
# Restart, reset, or recover HoloLens 1st Gen
|
||||
|
||||
If you're experiencing problems with your HoloLens you may want to try a restart, reset, or even re-flash with device recovery.
|
||||
|
||||
Here are some things to try if your HoloLens isn't running well. This article will guide you through the recommended recovery steps in succession.
|
||||
|
||||
If you are looking to recover a HoloLens 2, please view the page for [Recovering a HoloLens 2](https://docs.microsoft.com/hololens/hololens-recovery), as there are differences in the processes.
|
||||
|
||||
This article focuses on the HoloLens device and software, if your holograms don't look right, [this article](hololens-environment-considerations.md) talks about environmental factors that improve hologram quality.
|
||||
|
||||
## Restart
|
||||
|
||||
### Perform a safe restart by using Cortana
|
||||
|
||||
The safest way to restart the HoloLens is by using Cortana. This is generally an easy first-step when experiencing an issue with HoloLens.
|
||||
|
||||
> [!NOTE]
|
||||
> Cortana is not avalible on all devices.
|
||||
> Cortana is avalible to all HoloLens (1st Gen) devices.
|
||||
> Cortana is avalible on HoloLens 2 devices on a build prior to the Windows Holograpic, Version 2004 update.
|
||||
|
||||
1. Put on your device
|
||||
1. Make sure it's powered on, a user is logged in, and the device is not waiting for a password to unlock it.
|
||||
1. Say "Hey Cortana, reboot" or "Hey Cortana, restart."
|
||||
1. When she acknowledges she will ask you for confirmation. Wait a second for a sound to play after she has finished her question, indicating she is listening to you and then say "Yes."
|
||||
1. The device will now restart.
|
||||
|
||||
### Perform a safe restart by using the power button
|
||||
|
||||
If you still can't restart your device, you can try to restart it by using the power button:
|
||||
|
||||
1. Press and hold the power button for five seconds.
|
||||
1. After one second, you will see all five LEDs illuminate, then slowly turn off from right to left.
|
||||
1. After five seconds, all LEDs will be off, indicating the shutdown command was issued successfully.
|
||||
1. Note that it's important to stop pressing the button immediately after all the LEDs have turned off.
|
||||
1. Wait one minute for the shutdown to cleanly succeed. Note that the shutdown may still be in progress even if the displays are turned off.
|
||||
1. Power on the device again by pressing and holding the power button for one second.
|
||||
|
||||
### Perform a safe restart by using Windows Device Portal
|
||||
|
||||
> [!NOTE]
|
||||
> To do this, HoloLens has to be configured as a developer device.
|
||||
> Read more about [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal).
|
||||
|
||||
If the previous procedure doesn't work, you can try to restart the device by using [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal). In the upper right corner, there is an option to restart or shut down the device.
|
||||
|
||||
### Perform an unsafe forced restart
|
||||
|
||||
If none of the previous methods are able to successfully restart your device, you can force a restart. This method is equivalent to pulling the battery from the HoloLens. It is a dangerous operation which may leave your device in a corrupt state. If that happens, you'll have to flash your HoloLens.
|
||||
|
||||
> [!WARNING]
|
||||
> This is a potentially harmful method and should only be used in the event none of the above methods work.
|
||||
|
||||
1. Press and hold the power button for at least 10 seconds.
|
||||
- It's okay to hold the button for longer than 10 seconds.
|
||||
- It's safe to ignore any LED activity.
|
||||
1. Release the button and wait for two or three seconds.
|
||||
1. Power on the device again by pressing and holding the power button for one second.
|
||||
If you're still having problems, press the power button for 4 seconds, until all of the battery indicators fade out and the screen stops displaying holograms. Wait 1 minute, then press the power button again to turn on the device.
|
||||
|
||||
## Reset to factory settings
|
||||
|
||||
> [!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.
|
||||
|
||||
If you reset your device, all your personal data, apps, and settings will be erased, including TPM reset. Resetting will only install the latest installed version of Windows Holographic and you will have to redo all the initialization steps (calibrate, connect to Wi-Fi, create a user account, download apps, and so forth).
|
||||
|
||||
1. Launch the Settings app, and then select **Update** > **Reset**.
|
||||
1. Select the **Reset device** option and read the confirmation message.
|
||||
1. If you agree to reset your device, the device will restart and display a set of spinning gears with a progress bar.
|
||||
1. Wait about 30 minutes for this process to complete.
|
||||
1. The reset will complete and the device will restart into the out-of-the-box experience.
|
||||
|
||||
## Re-install the operating system
|
||||
|
||||
If the device is still having a problem after rebooting and resetting, you can use a recovery tool on your computer to reinstall the HoloLens' operating system and firmware.
|
||||
|
||||
All of the data HoloLens needs to reset is packaged in a Full Flash Update (ffu). This is similar to an iso, wim, or vhd. [Learn about FFU image file formats.](https://docs.microsoft.com/windows-hardware/manufacture/desktop/wim-vs-ffu-image-file-formats)
|
||||
|
||||
If necessary, you can install a completely new operating system on your HoloLens (1st gen) with the Windows Device Recovery Tool.
|
||||
|
||||
Before you use this tool, determine if restarting or resetting your HoloLens fixes the problem. The recovery process may take some time. When you're done, the latest version of the Windows Holographic software approved for your HoloLens will be installed.
|
||||
|
||||
To use the tool, you'll need a computer running Windows 10 or later, with at least 4 GB of free storage space. Please note that you can't run this tool on a virtual machine.
|
||||
|
||||
### Recover your HoloLens:
|
||||
|
||||
1. Download and install the [Windows Device Recovery Tool](https://support.microsoft.com/help/12379/windows-10-mobile-device-recovery-tool-faq) on your computer.
|
||||
1. Connect the HoloLens (1st gen) to your computer using the Micro USB cable that came with your HoloLens.
|
||||
1. Run the Windows Device Recovery Tool and follow the instructions.
|
||||
|
||||
If the HoloLens (1st gen) isn't automatically detected, select **My device was not detected** and follow the instructions to put your device into recovery mode.
|
||||
|
||||
### Manual Flashing Mode:
|
||||
|
||||
In the event that your device is not being detected please use the following method to manually place it into flashing mode.
|
||||
|
||||
1. Unplug the device from all power sources.
|
||||
1. If the device is on please hold down the power button until it is completely off.
|
||||
1. Hold the **Volume Up** button, and breifly tap the **Power button**.
|
||||
1. The device should boot and then display only the middle LED light.
|
||||
1. Plug the device into your PC.
|
||||
1. Launch Windows Device Recovery Tool.
|
||||
1. You will need to select *My device was not detected**, and then select **HoloLens**.
|
||||
1. Follow the instructions to recover your device.
|
||||
@ -104,7 +104,7 @@ Not sure what the indicator lights on your HoloLens mean? Want to know how HoloL
|
||||
| - | - | - |
|
||||
| You press the Power button. | One light flashes five times, then turns off. | The HoloLens battery is critically low. Charge your HoloLens. |
|
||||
| You press the Power button. | All five lights flash five times, then turn off. | HoloLens cannot start correctly and is in an error state. [Reinstall the operating system](hololens-recovery.md) to recover your device. |
|
||||
| You press the Power button. | The 1st, 3rd, and 5th lights flash together continually. | HoloLens may have a hardware failure. To be sure, [reinstall the OS](hololens-recovery.md#hololens-2), and try again. After reinstalling the OS, if the light-flash pattern persists, contact [support](https://support.microsoft.com/en-us/supportforbusiness/productselection?sapid=3ec35c62-022f-466b-3a1e-dbbb7b9a55fb). |
|
||||
| You press the Power button. | The 1st, 3rd, and 5th lights flash together continually. | HoloLens may have a hardware failure. To be sure, [reinstall the OS](hololens-recovery.md), and try again. After reinstalling the OS, if the light-flash pattern persists, contact [support](https://support.microsoft.com/en-us/supportforbusiness/productselection?sapid=3ec35c62-022f-466b-3a1e-dbbb7b9a55fb). |
|
||||
|
||||
## Safety and comfort
|
||||
|
||||
|
||||
BIN
devices/hololens/images/ARC1.png
Normal file
BIN
devices/hololens/images/ARC1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
BIN
devices/hololens/images/ARC2.png
Normal file
BIN
devices/hololens/images/ARC2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
BIN
devices/hololens/images/ResetRecovery1.png
Normal file
BIN
devices/hololens/images/ResetRecovery1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 150 KiB |
BIN
devices/hololens/images/ResetRecovery2.png
Normal file
BIN
devices/hololens/images/ResetRecovery2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
@ -9,7 +9,6 @@ ms.author: greglin
|
||||
manager: laurawi
|
||||
audience: Admin
|
||||
ms.topic: article
|
||||
ms.date: 11/04/2019
|
||||
ms.localizationpriority: Medium
|
||||
---
|
||||
|
||||
@ -19,7 +18,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 1 - Training overview
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46Jud>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46Jud]
|
||||
|
||||
- Welcome and introduction
|
||||
- Training overview and agenda
|
||||
@ -31,7 +30,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 2 - Getting started with Surface Hub
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46Ejt>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46Ejt]
|
||||
|
||||
- What is Surface Hub?
|
||||
- Technical overview
|
||||
@ -42,7 +41,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 3 - Navigating Surface Hub
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46OFW>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46OFW]
|
||||
|
||||
- Welcome screen
|
||||
- Start menu
|
||||
@ -54,7 +53,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 4 - Whiteboarding and collaboration
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46M4v>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46M4v]
|
||||
|
||||
- Whiteboard introduction
|
||||
- Starting the Whiteboard
|
||||
@ -66,7 +65,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 5 - Exploring Surface Hub apps
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46Ejz>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46Ejz]
|
||||
|
||||
- Surface Hub apps introduction
|
||||
- PowerPoint overview
|
||||
@ -76,7 +75,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 6 - Advanced apps and Office 365
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46EjA>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46EjA]
|
||||
|
||||
- Advanced apps introduction
|
||||
- Microsoft Maps
|
||||
@ -88,7 +87,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 7 - Connecting devices
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46M4w>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46M4w]
|
||||
|
||||
- Connect introduction
|
||||
- Miracast overview
|
||||
@ -99,7 +98,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 8 - Skype for Business meetings
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46M4x>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46M4x]
|
||||
|
||||
- Introduction to Skype for Business
|
||||
-Scheduling Skype for Business meetings
|
||||
@ -111,7 +110,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 9 - Microsoft Teams meetings
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46OFZ>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46OFZ]
|
||||
|
||||
- Introduction to Microsoft Teams
|
||||
- Scheduling Microsoft Teams meetings
|
||||
@ -124,7 +123,7 @@ This page contains comprehensive training for Surface Hub 2S, available on deman
|
||||
|
||||
## Chapter 10 - Basic troubleshooting
|
||||
|
||||
> ![VIDEO <https://www.microsoft.com/videoplayer/embed/RE46z65>]<br>
|
||||
> [!video https://www.microsoft.com/videoplayer/embed/RE46z65]
|
||||
|
||||
- Introduction to Surface Hub troubleshooting
|
||||
- Application troubleshooting
|
||||
|
||||
@ -79,8 +79,8 @@ Groups are characterized by a scope that identifies the extent to which the grou
|
||||
|
||||
- Domain Local
|
||||
|
||||
**Note**
|
||||
In addition to these three scopes, the default groups in the **Builtin** container have a group scope of Builtin Local. This group scope and group type cannot be changed.
|
||||
> [!NOTE]
|
||||
> In addition to these three scopes, the default groups in the **Builtin** container have a group scope of Builtin Local. This group scope and group type cannot be changed.
|
||||
|
||||
|
||||
|
||||
@ -111,8 +111,8 @@ The following table lists the three group scopes and more information about each
|
||||
<td><p>Accounts from any domain in the same forest</p>
|
||||
<p>Global groups from any domain in the same forest</p>
|
||||
<p>Other Universal groups from any domain in the same forest</p></td>
|
||||
<td><p>Can be converted to Domain Local scope</p>
|
||||
<p>Can be converted to Global scope if the group is not a member of any other Universal groups</p></td>
|
||||
<td><p>Can be converted to Domain Local scope if the group is not a member of any other Universal groups</p>
|
||||
<p>Can be converted to Global scope if the group does not contain any other Universal groups</p></td>
|
||||
<td><p>On any domain in the same forest or trusting forests</p></td>
|
||||
<td><p>Other Universal groups in the same forest</p>
|
||||
<p>Domain Local groups in the same forest or trusting forests</p>
|
||||
@ -620,8 +620,8 @@ Members of the Account Operators group cannot manage the Administrator user acco
|
||||
|
||||
The Account Operators group applies to versions of the Windows Server operating system listed in the [Active Directory Default Security Groups table](#bkmk-groupstable).
|
||||
|
||||
**Note**
|
||||
By default, this built-in group has no members, and it can create and manage users and groups in the domain, including its own membership and that of the Server Operators group. This group is considered a service administrator group because it can modify Server Operators, which in turn can modify domain controller settings. As a best practice, leave the membership of this group empty, and do not use it for any delegated administration. This group cannot be renamed, deleted, or moved.
|
||||
> [!NOTE]
|
||||
> By default, this built-in group has no members, and it can create and manage users and groups in the domain, including its own membership and that of the Server Operators group. This group is considered a service administrator group because it can modify Server Operators, which in turn can modify domain controller settings. As a best practice, leave the membership of this group empty, and do not use it for any delegated administration. This group cannot be renamed, deleted, or moved.
|
||||
|
||||
|
||||
|
||||
@ -686,8 +686,8 @@ Members of the Administrators group have complete and unrestricted access to the
|
||||
|
||||
The Administrators group applies to versions of the Windows Server operating system listed in the [Active Directory Default Security Groups table](#bkmk-groupstable).
|
||||
|
||||
**Note**
|
||||
The Administrators group has built-in capabilities that give its members full control over the system. This group cannot be renamed, deleted, or moved. This built-in group controls access to all the domain controllers in its domain, and it can change the membership of all administrative groups.
|
||||
> [!NOTE]
|
||||
> The Administrators group has built-in capabilities that give its members full control over the system. This group cannot be renamed, deleted, or moved. This built-in group controls access to all the domain controllers in its domain, and it can change the membership of all administrative groups.
|
||||
|
||||
Membership can be modified by members of the following groups: the default service Administrators, Domain Admins in the domain, or Enterprise Admins. This group has the special privilege to take ownership of any object in the directory or any resource on a domain controller. This account is considered a service administrator group because its members have full access to the domain controllers in the domain.
|
||||
|
||||
@ -2056,8 +2056,8 @@ When a member of the Guests group signs out, the entire profile is deleted. This
|
||||
|
||||
Computer Configuration\\Administrative Templates\\System\\User Profiles
|
||||
|
||||
**Note**
|
||||
A Guest account is a default member of the Guests security group. People who do not have an actual account in the domain can use the Guest account. A user whose account is disabled (but not deleted) can also use the Guest account.
|
||||
> [!NOTE]
|
||||
> A Guest account is a default member of the Guests security group. People who do not have an actual account in the domain can use the Guest account. A user whose account is disabled (but not deleted) can also use the Guest account.
|
||||
|
||||
The Guest account does not require a password. You can set rights and permissions for the Guest account as in any user account. By default, the Guest account is a member of the built-in Guests group and the Domain Guests global group, which allows a user to sign in to a domain. The Guest account is disabled by default, and we recommend that it stay disabled.
|
||||
|
||||
@ -2125,8 +2125,8 @@ This security group has not changed since Windows Server 2008.
|
||||
|
||||
Members of the Hyper-V Administrators group have complete and unrestricted access to all the features in Hyper-V. Adding members to this group helps reduce the number of members required in the Administrators group, and further separates access.
|
||||
|
||||
**Note**
|
||||
Prior to Windows Server 2012, access to features in Hyper-V was controlled in part by membership in the Administrators group.
|
||||
> [!NOTE]
|
||||
> Prior to Windows Server 2012, access to features in Hyper-V was controlled in part by membership in the Administrators group.
|
||||
|
||||
|
||||
|
||||
@ -2252,8 +2252,8 @@ Members of the Incoming Forest Trust Builders group can create incoming, one-way
|
||||
|
||||
To make this determination, the Windows security system computes a trust path between the domain controller for the server that receives the request and a domain controller in the domain of the requesting account. A secured channel extends to other Active Directory domains through interdomain trust relationships. This secured channel is used to obtain and verify security information, including security identifiers (SIDs) for users and groups.
|
||||
|
||||
**Note**
|
||||
This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO).
|
||||
> [!NOTE]
|
||||
> This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO).
|
||||
|
||||
|
||||
|
||||
@ -2261,8 +2261,8 @@ For more information, see [How Domain and Forest Trusts Work: Domain and Forest
|
||||
|
||||
The Incoming Forest Trust Builders group applies to versions of the Windows Server operating system listed in the [Active Directory Default Security Groups table](#bkmk-groupstable).
|
||||
|
||||
**Note**
|
||||
This group cannot be renamed, deleted, or moved.
|
||||
> [!NOTE]
|
||||
> This group cannot be renamed, deleted, or moved.
|
||||
|
||||
|
||||
|
||||
@ -2359,16 +2359,14 @@ Members of the Network Configuration Operators group can have the following admi
|
||||
|
||||
- Enter the PIN unblock key (PUK) for mobile broadband devices that support a SIM card.
|
||||
|
||||
**Note**
|
||||
This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO).
|
||||
|
||||
> [!NOTE]
|
||||
> This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO).
|
||||
|
||||
|
||||
The Network Configuration Operators group applies to versions of the Windows Server operating system listed in the [Active Directory Default Security Groups table](#bkmk-groupstable).
|
||||
|
||||
**Note**
|
||||
This group cannot be renamed, deleted, or moved.
|
||||
|
||||
> [!NOTE]
|
||||
> This group cannot be renamed, deleted, or moved.
|
||||
|
||||
|
||||
This security group has not changed since Windows Server 2008.
|
||||
@ -2434,25 +2432,22 @@ Members of the Performance Log Users group can manage performance counters, logs
|
||||
|
||||
- Can create and modify Data Collector Sets after the group is assigned the [Log on as a batch job](/windows/device-security/security-policy-settings/log-on-as-a-batch-job) user right.
|
||||
|
||||
**Warning**
|
||||
If you are a member of the Performance Log Users group, you must configure Data Collector Sets that you create to run under your credentials.
|
||||
|
||||
> [!WARNING]
|
||||
> If you are a member of the Performance Log Users group, you must configure Data Collector Sets that you create to run under your credentials.
|
||||
|
||||
|
||||
- Cannot use the Windows Kernel Trace event provider in Data Collector Sets.
|
||||
|
||||
For members of the Performance Log Users group to initiate data logging or modify Data Collector Sets, the group must first be assigned the [Log on as a batch job](/windows/device-security/security-policy-settings/log-on-as-a-batch-job) user right. To assign this user right, use the Local Security Policy snap-in in Microsoft Management Console.
|
||||
|
||||
**Note**
|
||||
This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO).
|
||||
|
||||
> [!NOTE]
|
||||
> This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO).
|
||||
|
||||
|
||||
The Performance Log Users group applies to versions of the Windows Server operating system listed in the [Active Directory Default Security Groups table](#bkmk-groupstable).
|
||||
|
||||
**Note**
|
||||
This account cannot be renamed, deleted, or moved.
|
||||
|
||||
> [!NOTE]
|
||||
> This account cannot be renamed, deleted, or moved.
|
||||
|
||||
|
||||
This security group has not changed since Windows Server 2008.
|
||||
@ -2524,13 +2519,13 @@ Specifically, members of this security group:
|
||||
|
||||
- Cannot create or modify Data Collector Sets.
|
||||
|
||||
**Warning**
|
||||
You cannot configure a Data Collector Set to run as a member of the Performance Monitor Users group.
|
||||
> [!WARNING]
|
||||
> You cannot configure a Data Collector Set to run as a member of the Performance Monitor Users group.
|
||||
|
||||
|
||||
|
||||
**Note**
|
||||
This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO). This group cannot be renamed, deleted, or moved.
|
||||
> [!NOTE]
|
||||
> This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO). This group cannot be renamed, deleted, or moved.
|
||||
|
||||
|
||||
|
||||
@ -2590,14 +2585,12 @@ This security group has not changed since Windows Server 2008.
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-pre-ws2kcompataccess"></a>Pre–Windows 2000 Compatible Access
|
||||
|
||||
Members of the Pre–Windows 2000 Compatible Access group have Read access for all users and groups in the domain. This group is provided for backward compatibility for computers running Windows NT 4.0 and earlier. By default, the special identity group, Everyone, is a member of this group. Add users to this group only if they are running Windows NT 4.0 or earlier.
|
||||
|
||||
**Warning**
|
||||
This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO).
|
||||
|
||||
> [!WARNING]
|
||||
> This group appears as a SID until the domain controller is made the primary domain controller and it holds the operations master role (also known as flexible single master operations or FSMO).
|
||||
|
||||
|
||||
The Pre–Windows 2000 Compatible Access group applies to versions of the Windows Server operating system listed in the [Active Directory Default Security Groups table](#bkmk-groupstable).
|
||||
@ -3243,8 +3236,8 @@ This security group was introduced in Windows Server 2012, and it has not chang
|
||||
|
||||
Computers that are members of the Replicator group support file replication in a domain. Windows Server operating systems use the File Replication service (FRS) to replicate system policies and logon scripts stored in the System Volume (SYSVOL). Each domain controller keeps a copy of SYSVOL for network clients to access. FRS can also replicate data for the Distributed File System (DFS), synchronizing the content of each member in a replica set as defined by DFS. FRS can copy and maintain shared files and folders on multiple servers simultaneously. When changes occur, content is synchronized immediately within sites and by a schedule between sites.
|
||||
|
||||
**Important**
|
||||
In Windows Server 2008 R2, FRS cannot be used for replicating DFS folders or custom (non-SYSVOL) data. A Windows Server 2008 R2 domain controller can still use FRS to replicate the contents of a SYSVOL shared resource in a domain that uses FRS for replicating the SYSVOL shared resource between domain controllers.
|
||||
> [!WARNING]
|
||||
> In Windows Server 2008 R2, FRS cannot be used for replicating DFS folders or custom (non-SYSVOL) data. A Windows Server 2008 R2 domain controller can still use FRS to replicate the contents of a SYSVOL shared resource in a domain that uses FRS for replicating the SYSVOL shared resource between domain controllers.
|
||||
|
||||
However, Windows Server 2008 R2 servers cannot use FRS to replicate the contents of any replica set apart from the SYSVOL shared resource. The DFS Replication service is a replacement for FRS, and it can be used to replicate the contents of a SYSVOL shared resource, DFS folders, and other custom (non-SYSVOL) data. You should migrate all non-SYSVOL FRS replica sets to DFS Replication. For more information, see:
|
||||
|
||||
@ -3489,8 +3482,8 @@ For more information about this security group, see [Terminal Services License S
|
||||
|
||||
The Terminal Server License Servers group applies to versions of the Windows Server operating system listed in the [Active Directory Default Security Groups table](#bkmk-groupstable).
|
||||
|
||||
**Note**
|
||||
This group cannot be renamed, deleted, or moved.
|
||||
> [!NOTE]
|
||||
> This group cannot be renamed, deleted, or moved.
|
||||
|
||||
|
||||
|
||||
@ -3624,9 +3617,8 @@ Members of this group have access to the computed token GroupsGlobalAndUniversal
|
||||
|
||||
The Windows Authorization Access group applies to versions of the Windows Server operating system listed in the [Active Directory Default Security Groups table](#bkmk-groupstable).
|
||||
|
||||
**Note**
|
||||
This group cannot be renamed, deleted, or moved.
|
||||
|
||||
> [!NOTE]
|
||||
> This group cannot be renamed, deleted, or moved.
|
||||
|
||||
|
||||
This security group has not changed since Windows Server 2008.
|
||||
@ -3704,8 +3696,8 @@ The WinRMRemoteWMIUsers\_ group applies to versions of the Windows Server operat
|
||||
|
||||
In Windows Server 2012, the Access Denied Assistance functionality adds the Authenticated Users group to the local WinRMRemoteWMIUsers\_\_ group. Therefore, when the Access Denied Assistance functionality is enabled, all authenticated users who have Read permissions to the file share can view the file share permissions.
|
||||
|
||||
**Note**
|
||||
The WinRMRemoteWMIUsers\_ group allows running Windows PowerShell commands remotely whereas the [Remote Management Users](#bkmk-remotemanagementusers) group is generally used to allow users to manage servers by using the Server Manager console.
|
||||
> [!NOTE]
|
||||
> The WinRMRemoteWMIUsers\_ group allows running Windows PowerShell commands remotely whereas the [Remote Management Users](#bkmk-remotemanagementusers) group is generally used to allow users to manage servers by using the Server Manager console.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@
|
||||
|
||||
## [Encrypted Hard Drive](encrypted-hard-drive.md)
|
||||
|
||||
## [Kernel DMA Protection for Thunderbolt™ 3](kernel-dma-protection-for-thunderbolt.md)
|
||||
## [Kernel DMA Protection](kernel-dma-protection-for-thunderbolt.md)
|
||||
|
||||
## [Protect your enterprise data using Windows Information Protection (WIP)](windows-information-protection\protect-enterprise-data-using-wip.md)
|
||||
### [Create a WIP policy using Microsoft Intune](windows-information-protection\overview-create-wip-policy.md)
|
||||
|
||||
@ -22,7 +22,7 @@ Learn more about how to secure documents and other data across your organization
|
||||
|-|-|
|
||||
| [BitLocker](bitlocker/bitlocker-overview.md)| Provides information about BitLocker, which is a data protection feature that integrates with the operating system and addresses the threats of data theft or exposure from lost, stolen, or inappropriately decommissioned computers. |
|
||||
| [Encrypted Hard Drive](encrypted-hard-drive.md)| Encrypted Hard Drive uses the rapid encryption that is provided by BitLocker Drive Encryption to enhance data security and management. |
|
||||
| [Kernel DMA Protection for Thunderbolt™ 3](kernel-dma-protection-for-thunderbolt.md)| Kernel DMA Protection protects PCs against drive-by Direct Memory Access (DMA) attacks using PCI hot plug devices connected to Thunderbolt™ 3 ports. |
|
||||
| [Kernel DMA Protection](kernel-dma-protection-for-thunderbolt.md)| Kernel DMA Protection protects PCs against drive-by Direct Memory Access (DMA) attacks using PCI hot plug devices connected to PCI accessible ports, such as Thunderbolt™ 3 ports. |
|
||||
| [Protect your enterprise data using Windows Information Protection (WIP)](windows-information-protection/protect-enterprise-data-using-wip.md)|Provides info about how to create a Windows Information Protection policy that can help protect against potential corporate data leakage.|
|
||||
| [Secure the Windows 10 boot process](secure-the-windows-10-boot-process.md)| Windows 10 supports features to help prevent rootkits and bootkits from loading during the startup process. |
|
||||
| [Trusted Platform Module](tpm/trusted-platform-module-top-node.md)| Trusted Platform Module (TPM) technology is designed to provide hardware-based, security-related functions. A TPM chip is a secure crypto-processor that helps you with actions such as generating, storing, and limiting the use of cryptographic keys. |
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
|
||||
## [Understand malware & other threats](understanding-malware.md)
|
||||
|
||||
### [Prevent malware infection](prevent-malware-infection.md)
|
||||
|
||||
### [Malware names](malware-naming.md)
|
||||
|
||||
### [Coin miners](coinminer-malware.md)
|
||||
|
||||
### [Exploits and exploit kits](exploits-malware.md)
|
||||
@ -30,6 +26,10 @@
|
||||
|
||||
### [Worms](worms-malware.md)
|
||||
|
||||
## [Prevent malware infection](prevent-malware-infection.md)
|
||||
|
||||
## [Malware naming convention](malware-naming.md)
|
||||
|
||||
## [How Microsoft identifies malware and PUA](criteria.md)
|
||||
|
||||
## [Submit files for analysis](submission-guide.md)
|
||||
|
||||
@ -15,9 +15,11 @@ ms.topic: conceptual
|
||||
---
|
||||
# Security intelligence
|
||||
|
||||
Here you will find information about different types of malware, safety tips on how you can protect your organization, and resources for industry collaboration programs
|
||||
Here you will find information about different types of malware, safety tips on how you can protect your organization, and resources for industry collaboration programs.
|
||||
|
||||
* [Understand malware & other threats](understanding-malware.md)
|
||||
* [Prevent malware infection](prevent-malware-infection.md)
|
||||
* [Malware naming convention](malware-naming.md)
|
||||
* [How Microsoft identifies malware and PUA](criteria.md)
|
||||
* [Submit files for analysis](submission-guide.md)
|
||||
* [Safety Scanner download](safety-scanner-download.md)
|
||||
|
||||
@ -50,6 +50,7 @@ The following table summarizes what happens with Microsoft Defender Antivirus wh
|
||||
If you are Using Windows Server, version 1803 and Windows 2019, you can enable passive mode by setting this registry key:
|
||||
- Path: `HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection`
|
||||
- Name: ForceDefenderPassiveMode
|
||||
- Type: REG_DWORD
|
||||
- Value: 1
|
||||
|
||||
See [Microsoft Defender Antivirus on Windows Server 2016 and 2019](microsoft-defender-antivirus-on-windows-server-2016.md) for key differences and management options for Windows Server installations.
|
||||
|
||||
@ -399,7 +399,7 @@ GUID: `e6db77e5-3df2-4cf1-b95a-636979351e5b`
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Attack surface reduction FAQ](attack-surface-reduction.md)
|
||||
- [Attack surface reduction FAQ](attack-surface-reduction-faq.md)
|
||||
|
||||
- [Enable attack surface reduction rules](enable-attack-surface-reduction.md)
|
||||
|
||||
|
||||
@ -94,6 +94,12 @@ You can partner with Microsoft Threat Experts who can be engaged directly from w
|
||||
|
||||
4. Enter the email address that you'd like to use to correspond with Microsoft Threat Experts.
|
||||
|
||||
> [!NOTE]
|
||||
> Customers with Premier Support subscription mapped to their Office 365 license can track the status of their Experts on Demand cases through Microsoft Services Hub. Watch this video for a quick overview of the Microsoft Services Hub.
|
||||
|
||||
>[!VIDEO https://www.microsoft.com/videoplayer/embed/RE4pk9f]
|
||||
<BR>
|
||||
|
||||
## Sample investigation topics that you can consult with Microsoft Threat Experts
|
||||
|
||||
**Alert information**
|
||||
|
||||
@ -85,9 +85,9 @@ You'll need to take the following steps if you choose to onboard servers through
|
||||
Microsoft Defender ATP integrates with System Center Endpoint Protection. The integration provides visibility to malware detections and to stop propagation of an attack in your organization by banning potentially malicious files or suspected malware.
|
||||
|
||||
The following steps are required to enable this integration:
|
||||
- Install the [January 2017 anti-malware platform update for Endpoint Protection clients](https://support.microsoft.com/help/3209361/january-2017-anti-malware-platform-update-for-endpoint-protection-clie)
|
||||
- Install the [January 2017 anti-malware platform update for Endpoint Protection clients](https://support.microsoft.com/help/3209361/january-2017-anti-malware-platform-update-for-endpoint-protection-clie).
|
||||
|
||||
- Configure the SCEP client Cloud Protection Service membership to the **Advanced** setting
|
||||
- Configure the SCEP client Cloud Protection Service membership to the **Advanced** setting.
|
||||
|
||||
|
||||
### Turn on Server monitoring from the Microsoft Defender Security Center portal
|
||||
@ -156,6 +156,7 @@ Support for Windows Server, provide deeper insight into activities happening on
|
||||
1. Set the following registry entry:
|
||||
- Path: `HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection`
|
||||
- Name: ForceDefenderPassiveMode
|
||||
- Type: REG_DWORD
|
||||
- Value: 1
|
||||
|
||||
1. Run the following PowerShell command to verify that the passive mode was configured:
|
||||
@ -185,7 +186,7 @@ The following capabilities are included in this integration:
|
||||
> Automated onboarding is only applicable for Windows Server 2008 R2 SP1, Windows Server 2012 R2, and Windows Server 2016.
|
||||
|
||||
- Servers monitored by Azure Security Center will also be available in Microsoft Defender ATP - Azure Security Center seamlessly connects to the Microsoft Defender ATP tenant, providing a single view across clients and servers. In addition, Microsoft Defender ATP alerts will be available in the Azure Security Center console.
|
||||
- Server investigation - Azure Security Center customers can access Microsoft Defender Security Center to perform detailed investigation to uncover the scope of a potential breach
|
||||
- Server investigation - Azure Security Center customers can access Microsoft Defender Security Center to perform detailed investigation to uncover the scope of a potential breach.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> - When you use Azure Security Center to monitor servers, a Microsoft Defender ATP tenant is automatically created. The Microsoft Defender ATP data is stored in Europe by default.
|
||||
@ -233,7 +234,7 @@ To offboard the server, you can use either of the following methods:
|
||||
|
||||
2. Open an elevated PowerShell and run the following command. Use the Workspace ID you obtained and replacing `WorkspaceID`:
|
||||
|
||||
```
|
||||
```powershell
|
||||
# Load agent scripting object
|
||||
$AgentCfg = New-Object -ComObject AgentConfigManager.MgmtSvcCfg
|
||||
# Remove OMS Workspace
|
||||
|
||||
Binary file not shown.
Binary file not shown.
@ -50,7 +50,7 @@ File, folder, and process exclusions support the following wildcards:
|
||||
|
||||
Wildcard | Description | Example | Matches | Does not match
|
||||
---|---|---|---|---
|
||||
\* | Matches any number of any characters including none (note that when this wildcard is used inside a path it will substitute only one folder) | `/var/\*/\*.log` | `/var/log/system.log` | `/var/log/nested/system.log`
|
||||
\* | Matches any number of any characters including none (note that when this wildcard is used inside a path it will substitute only one folder) | `/var/*/*.log` | `/var/log/system.log` | `/var/log/nested/system.log`
|
||||
? | Matches any single character | `file?.log` | `file1.log`<br/>`file2.log` | `file123.log`
|
||||
|
||||
## How to configure the list of exclusions
|
||||
|
||||
@ -65,5 +65,11 @@ The option to **Consult a threat expert** is available in several places in the
|
||||
- <i>**File page actions menu**</i><BR>
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> Customers with Premier Support subscription mapped to their Office 365 license can track the status of their Experts on Demand cases through Microsoft Services Hub. Watch this video for a quick overview of the Microsoft Services Hub.
|
||||
<BR>
|
||||
>[!VIDEO https://www.microsoft.com/videoplayer/embed/RE4pk9f]
|
||||
<BR>
|
||||
|
||||
## Related topic
|
||||
- [Configure Microsoft Threat Experts capabilities](configure-microsoft-threat-experts.md)
|
||||
|
||||
Reference in New Issue
Block a user