Merge branch 'master' into v-tea-locpri
@ -786,11 +786,6 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/controlled-folders-exploit-guard.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/controlled-folders",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/customize-attack-surface-reduction",
|
||||
"redirect_document_id": true
|
||||
@ -881,11 +876,6 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/network-protection-exploit-guard.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/network-protection",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/threat-protection/windows-defender-exploit-guard/prerelease.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/prerelease",
|
||||
"redirect_document_id": true
|
||||
|
@ -53,6 +53,8 @@
|
||||
# Update and recovery
|
||||
## [Join the Windows Insider program](hololens-insider.md)
|
||||
## [Restart, reset, or recover](hololens-recovery.md)
|
||||
## [Known issues](hololens-known-issues.md)
|
||||
## [Frequently asked questions](hololens-faq.md)
|
||||
|
||||
# [Give us feedback](hololens-feedback.md)
|
||||
# [Change history for Microsoft HoloLens documentation](change-history-hololens.md)
|
||||
|
@ -9,6 +9,7 @@ ms.topic: article
|
||||
ms.localizationpriority: high
|
||||
ms.date: 10/30/2019
|
||||
ms.reviewer: scooley
|
||||
audience: ITPro
|
||||
manager: jarrettr
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
@ -59,22 +60,22 @@ If you're having trouble after reading these topics, see [Troubleshooting](#trou
|
||||
|
||||
- Scale/rotation/translation animation on individual objects
|
||||
- Skeletal (rigged) animation with skinning
|
||||
- Maximum of 4 influences per vertex
|
||||
- Maximum of 4 influences per vertex
|
||||
|
||||
### Materials
|
||||
|
||||
- Lambert and Phong materials are supported, with adjustable parameters
|
||||
- Supported material properties for Lambert
|
||||
- Main Texture (RGB + Alpha Test)
|
||||
- Diffuse Color (RGB)
|
||||
- Ambient Color (RGB)
|
||||
- Main Texture (RGB + Alpha Test)
|
||||
- Diffuse Color (RGB)
|
||||
- Ambient Color (RGB)
|
||||
- Supported material properties for Phong
|
||||
- Main Texture (RGB + Alpha Test)
|
||||
- Diffuse Color (RGB)
|
||||
- Ambient Color (RGB)
|
||||
- Specular Color (RGB)
|
||||
- Shininess
|
||||
- Reflectivity
|
||||
- Main Texture (RGB + Alpha Test)
|
||||
- Diffuse Color (RGB)
|
||||
- Ambient Color (RGB)
|
||||
- Specular Color (RGB)
|
||||
- Shininess
|
||||
- Reflectivity
|
||||
- Custom materials are not supported
|
||||
- Maximum of one material per mesh
|
||||
- Maximum of one material layer
|
||||
|
@ -35,7 +35,6 @@ You can install your own applications on HoloLens either by using the Device Por
|
||||
> Make sure to reference any associated dependency and certificate files.
|
||||
|
||||
1. Select **Go**.
|
||||
|
||||

|
||||
|
||||
### Deploying from Microsoft Visual Studio 2015
|
||||
@ -44,7 +43,6 @@ You can install your own applications on HoloLens either by using the Device Por
|
||||
1. Open the project's **Properties**.
|
||||
1. Select the following build configuration: **Master/x86/Remote Machine**.
|
||||
1. When you select **Remote Machine**:
|
||||
|
||||
- Make sure the address points to the Wi-Fi IP address of your HoloLens.
|
||||
- Set authentication to **Universal (Unencrypted Protocol)**.
|
||||
1. Build your solution.
|
||||
|
217
devices/hololens/hololens-FAQ.md
Normal file
@ -0,0 +1,217 @@
|
||||
---
|
||||
title: Frequently asked questions about HoloLens 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
|
||||
ms.sitesec: library
|
||||
author: Teresa-Motiv
|
||||
ms.author: v-tea
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/30/2019
|
||||
ms.reviewer:
|
||||
manager: jarrettr
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# HoloLens and holograms: Frequently asked questions
|
||||
|
||||
Here are some answers to questions you might have about using HoloLens, placing holograms, working 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).
|
||||
|
||||
For tips about wearing your HoloLens, see [HoloLens fit and comfort: FAQ](https://support.microsoft.com/help/13405/hololens-fit-and-comfort-faq).
|
||||
|
||||
This FAQ 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)
|
||||
- [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)
|
||||
- [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)
|
||||
- [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)
|
||||
- [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)
|
||||
|
||||
## 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.
|
||||
- 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**.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## 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."
|
||||
|
||||
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.
|
||||
|
||||
If you see these messages often, try the following:
|
||||
|
||||
- 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**.
|
||||
- Try moving more slowly.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I'm not seeing the holograms 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:
|
||||
|
||||
- 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**.
|
||||
|
||||
> [!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
|
||||
|
||||
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.
|
||||
- Don't place holograms on black or reflective surfaces.
|
||||
- Make sure you're in a well-lit room without 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.
|
||||
|
||||
Holograms can also be blocked or encased by other holograms or by objects such as walls. If this happens, try one of the following:
|
||||
|
||||
- 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 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.
|
||||
|
||||
[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 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.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## When I place a hologram on a wall, it 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:
|
||||
|
||||
- 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.
|
||||
- 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.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I'm getting a low disk space error
|
||||
|
||||
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?](hololens-find-and-save-files.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.)
|
||||
|
||||
[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).
|
||||
|
||||
[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).
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I'm having problems pairing or using a Bluetooth device
|
||||
|
||||
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.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I'm having problems with the HoloLens clicker
|
||||
|
||||
Use the [clicker](hololens1-clicker.md) to select, scroll, move, and resize holograms. Additional clicker gestures may vary from app to app.
|
||||
|
||||
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 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).
|
||||
|
||||
[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:
|
||||
|
||||
- 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.
|
||||
- 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.
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## My HoloLens isn't running well, is unresponsive, or won't start
|
||||
|
||||
If your device isn't performing properly, see [Restart, reset, or recover HoloLens](hololens-recovery.md).
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## How do I delete all spaces?
|
||||
|
||||
*Coming soon*
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
## I cannot find or use the keyboard to type in the HoloLens 2 Emulator
|
||||
|
||||
*Coming soon*
|
||||
|
||||
[Back to list](#list)
|
@ -1,11 +1,12 @@
|
||||
---
|
||||
title: Commercial features
|
||||
description: The Microsoft HoloLens Commercial Suite includes features that make it easier for businesses to manage HoloLens devices. HoloLens 2 devices are equipped with commercial features by default.
|
||||
keywords: HoloLens, commercial, features, mdm, mobile device management, kiosk mode
|
||||
author: scooley
|
||||
ms.author: scooley
|
||||
ms.date: 08/26/19
|
||||
ms.date: 08/26/2019
|
||||
ms.topic: article
|
||||
keywords: HoloLens, commercial, features, mdm, mobile device management, kiosk mode
|
||||
audience: ITPro
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
@ -53,7 +54,7 @@ HoloLens (1st gen) came with two licensing options, the developer license and a
|
||||
|Ability to block unenrollment | |✔️ |✔️ |
|
||||
|Cert-based corporate Wi-Fi access | |✔️ |✔️ |
|
||||
|Microsoft Store (Consumer) |Consumer |Filter by using MDM |Filter by using MDM |
|
||||
[Business Store Portal](https://docs.microsoft.com/microsoft-store/working-with-line-of-business-apps) | |✔️ |✔️ |
|
||||
|[Business Store Portal](https://docs.microsoft.com/microsoft-store/working-with-line-of-business-apps) | |✔️ |✔️ |
|
||||
|**Security and identity** | | | |
|
||||
|Sign in by using Azure Active Directory (AAD) account |✔️ |✔️ |✔️ |
|
||||
|Sign in by using Microsoft Account (MSA) |✔️ |✔️ |✔️ |
|
||||
|
@ -50,6 +50,7 @@ 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).
|
||||
|
||||
|
@ -1,16 +1,19 @@
|
||||
---
|
||||
title: Enroll HoloLens in MDM (HoloLens)
|
||||
title: Enroll HoloLens in MDM
|
||||
description: Enroll HoloLens in mobile device management (MDM) for easier management of multiple devices.
|
||||
ms.prod: hololens
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.assetid: 2a9b3fca-8370-44ec-8b57-fb98b8d317b0
|
||||
author: scooley
|
||||
ms.author: scooley
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 07/15/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Enroll HoloLens in MDM
|
||||
@ -39,3 +42,7 @@ When auto-enrollment is enabled, no additional manual enrollment is needed. When
|
||||
1. Upon successful authentication to the MDM server, a success message is shown.
|
||||
|
||||
Your device is now enrolled with your MDM server. The device will need to restart to acquire policies, certificates, and apps. The Settings app will now reflect that the device is enrolled in device management.
|
||||
|
||||
## Unenroll HoloLens from Intune
|
||||
|
||||
You cannot [unenroll](https://docs.microsoft.com/intune-user-help/unenroll-your-device-from-intune-windows) HoloLens from Intune remotely. If the administrator unenrolls the device using MDM, the device will age out of the Intune dashboard.
|
@ -77,7 +77,7 @@ The cameras can see no closer than 15cm from an object.
|
||||
|
||||
### Surfaces in a space
|
||||
|
||||
Strongly reflective surfaces will likely look different depending on the angle, which affects tracking. Think of a brand new car—when you move around it, light reflects and you see different objects in the surface as you move. To the tracker, the different objects reflected in the surface represent a changing environment, and the device loses tracking.
|
||||
Strongly reflective surfaces will likely look different depending on the angle, which affects tracking. Think of a brand new car - when you move around it, light reflects and you see different objects in the surface as you move. To the tracker, the different objects reflected in the surface represent a changing environment, and the device loses tracking.
|
||||
|
||||
Less shiny objects are easier to track against.
|
||||
|
||||
|
@ -80,4 +80,3 @@ To easily direct other people (such as co-workers, Microsoft staff, [forum](http
|
||||
1. Enter your feedback.
|
||||
1. If you are reporting a reproducible issue, you can select **Reproduce**. Without closing Feedback Hub, reproduce the issue. After you finish, come back to Feedback Hub and select **I’m done**. The app adds a mixed reality capture of your repro and relevant diagnostic logs to your feedback.
|
||||
1. Select **Post feedback**, and you’re done.
|
||||
|
||||
|
@ -12,6 +12,9 @@ author: v-miegge
|
||||
ms.author: v-miegge
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Find and save files on HoloLens
|
||||
|
@ -10,6 +10,9 @@ ms.localizationpriority: medium
|
||||
ms.date: 10/23/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Insider preview for Microsoft HoloLens
|
||||
|
169
devices/hololens/hololens-known-issues.md
Normal file
@ -0,0 +1,169 @@
|
||||
---
|
||||
title: HoloLens known issues
|
||||
description: This is the list of known issues that may affect HoloLens developers.
|
||||
keywords: troubleshoot, known issue, help
|
||||
author: mattzmsft
|
||||
ms.author: mazeller
|
||||
ms.date: 8/30/2019
|
||||
ms.topic: article
|
||||
HoloLens and holograms: Frequently asked questions
|
||||
manager: jarrettr
|
||||
ms.prod: hololens
|
||||
appliesto:
|
||||
- HoloLens 1
|
||||
---
|
||||
|
||||
# HoloLens known issues
|
||||
|
||||
This is the current list of known issues for HoloLens that affect developers. Check here first if you are seeing an odd behavior. This list will be kept updated as new issues are discovered or reported, or as issues are addressed in future HoloLens software updates.
|
||||
|
||||
## 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.
|
||||
|
||||
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.
|
||||
|
||||
Issue root-cause: Users who used Visual Studio 2015 or early releases of Visual Studio 2017 to deploy and debug applications on their HoloLens and then subsequently used the latest versions of Visual Studio 2017 or Visual Studio 2019 with the same HoloLens will be affected. The newer releases of Visual Studio deploy a new version of a component, but files from the older version are left over on the device, causing the newer version to fail. This causes the following error message: DEP0100: Please ensure that target device has developer mode enabled. Could not obtain a developer license on \<ip\> due to error 80004005.
|
||||
|
||||
### Workaround
|
||||
|
||||
Our team is currently working on a fix. In the meantime, you can use the following steps to work around the issue and help unblock deployment and debugging:
|
||||
|
||||
1. Open Visual Studio
|
||||
1. Select **File** > **New** > **Project**.
|
||||
1. Select **Visual C#** > **Windows Desktop** > **Console App (.NET Framework)**.
|
||||
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
|
||||
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.
|
||||
|
||||
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 (\*.\*)**.
|
||||
1. Select both SirepClient.dll and SshClient.dll, and Select **Add**.
|
||||
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
|
||||
using Microsoft.Tools.Deploy;
|
||||
using System.Net;
|
||||
```
|
||||
|
||||
1. Inside of `static void Main(...)`, add the following code:
|
||||
|
||||
``` PowerShell
|
||||
RemoteDeployClient client = RemoteDeployClient.CreateRemoteDeployClient();
|
||||
client.Connect(new ConnectionOptions()
|
||||
{
|
||||
Credentials = new NetworkCredential("DevToolsUser", string.Empty),
|
||||
IPAddress = IPAddress.Parse(args[0])
|
||||
});
|
||||
client.RemoteDevice.DeleteFile(@"C:\Data\Users\DefaultAccount\AppData\Local\DevelopmentFiles\VSRemoteTools\x86\CoreCLR\mscorlib.ni.dll");
|
||||
```
|
||||
|
||||
1. Select **Build** > **Build Solution**.
|
||||
1. Open a Command Prompt Window and cd to the folder that contains the compiled .exe file (for example, C:\MyProjects\HoloLensDeploymentFix\bin\Debug)
|
||||
1. Run the executable and provide the device's IP address as a command-line argument. (If connected using USB, you can use 127.0.0.1, otherwise use the device’s Wi-Fi IP address.) For example, "HoloLensDeploymentFix 127.0.0.1"
|
||||
|
||||
1. After the tool has exited without any messages (this should only take a few seconds), you will now be able to deploy and debug from Visual Studio 2017 or newer. Continued use of the tool is not necessary.
|
||||
|
||||
We will provide further updates as they become available.
|
||||
|
||||
## Issues launching the Microsoft Store and apps on HoloLens
|
||||
|
||||
> [!NOTE]
|
||||
> Last Update: 4/2 @ 10 AM - Issue resolved.
|
||||
|
||||
You may experience issues when trying to launch the Microsoft Store and apps on HoloLens. We've determined that the issue occurs when background app updates deploy a newer version of framework packages in specific sequences while one or more of their dependent apps are still running. In this case, an automatic app update delivered a new version of the .NET Native Framework (version 10.0.25531 to 10.0.27413) caused the apps that are running to not correctly update for all running apps consuming the prior version of the framework. The flow for framework update is as follows:
|
||||
|
||||
1. The new framework package is downloaded from the store and installed
|
||||
1. All apps using the older framework are ‘updated’ to use the newer version
|
||||
|
||||
If step 2 is interrupted before completion then any apps for which the newer framework wasn’t registered will fail to launch from the start menu. We believe any app on HoloLens could be affected by this issue.
|
||||
|
||||
Some users have reported that closing hung apps and launching other apps such as Feedback Hub, 3D Viewer or Photos resolves the issue for them—however, this does not work 100% of the time.
|
||||
|
||||
We have root caused that this issue was not caused the update itself, but a bug in the OS that resulted in the .NET Native framework update being handled incorrectly. We are pleased to announce that we have identified a fix and have released an update (OS version 17763.380) containing the fix.
|
||||
|
||||
To see if your device can take the update, please:
|
||||
|
||||
1. Go to the Settings app and open **Update & Security**.
|
||||
1. Select **Check for Updates**.
|
||||
1. If update to 17763.380 is available, please update to this build to receive the fix for the App Hang bug
|
||||
1. Upon updating to this version of the OS, the Apps should work as expected.
|
||||
|
||||
Additionally, as we do with every HoloLens OS release, we have posted the FFU image to the [Microsoft Download Center](https://aka.ms/hololensdownload/10.0.17763.380).
|
||||
|
||||
If you would not like to take the update, we have released a new version of the Microsoft Store UWP app as of 3/29. After you have the updated version of the Store:
|
||||
|
||||
1. Open the Store and confirm that it loads.
|
||||
1. Use the bloom gesture to open the menu.
|
||||
1. Attempt to open previously broken apps.
|
||||
1. If it still cannot be launched, tap and hold the icon of the broken app and select uninstall.
|
||||
1. Resinstall these apps from the store.
|
||||
|
||||
If your device is still unable to load apps, you can sideload a version of the .NET Native Framework and Runtime through the download center by following these steps:
|
||||
|
||||
1. Please download [this zip file](https://download.microsoft.com/download/8/5/C/85C23745-794C-419D-B8D7-115FBCCD6DA7/netfx_1.7.zip) from the Microsoft Download Center. Unzipping will produce two files. Microsoft.NET.Native.Runtime.1.7.appx and Microsoft.NET.Native.Framework.1.7.appx
|
||||
1. Please verify that your device is dev unlocked. If you haven’t done that before the instructions to do that are [here](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal).
|
||||
1. You then want to get into the Windows Device Portal. Our recommendation is to do this over USB and you would do that by typing http://127.0.0.1:10080 into your browser.
|
||||
1. After you have the Windows Device Portal up we need you to “side load” the two files that you downloaded. To do that you need to go down the left side bar until you get to the **Apps** section and select **Apps**.
|
||||
1. You will then see a screen that is similar to the below. You want to go to the section that says **Install App** and browse to where you unzipped those two APPX files. You can only do one at a time, so after you select the first one, then click on “Go” under the Deploy section. Then do this for the second APPX file.
|
||||
|
||||

|
||||
1. At this point we believe your applications should start working again and that you can also get to the Store.
|
||||
1. In some cases, it is necessary run the additional step of launching the 3D Viewer app before affected apps will launch.
|
||||
|
||||
We appreciate your patience as we have gone through the process to get this issue resolved, and we look forward to continued working with our community to create successful Mixed Reality experiences.
|
||||
|
||||
## Connecting to WiFi
|
||||
|
||||
During HoloLens Setup, there is a credential timeout of 2 minutes. The username/password needs to be entered within 2 minutes otherwise the username field will be automatically cleared.
|
||||
|
||||
We recommend using a Bluetooth keyboard for entering long passwords.
|
||||
|
||||
> [!NOTE]
|
||||
> If the wrong network is selected during HoloLens Setup, the device will need to be fully reset. Instructions can be found [here.](hololens-restart-recover.md)
|
||||
|
||||
## Device Update
|
||||
|
||||
- 30 seconds after a new update, the shell may disappear one time. Please perform the **bloom** gesture to resume your session.
|
||||
|
||||
## Visual Studio
|
||||
|
||||
- See [Install the tools](https://docs.microsoft.com/windows/mixed-reality/install-the-tools) for the most up-to-date version of Visual Studio that is recommended for HoloLens development.
|
||||
- When deploying an app from Visual Studio to your HoloLens, you may see the error: **The requested operation cannot be performed on a file with a user-mapped section open. (Exception from HRESULT: 0x800704C8)**. If this happens, try again and your deployment will generally succeed.
|
||||
|
||||
## Emulator
|
||||
|
||||
- Not all apps in the Microsoft Store are compatible with the emulator. For example, Young Conker and Fragments are not playable on the emulator.
|
||||
- You cannot use the PC webcam in the Emulator.
|
||||
- The Live Preview feature of the Windows Device Portal does not work with the emulator. You can still capture Mixed Reality videos and images.
|
||||
|
||||
## Unity
|
||||
|
||||
- See [Install the tools](https://docs.microsoft.com/windows/mixed-reality/install-the-tools) for the most up-to-date version of Unity recommended for HoloLens development.
|
||||
- Known issues with the Unity HoloLens Technical Preview are documented in the [HoloLens Unity forums](https://forum.unity3d.com/threads/known-issues.394627/).
|
||||
|
||||
## Windows Device Portal
|
||||
|
||||
- The Live Preview feature in Mixed Reality capture may exhibit several seconds of latency.
|
||||
- On the Virtual Input page, the Gesture and Scroll controls under the Virtual Gestures section are not functional. Using them will have no effect. The virtual keyboard on the same page works correctly.
|
||||
- After enabling Developer Mode in Settings, it may take a few seconds before the switch to turn on the Device Portal is enabled.
|
||||
|
||||
## API
|
||||
|
||||
- If the application sets the [focus point](https://docs.microsoft.com/windows/mixed-reality/focus-point-in-unity) behind the user or the normal to camera.forward, holograms will not appear in Mixed Reality Capture photos or videos. Until this bug is fixed in Windows, if applications actively set the [focus point](https://docs.microsoft.com/windows/mixed-reality/focus-point-in-unity) they should ensure the plane normal is set opposite camera-forward (for example, normal = -camera.forward).
|
||||
|
||||
## Xbox Wireless Controller
|
||||
|
||||
- Xbox Wireless Controller S must be updated before it can be used with HoloLens. Ensure you are [up to date](https://support.xbox.com/xbox-one/accessories/update-controller-for-stereo-headset-adapter) before attempting to pair your controller with a HoloLens.
|
||||
- If you reboot your HoloLens while the Xbox Wireless Controller is connected, the controller will not automatically reconnect to HoloLens. The Guide button light will flash slowly until the controller powers off after 3 minutes. To reconnect your controller immediately, power off the controller by holding the Guide button until the light turns off. When you power your controller on again, it will reconnect to HoloLens.
|
||||
- If your HoloLens enters standby while the Xbox Wireless Controller is connected, any input on the controller will wake the HoloLens. You can prevent this by powering off your controller when you are done using it.
|
@ -21,6 +21,8 @@ It's common to share one HoloLens with many people or to have many people share
|
||||
|
||||
## Share with multiple people, each using their own account
|
||||
|
||||
**Prerequisite**: The HoloLens device must be running Windows 10, version 1803 or later. HoloLens (1st gen) also need to be [upgraded to Windows Holographic for Business](hololens-upgrade-enterprise.md).
|
||||
|
||||
When they use their own Azure Active Directory (Azure AD) accounts, multiple users can each keep their own user settings and user data on the device.
|
||||
|
||||
To make sure that multiple people can use their own accounts on your HoloLens, follow these steps to configure it:
|
||||
|
@ -27,10 +27,10 @@ Area|HoloLens (1st gen)|HoloLens 2
|
||||
|
||||
## Notes and related topics
|
||||
|
||||
[Frequently asked questions about using Skype for HoloLens](https://support.skype.com/en/faq/FA34641/frequently-asked-questions-about-using-skype-for-hololens)
|
||||
[Frequently asked questions about using Skype for HoloLens](https://support.skype.com/faq/FA34641/frequently-asked-questions-about-using-skype-for-hololens)
|
||||
|
||||
For more details about the status of the myriad Azure Services that can connect to HoloLens, see [Azure status](https://azure.microsoft.com/status/).
|
||||
|
||||
For more details about current known issues, see [HoloLens known issues](https://docs.microsoft.com/windows/mixed-reality/hololens-known-issues).
|
||||
For more details about current known issues, see [HoloLens known issues](hololens-known-issues.md).
|
||||
|
||||
Follow HoloLens on [Twitter](https://twitter.com/HoloLens) and subscribe on [Reddit](https://www.reddit.com/r/HoloLens/).
|
||||
|
BIN
devices/hololens/images/20190322-DevicePortal.png
Normal file
After Width: | Height: | Size: 109 KiB |
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Microsoft HoloLens (HoloLens)
|
||||
description: Landing page for HoloLens commercial and enterprise management.
|
||||
title: Microsoft HoloLens
|
||||
description: Landing page Microsoft HoloLens.
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
ms.assetid: 0947f5b3-8f0f-42f0-aa27-6d2cad51d040
|
||||
@ -8,7 +8,12 @@ author: scooley
|
||||
ms.author: scooley
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/14/2019
|
||||
ms.date: 10/14/2019
|
||||
audience: ITPro
|
||||
appliesto:
|
||||
- HoloLens 1
|
||||
- HoloLens 2
|
||||
|
||||
---
|
||||
|
||||
# Microsoft HoloLens
|
||||
@ -21,33 +26,33 @@ ms.date: 07/14/2019
|
||||
|
||||
<p>To learn more about HoloLens 2 for developers, check out the <a href="https://docs.microsoft.com/windows/mixed-reality/">mixed reality developer documentation</a>.</p>
|
||||
|
||||
</td><td align="left" style="border: 0px"><img alt="HoloLens 2 side view" src="images/hololens2-side-render-xs.png"/></td></tr>
|
||||
<p>To buy HoloLens, check out <a href="https://www.microsoft.com/hololens/buy">HoloLens pricing and sales</a> on <a href="https://www.microsoft.com/hololens">microsoft.com/HoloLens</a>.</p>
|
||||
</td>
|
||||
|
||||
<td align="left" style="border: 0px"><img alt="HoloLens 2 side view" src="images/hololens2-side-render-xs.png"/></td></tr>
|
||||
</tbody></table>
|
||||
|
||||
## Guides in this section
|
||||
|
||||
| Guide | Description |
|
||||
| --- | --- |
|
||||
| [Get started with HoloLens](hololens1-setup.md) | Set up HoloLens for the first time. |
|
||||
| [Deploy HoloLens in a commercial environment](hololens-requirements.md) | Configure HoloLens for scale enterprise deployment and ongoing device management. |
|
||||
| [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. |
|
||||
| [Get started with HoloLens 2](hololens2-setup.md) | Set up HoloLens 2 for the first time. |
|
||||
| [Get started with HoloLens (1st gen)](hololens1-setup.md) | Set up HoloLens (1st gen) for the first time. |
|
||||
| [Get started with HoloLens in a commercial or classroom environment](hololens-requirements.md) | Plan for a multi-device HoloLens deployment and create a strategy for ongoing device management.</br>This section is tailored to IT professionals managing devices with existing device management infrastructure. |
|
||||
|
||||
## Quick reference by topic
|
||||
|
||||
| Topic | Description |
|
||||
| --- | --- |
|
||||
| [What's new in Microsoft HoloLens](hololens-whats-new.md) | Discover new features in the latest updates. |
|
||||
| [Configure HoloLens using a provisioning package](hololens-provisioning.md) | Provisioning packages make it easy for IT administrators to configure HoloLens devices without imaging |
|
||||
| [HoloLens MDM support](hololens-enroll-mdm.md) | Manage multiple HoloLens devices simultaneously using Mobile Device Management (MDM) solutions like Microsoft Intune. |
|
||||
| [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. |
|
||||
| [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 application access management](hololens-kiosk.md) | Manage application access for different user groups. |
|
||||
| [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) | Learn how to use Bitlocker device encryption to protect files and information stored on the HoloLens. |
|
||||
| [Install localized version of HoloLens](hololens1-install-localized.md) | Configure HoloLens for different locale. |
|
||||
| [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. |
|
||||
|
||||
## Related resources
|
||||
|
||||
* [Documentation for Holographic app development](https://developer.microsoft.com/windows/mixed-reality/development)
|
||||
* [HoloLens Commercial Suite](https://www.microsoft.com/microsoft-hololens/hololens-commercial)
|
||||
* [HoloLens release notes](https://developer.microsoft.com/windows/mixed-reality/release_notes)
|
||||
|
@ -6,22 +6,26 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.date: 10/02/2018
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Battery Limit setting
|
||||
|
||||
Battery Limit option is a UEFI setting that changes how the Surface device battery is charged and may prolong its longevity. This setting is recommended in cases in which the device is continuously connected to power, for example when devices are integrated into kiosk solutions.
|
||||
|
||||
## Battery Limit information
|
||||
## How Battery Limit works
|
||||
|
||||
Setting the device on Battery Limit changes the protocol for charging the device battery. When Battery Limit is enabled, the battery charge will be limited to 50% of its maximum capacity. The charge level reported in Windows will reflect this limit. Therefore, it will show that the battery is charged up to 50% and will not charge beyond this limit. If you enable Battery Limit while the device is above 50% charge, the Battery icon will show that the device is plugged in but discharging until the device reaches 50% of its maximum charge capacity.
|
||||
|
||||
Adding the Battery Limit option to Surface UEFI requires a [Surface UEFI firmware update](update.md), available through Windows Update or via the MSI driver and firmware packages on the Microsoft Download Center. Check [Enable "Battery Limit" for Surface devices that have to be plugged in for extended periods of time](https://support.microsoft.com/help/4464941) for the specific Surface UEFI version required for each supported device. Currently, Battery Limit is supported on a subset of Surface devices and will be available in the future on other Surface device models.
|
||||
## Supported devices
|
||||
The Battery Limit UEFI setting is built into the latest Surface devices including Surface Pro 7 and Surface Laptop 3. Earlier devices require a
|
||||
[Surface UEFI firmware update](update.md), available through Windows Update or via the MSI driver and firmware packages on the [Surface Support site](https://support.microsoft.com/help/4023482/surface-download-drivers-and-firmware-for-surface). Check [Enable "Battery Limit" for Surface devices that have to be plugged in for extended periods of time](https://support.microsoft.com/help/4464941) for the specific Surface UEFI version required for each supported device.
|
||||
|
||||
## Enabling Battery Limit in Surface UEFI (Surface Pro 4 and later)
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Deploy Surface devices
|
||||
@ -39,19 +41,7 @@ Learn about about deploying ARM- and Intel-based Surface devices.
|
||||
| [Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md)| See how Microsoft Surface Deployment Accelerator provides a quick and simple deployment mechanism for organizations to reimage Surface devices. |
|
||||
[Battery Limit setting](battery-limit.md) | Learn how to use Battery Limit, a UEFI setting that changes how the Surface device battery is charged and may prolong its longevity.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
[Surface for IT pros blog](http://blogs.technet.com/b/surface/)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
[Surface IT Pro Blog](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/bg-p/SurfaceITPro)
|
||||
|
||||
|
@ -9,12 +9,15 @@ ms.sitesec: library
|
||||
author: Teresa-Motiv
|
||||
ms.author: v-tea
|
||||
ms.topic: article
|
||||
ms.date: 10/2/2019
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer: scottmca
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
manager: jarrettr
|
||||
appliesto:
|
||||
- Surface Laptop (1st Gen)
|
||||
- Surface Laptop 2
|
||||
- Surface Laptop 3
|
||||
---
|
||||
|
||||
# How to enable the Surface Laptop keyboard during MDT deployment
|
||||
@ -30,44 +33,77 @@ On most types of Surface devices, the keyboard should work during Lite Touch Ins
|
||||
To add the keyboard drivers to the selection profile, follow these steps:
|
||||
|
||||
1. Download the latest Surface Laptop MSI file from the appropriate locations:
|
||||
- [Surface Laptop (1st Gen) Drivers and Firmware](https://www.microsoft.com/download/details.aspx?id=55489)
|
||||
- [Surface Laptop 2 Drivers and Firmware](https://www.microsoft.com/download/details.aspx?id=57515)
|
||||
- [Surface Laptop (1st Gen) Drivers and Firmware](https://www.microsoft.com/download/details.aspx?id=55489)
|
||||
- [Surface Laptop 2 Drivers and Firmware](https://www.microsoft.com/download/details.aspx?id=57515)
|
||||
- [Surface Laptop 3 with Intel Processor Drivers and Firmware](https://www.microsoft.com/download/details.aspx?id=100429)
|
||||
|
||||
1. Extract the contents of the Surface Laptop MSI file to a folder that you can easily locate (for example, c:\surface_laptop_drivers). To extract the contents, open an elevated Command Prompt window and run the following command:
|
||||
2. Extract the contents of the Surface Laptop MSI file to a folder that you can easily locate (for example, c:\surface_laptop_drivers). To extract the contents, open an elevated Command Prompt window and run the command from the following example:
|
||||
|
||||
```cmd
|
||||
Msiexec.exe /a SurfaceLaptop_Win10_15063_1703008_1.msi targetdir=c:\surface_laptop_drivers /qn
|
||||
```
|
||||
|
||||
1. Open the Deployment Workbench and expand the **Deployment Shares** node and your deployment share, then navigate to the **WindowsPEX64** folder.
|
||||
3. Open the Deployment Workbench and expand the **Deployment Shares** node and your deployment share, then navigate to the **WindowsPEX64** folder.
|
||||
|
||||

|
||||
|
||||
1. Right-click the **WindowsPEX64** folder and select **Import Drivers**.
|
||||
1. Follow the instructions in the Import Driver Wizard to import the driver folders into the WindowsPEX64 folder.
|
||||
4. Right-click the **WindowsPEX64** folder and select **Import Drivers**.
|
||||
5. Follow the instructions in the Import Driver Wizard to import the driver folders into the WindowsPEX64 folder.
|
||||
|
||||
To support Surface Laptop (1st Gen), import the following folders:
|
||||
- SurfacePlatformInstaller\Drivers\System\GPIO
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceHidMiniDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
|
||||
> [!NOTE]
|
||||
> Check the downloaded MSI package to determine the format and directory structure. The directory structure will start with either SurfacePlatformInstaller (older MSI files) or SurfaceUpdate (Newer MSI files) depending on when the MSI was released.
|
||||
|
||||
To support Surface Laptop 2, import the following folders:
|
||||
- SurfacePlatformInstaller\Drivers\System\GPIO
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceHIDMiniDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\I2C
|
||||
- SurfacePlatformInstaller\Drivers\System\SPI
|
||||
- SurfacePlatformInstaller\Drivers\System\UART
|
||||
To support Surface Laptop (1st Gen), import the following folders:
|
||||
|
||||
1. Verify that the WindowsPEX64 folder now contains the imported drivers. The folder should resemble the following:
|
||||
- SurfacePlatformInstaller\Drivers\System\GPIO
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceHidMiniDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
|
||||
|
||||
Or for newer MSI files beginning with "SurfaceUpdate", use:
|
||||
|
||||
- SurfaceUpdate\SerialIOGPIO
|
||||
- SurfaceUpdate\SurfaceHidMiniDriver
|
||||
- SurfaceUpdate\SurfaceSerialHubDriver
|
||||
|
||||
To support Surface Laptop 2, import the following folders:
|
||||
|
||||
- SurfacePlatformInstaller\Drivers\System\GPIO
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceHIDMiniDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\I2C
|
||||
- SurfacePlatformInstaller\Drivers\System\SPI
|
||||
- SurfacePlatformInstaller\Drivers\System\UART
|
||||
|
||||
Or for newer MSI files beginning with "SurfaceUpdate", use:
|
||||
|
||||
- SurfaceUpdate\SerialIOGPIO
|
||||
- SurfaceUpdate\IclSerialIOI2C
|
||||
- SurfaceUpdate\IclSerialIOSPI
|
||||
- SurfaceUpdate\IclSerialIOUART
|
||||
- SurfaceUpdate\SurfaceHidMini
|
||||
- SurfaceUpdate\SurfaceSerialHub
|
||||
|
||||
|
||||
To support Surface Laptop 3 with Intel Processor, import the following folders:
|
||||
|
||||
- SurfaceUpdate\IclSerialIOGPIO
|
||||
- SurfaceUpdate\IclSerialIOI2C
|
||||
- SurfaceUpdate\IclSerialIOSPI
|
||||
- SurfaceUpdate\IclSerialIOUART
|
||||
- SurfaceUpdate\SurfaceHidMini
|
||||
- SurfaceUpdate\SurfaceSerialHub
|
||||
- SurfaceUpdate\SurfaceHotPlug
|
||||
|
||||
|
||||
6. Verify that the WindowsPEX64 folder now contains the imported drivers. The folder should resemble the following:
|
||||
|
||||

|
||||
|
||||
1. Configure a selection profile that uses the WindowsPEX64 folder. The selection profile should resemble the following:
|
||||
7. Configure a selection profile that uses the WindowsPEX64 folder. The selection profile should resemble the following:
|
||||
|
||||

|
||||
|
||||
1. Configure the Windows PE properties of the MDT deployment share to use the new selection profile, as follows:
|
||||
8. Configure the Windows PE properties of the MDT deployment share to use the new selection profile, as follows:
|
||||
|
||||
- For **Platform**, select **x64**.
|
||||
- For **Selection profile**, select the new profile.
|
||||
@ -75,7 +111,7 @@ To add the keyboard drivers to the selection profile, follow these steps:
|
||||
|
||||

|
||||
|
||||
1. Verify that you have configured the remaining Surface Laptop drivers by using either a selection profile or a **DriverGroup001** variable.
|
||||
9. Verify that you have configured the remaining Surface Laptop drivers by using either a selection profile or a **DriverGroup001** variable.
|
||||
- For Surface Laptop (1st Gen), the model is **Surface Laptop**. The remaining Surface Laptop drivers should reside in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop folder as shown in the figure that follows this list.
|
||||
- For Surface Laptop 2, the model is **Surface Laptop 2**. The remaining Surface Laptop drivers should reside in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop 2 folder.
|
||||
|
||||
|
BIN
devices/surface/images/manage-surface-uefi-fig5a.png
Normal file
After Width: | Height: | Size: 56 KiB |
BIN
devices/surface/images/manage-surface-uefi-fig7a.png
Normal file
After Width: | Height: | Size: 59 KiB |
@ -10,6 +10,8 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Long-Term Servicing Channel (LTSC) for Surface devices
|
||||
@ -28,23 +30,7 @@ General-purpose Surface devices are intended to run on the Semi-Annual Channel t
|
||||
|
||||
Surface devices in specialized scenarios–such as PCs that control medical equipment, point-of-sale systems, and ATMs–might consider the use of LTSC. These special-purpose systems typically perform a single task and do not require feature updates as frequently as other devices in the organization.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Surface TechCenter](https://technet.microsoft.com/windows/surface)
|
||||
|
||||
- [Surface for IT pros blog](http://blogs.technet.com/b/surface/)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Surface IT Pro Blog](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/bg-p/SurfaceITPro)
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Best practice power settings for Surface devices
|
||||
description: This topic provides best practice recommendations for maintaining optimal power settings and explains how Surface streamlines the power management experience.
|
||||
description: This topic provides best practice recommendations for maintaining optimal power settings and explains how Surface streamlines the power management experience. This article applies to all currently supported Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
@ -9,7 +9,9 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.date: 08/21/2019
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
ms.date: 10/28/2019
|
||||
---
|
||||
|
||||
# Best practice power settings for Surface devices
|
||||
@ -49,7 +51,7 @@ module (SAM). The SAM chip functions as the Surface device power-policy
|
||||
owner, using algorithms to calculate optimal power requirements. It
|
||||
works in conjunction with Windows power manager to allocate or throttle
|
||||
only the exact amount of power required for hardware components to
|
||||
function.
|
||||
function. This article applies to all currently supported Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3.
|
||||
|
||||
## Utilizing the custom power profile in Surface
|
||||
|
||||
|
@ -17,22 +17,25 @@ manager: dansimp
|
||||
|
||||
# Manage Surface UEFI settings
|
||||
|
||||
Current and future generations of Surface devices, including Surface Pro 7, Surface Book 2, and Surface Studio 2,use a unique UEFI firmware engineered by Microsoft specifically for these devices. This firmware allows for significantly greater control of the device’s operation over firmware versions in earlier generation Surface devices, including the support for touch, mouse, and keyboard operation. By using the Surface UEFI settings you can easily enable or disable internal devices or components, configure security to protect UEFI settings from being changed, and adjust the Surface device boot settings.
|
||||
|
||||
>[!NOTE]
|
||||
>Surface Pro 3, Surface 3, Surface Pro 2, Surface 2, Surface Pro, and Surface do not use the Surface UEFI and instead use firmware provided by third-party manufacturers, such as AMI.
|
||||
|
||||
You can enter the Surface UEFI settings on your Surface device by pressing the **Volume Up** button and the **Power** button simultaneously. Hold the **Volume Up** button until the Surface logo is displayed, which indicates that the device has begun to boot.
|
||||
All current and future generations of Surface devices use a unique Unified Extensible Firmware Interface (UEFI) engineered by Microsoft specifically for these devices. Surface UEFI settings provide the ability to enable or disable built-in devices and components, protect UEFI settings from being changed, and adjust the Surface device boot settings.
|
||||
|
||||
## Support for cloud-based management
|
||||
|
||||
With Device Firmware Configuration Interface (DFCI) profiles built into Microsoft Intune (now available in public preview), Surface UEFI management extends the modern management stack down to the UEFI hardware level. DFCI supports zero-touch provisioning, eliminates BIOS passwords, provides control of security settings including boot options and built-in peripherals, and lays the groundwork for advanced security scenarios in the future. DFCI is currently available for Surface Pro 7, Surface Pro X, and Surface Laptop 3. For more information, refer to [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md).
|
||||
|
||||
## Open Surface UEFI menu
|
||||
|
||||
## PC information
|
||||
To adjust UEFI settings during system startup:
|
||||
|
||||
On the **PC information** page, detailed information about your Surface device is provided:
|
||||
1. Shut down your Surface and wait about 10 seconds to make sure it's off.
|
||||
2. Press and hold the **Volume-up** button and - at the same time - press and release the **Power button.**
|
||||
3. As the Microsoft or Surface logo appears on your screen, continue to hold the **Volume-up** button until the UEFI screen appears.
|
||||
|
||||
- **Model** – Your Surface device’s model will be displayed here, such as Surface Book or Surface Pro 4. The exact configuration of your device is not shown, (such as processor, disk size, or memory size).
|
||||
## UEFI PC information page
|
||||
|
||||
The PC information page includes detailed information about your Surface device:
|
||||
|
||||
- **Model** – Your Surface device’s model will be displayed here, such as Surface Book 2 or Surface Pro 7. The exact configuration of your device is not shown, (such as processor, disk size, or memory size).
|
||||
- **UUID** – This Universally Unique Identification number is specific to your device and is used to identify the device during deployment or management.
|
||||
|
||||
- **Serial Number** – This number is used to identify this specific Surface device for asset tagging and support scenarios.
|
||||
@ -56,9 +59,9 @@ You will also find detailed information about the firmware of your Surface devic
|
||||
|
||||
You can find up-to-date information about the latest firmware version for your Surface device in the [Surface Update History](https://www.microsoft.com/surface/support/install-update-activate/surface-update-history) for your device.
|
||||
|
||||
## Security
|
||||
## UEFI Security page
|
||||
|
||||
On the **Security** page of Surface UEFI settings, you can 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):
|
||||
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):
|
||||
|
||||
- Uppercase letters: A-Z
|
||||
|
||||
@ -74,21 +77,21 @@ The password must be at least 6 characters and is case sensitive.
|
||||
|
||||
*Figure 2. 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 3. 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*
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||

|
||||
|
||||
*Figure 4. Configure Surface UEFI security settings*
|
||||
|
||||
## Devices
|
||||
## UEFI menu: Devices
|
||||
|
||||
On the **Devices** page you can enable or disable specific devices and components of your Surface device. Devices that you can enable or disable on this page include:
|
||||
The Devices page allows you to enable or disable specific devices and components including:
|
||||
|
||||
- Docking and USB Ports
|
||||
|
||||
@ -106,13 +109,13 @@ On the **Devices** page you can enable or disable specific devices and component
|
||||
|
||||
Each device is listed with a slider button that you can move to **On** (enabled) or **Off** (disabled) position, as shown in Figure 5.
|
||||
|
||||

|
||||

|
||||
|
||||
*Figure 5. Enable and disable specific devices*
|
||||
|
||||
## Boot configuration
|
||||
## UEFI menu: Boot configuration
|
||||
|
||||
On the **Boot Configuration** page, you can change the order of your boot devices and/or enable or disable boot of the following devices:
|
||||
The Boot Configuration page allows you to change the order of your boot devices as well as enable or disable boot of the following devices:
|
||||
|
||||
- Windows Boot Manager
|
||||
|
||||
@ -132,68 +135,83 @@ For the specified boot order to take effect, you must set the **Enable Alternate
|
||||
|
||||
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.
|
||||
|
||||
## UEFI menu: Management
|
||||
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.
|
||||
|
||||
## Exit
|
||||

|
||||
*Figure 7. Manage access to Zero Touch UEFI Management and other features*
|
||||
|
||||
Use the **Restart Now** button on the **Exit** page to exit UEFI settings, as shown in Figure 7.
|
||||
|
||||
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**.
|
||||
|
||||
> [!NOTE]
|
||||
> The UEFI Management settings page and use of DFCI is only available on Surface Pro 7, Surface Pro X, and Surface Laptop 3.
|
||||
|
||||
For more information, refer to [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md).
|
||||
|
||||
## UEFI menu: Exit
|
||||
|
||||
Use the **Restart Now** button on the **Exit** page to exit UEFI settings, as shown in Figure 8.
|
||||
|
||||

|
||||
|
||||
*Figure 7. Click Restart Now to exit Surface UEFI and restart the device*
|
||||
*Figure 8. Click Restart Now to exit Surface UEFI and restart the device*
|
||||
|
||||
## Surface UEFI boot screens
|
||||
|
||||
When you update Surface device firmware, by using either Windows Update or manual installation, the updates are not applied immediately to the device, but instead during the next reboot cycle. You can find out more about the Surface firmware update process in [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-pro-3-firmware-updates). The progress of the firmware update is displayed on a screen with progress bars of differing colors to indicate the firmware for each component. Each component’s progress bar is shown in Figures 8 through 17.
|
||||
When you update Surface device firmware, by using either Windows Update or manual installation, the updates are not applied immediately to the device, but instead during the next reboot cycle. You can find out more about the Surface firmware update process in [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-pro-3-firmware-updates). The progress of the firmware update is displayed on a screen with progress bars of differing colors to indicate the firmware for each component. Each component’s progress bar is shown in Figures 9 through 18.
|
||||
|
||||

|
||||
|
||||
*Figure 8. The Surface UEFI firmware update displays a blue progress bar*
|
||||
*Figure 9. The Surface UEFI firmware update displays a blue progress bar*
|
||||
|
||||

|
||||
|
||||
*Figure 9. The System Embedded Controller firmware update displays a green progress bar*
|
||||
*Figure 10. The System Embedded Controller firmware update displays a green progress bar*
|
||||
|
||||

|
||||
|
||||
*Figure 10. The SAM Controller firmware update displays an orange progress bar*
|
||||
*Figure 11. The SAM Controller firmware update displays an orange progress bar*
|
||||
|
||||

|
||||
|
||||
*Figure 11. The Intel Management Engine firmware update displays a red progress bar*
|
||||
*Figure 12. The Intel Management Engine firmware update displays a red progress bar*
|
||||
|
||||

|
||||
|
||||
*Figure 12. The Surface touch firmware update displays a gray progress bar*
|
||||
*Figure 13. The Surface touch firmware update displays a gray progress bar*
|
||||
|
||||

|
||||
|
||||
*Figure 13. The Surface KIP firmware update displays a light green progress bar*
|
||||
*Figure 14. The Surface KIP firmware update displays a light green progress bar*
|
||||
|
||||

|
||||
|
||||
*Figure 14. The Surface ISH firmware update displays a light pink progress bar*
|
||||
*Figure 15. The Surface ISH firmware update displays a light pink progress bar*
|
||||
|
||||

|
||||
|
||||
*Figure 15. The Surface Trackpad firmware update displays a pink progress bar*
|
||||
*Figure 16. The Surface Trackpad firmware update displays a pink progress bar*
|
||||
|
||||

|
||||
|
||||
*Figure 16. The Surface TCON firmware update displays a light gray progress bar*
|
||||
*Figure 17. The Surface TCON firmware update displays a light gray progress bar*
|
||||
|
||||
|
||||

|
||||
|
||||
*Figure 17. The Surface TPM firmware update displays a purple progress bar*
|
||||
*Figure 18. The Surface TPM firmware update displays a purple progress bar*
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>An additional warning message that indicates Secure Boot is disabled is displayed, as shown in Figure 18.
|
||||
>An additional warning message that indicates Secure Boot is disabled is displayed, as shown in Figure 19.
|
||||
|
||||

|
||||
|
||||
*Figure 18. Surface boot screen that indicates Secure Boot has been disabled in Surface UEFI settings*
|
||||
*Figure 19. Surface boot screen that indicates Secure Boot has been disabled in Surface UEFI settings*
|
||||
|
||||
## Related topics
|
||||
|
||||
[Advanced UEFI security features for Surface Pro 3](advanced-uefi-security-features-for-surface-pro-3.md)
|
||||
- [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md)
|
||||
|
||||
- [Surface Enterprise Management Mode](surface-enterprise-management-mode.md)
|
@ -8,9 +8,11 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 1/15/2019
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer: hachidan
|
||||
manager: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Surface Brightness Control
|
||||
|
@ -4,7 +4,7 @@ description: Microsoft Surface Deployment Accelerator provides a quick and simpl
|
||||
ms.assetid: E7991E90-4AAE-44B6-8822-58BFDE3EADE4
|
||||
ms.reviewer: hachidan
|
||||
manager: dansimp
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 10/31/2019
|
||||
ms.localizationpriority: medium
|
||||
keywords: deploy, install, tool
|
||||
ms.prod: w10
|
||||
@ -19,7 +19,6 @@ ms.audience: itpro
|
||||
|
||||
# Microsoft Surface Deployment Accelerator
|
||||
|
||||
|
||||
Microsoft Surface Deployment Accelerator (SDA) automates the creation and configuration of a Microsoft recommended deployment experience by using free Microsoft deployment tools.
|
||||
|
||||
> [!NOTE]
|
||||
|
@ -13,7 +13,7 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 10/31/2019
|
||||
---
|
||||
|
||||
# Step by step: Surface Deployment Accelerator
|
||||
|
@ -14,6 +14,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 09/26/2019
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Top support solutions for Surface devices
|
||||
|
@ -3,12 +3,12 @@ title: Deploy Surface Diagnostic Toolkit for Business
|
||||
description: This topic explains how to use the Surface Diagnostic Toolkit for Business.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.localizationpriority: normal
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 09/27/2019
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer: hachidan
|
||||
manager: dansimp
|
||||
ms.audience: itpro
|
||||
@ -173,8 +173,9 @@ You can select to run a wide range of logs across applications, drivers, hardwar
|
||||
### Version 2.43.139.0
|
||||
*Release date: October 21, 2019*<br>
|
||||
This version of Surface Diagnostic Toolkit for Business adds support for the following:
|
||||
-Surface Pro 7
|
||||
-Surface Laptop 3
|
||||
|
||||
- Surface Pro 7
|
||||
- Surface Laptop 3
|
||||
|
||||
### Version 2.42.139.0
|
||||
*Release date: September 24, 2019*<br>
|
||||
|
@ -16,7 +16,7 @@ ms.audience: itpro
|
||||
|
||||
# Run Surface Diagnostic Toolkit for Business using commands
|
||||
|
||||
Running the Surface Diagnostic Toolkit (SDT) at a command prompt requires downloading the STD app console. After it's installed, you can run SDT at a command prompt via the Windows command console (cmd.exe) or using Windows PowerShell, including PowerShell Integrated Scripting Environment (ISE), which provides support for autocompletion of commands, copy/paste, and other features.
|
||||
Running the Surface Diagnostic Toolkit (SDT) at a command prompt requires downloading the STD app console. After it's installed, you can run SDT at a command prompt via the Windows command console (cmd.exe) or using Windows PowerShell, including PowerShell Integrated Scripting Environment (ISE), which provides support for autocompletion of commands, copy/paste, and other features. For a list of supported Surface devices in SDT, refer to [Deploy Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md).
|
||||
|
||||
>[!NOTE]
|
||||
>To run SDT using commands, you must be signed in to the Administrator account or signed in to an account that is a member of the Administrator group on your Surface device.
|
||||
|
@ -7,36 +7,34 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 11/15/2018
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer: hachidan
|
||||
manager: dansimp
|
||||
ms.localizationpriority: normal
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Use Surface Diagnostic Toolkit for Business in desktop mode
|
||||
|
||||
This topic explains how to use the Surface Diagnostic Toolkit (SDT) to help users in your organization run the tool to identify and diagnose issues with the Surface device. Successfully running SDT can quickly determine if a reported issue is caused by failed hardware or user error.
|
||||
This topic explains how to use the Surface Diagnostic Toolkit (SDT) to help users in your organization run the tool to identify and diagnose issues with the Surface device. Successfully running SDT can quickly determine if a reported issue is caused by failed hardware or user error. For a list of supported Surface devices in SDT, refer to [Deploy Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md).
|
||||
|
||||
|
||||
1. Direct the user to install [the SDT package](surface-diagnostic-toolkit-business.md#create-custom-sdt) from a software distribution point or network share. After it is installed, you’re ready to guide the user through a series of tests.
|
||||
|
||||
2. Begin at the home page, which allows users to enter a description of the issue, and click **Continue**, as shown in figure 1.
|
||||
|
||||

|
||||
|
||||
*Figure 1. SDT in desktop mode*
|
||||
*Figure 1. SDT in desktop mode*
|
||||
|
||||
3. When SDT indicates the device has the latest updates, click **Continue** to advance to the catalog of available tests, as shown in figure 2.
|
||||
|
||||

|
||||
|
||||
*Figure 2. Select from SDT options*
|
||||
*Figure 2. Select from SDT options*
|
||||
|
||||
4. You can choose to run all the diagnostic tests. Or, if you already suspect a particular issue such as a faulty display or a power supply problem, click **Select** to choose from the available tests and click **Run Selected**, as shown in figure 3. See the following table for details of each test.
|
||||
|
||||

|
||||
|
||||
*Figure 3. Select hardware tests*
|
||||
*Figure 3. Select hardware tests*
|
||||
|
||||
Hardware test | Description
|
||||
--- | ---
|
||||
@ -55,6 +53,7 @@ This topic explains how to use the Surface Diagnostic Toolkit (SDT) to help user
|
||||
|
||||
|
||||
<span id="multiple" />
|
||||
|
||||
## Running multiple hardware tests to troubleshoot issues
|
||||
|
||||
SDT is designed as an interactive tool that runs a series of tests. For each test, SDT provides instructions summarizing the nature of the test and what users should expect or look for in order for the test to be successful. For example, to diagnose if the display brightness is working properly, SDT starts at zero and increases the brightness to 100 percent, asking users to confirm – by answering **Yes** or **No** -- that brightness is functioning as expected, as shown in figure 4.
|
||||
@ -62,7 +61,6 @@ SDT is designed as an interactive tool that runs a series of tests. For each tes
|
||||
For each test, if functionality does not work as expected and the user clicks **No**, SDT generates a report of the possible causes and ways to troubleshoot it.
|
||||
|
||||

|
||||
|
||||
*Figure 4. Running hardware diagnostics*
|
||||
|
||||
1. If the brightness successfully adjusts from 0-100 percent as expected, direct the user to click **Yes** and then click **Continue**.
|
||||
@ -75,24 +73,18 @@ For each test, if functionality does not work as expected and the user clicks **
|
||||
SDT enables you to diagnose and repair applications that may be causing issues, as shown in figure 5.
|
||||
|
||||

|
||||
|
||||
*Figure 5. Running repairs*
|
||||
|
||||
|
||||
|
||||
|
||||
<span id="logs" />
|
||||
|
||||
### Generating logs for analyzing issues
|
||||
|
||||
SDT provides extensive log-enabled diagnosis support across applications, drivers, hardware, and operating system issues, as shown in figure 6.
|
||||
|
||||

|
||||
|
||||
*Figure 6. Generating logs*
|
||||
|
||||
|
||||
|
||||
<span id="detailed-report" />
|
||||
|
||||
### Generating detailed report comparing device vs. optimal configuration
|
||||
|
||||
Based on the logs, SDT generates a report for software- and firmware-based issues that you can save to a preferred location.
|
||||
|
@ -10,7 +10,7 @@ ms.topic: article
|
||||
ms.date: 06/11/2019
|
||||
ms.reviewer: cottmca
|
||||
manager: dansimp
|
||||
ms.localizationpriority: normal
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 09/18/2019
|
||||
ms.date: 10/09/2019
|
||||
ms.reviewer: scottmca
|
||||
manager: dansimp
|
||||
ms.audience: itpro
|
||||
|
@ -9,9 +9,11 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 01/06/2017
|
||||
ms.reviewer:
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer: scottmca
|
||||
manager: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Microsoft Surface Enterprise Management Mode
|
||||
@ -19,12 +21,14 @@ manager: dansimp
|
||||
Microsoft Surface Enterprise Management Mode (SEMM) is a feature of Surface devices with Surface UEFI that allows you to secure and manage firmware settings within your organization. With SEMM, IT professionals can prepare configurations of UEFI settings and install them on a Surface device. In addition to the ability to configure UEFI settings, SEMM also uses a certificate to protect the configuration from unauthorized tampering or removal.
|
||||
|
||||
>[!NOTE]
|
||||
>SEMM is only available on devices with Surface UEFI firmware such as Surface Pro 4 and later, Surface Go, Surface Laptop, Surface Book, and Surface Studio. For more information about Surface UEFI, see [Manage Surface UEFI Settings](https://technet.microsoft.com/itpro/surface/manage-surface-uefi-settings).
|
||||
>SEMM is only available on devices with Surface UEFI firmware.
|
||||
|
||||
|
||||
When Surface devices are configured by SEMM and secured with the SEMM certificate, they are considered *enrolled* in SEMM. When the SEMM certificate is removed and control of UEFI settings is returned to the user of the device, the Surface device is considered *unenrolled* in SEMM.
|
||||
|
||||
There are two administrative options you can use to manage SEMM and enrolled Surface devices – a standalone tool or integration with System Center Configuration Manager. The SEMM standalone tool, called the Microsoft Surface UEFI Configurator, is described in this article. For more information about how to manage SEMM with System Center Configuration Manager, see [Use System Center Configuration Manager to manage devices with SEMM](https://technet.microsoft.com/itpro/surface/use-system-center-configuration-manager-to-manage-devices-with-semm).
|
||||
|
||||
|
||||
## Microsoft Surface UEFI Configurator
|
||||
|
||||
The primary workspace of SEMM is Microsoft Surface UEFI Configurator, as shown in Figure 1. Microsoft Surface UEFI Configurator is a tool that is used to create Windows Installer (.msi) packages or WinPE images that are used to enroll, configure, and unenroll SEMM on a Surface device. These packages contain a configuration file where the settings for UEFI are specified. SEMM packages also contain a certificate that is installed and stored in firmware and used to verify the signature of configuration files before UEFI settings are applied.
|
||||
@ -33,8 +37,6 @@ The primary workspace of SEMM is Microsoft Surface UEFI Configurator, as shown i
|
||||
|
||||
*Figure 1. Microsoft Surface UEFI Configurator*
|
||||
|
||||
>[!NOTE]
|
||||
>Windows 10 is required to run Microsoft Surface UEFI Configurator
|
||||
|
||||
You can use the Microsoft Surface UEFI Configurator tool in three modes:
|
||||
|
||||
@ -62,17 +64,11 @@ See the [Surface Enterprise Management Mode certificate requirements](#surface-e
|
||||
|
||||
After a device is enrolled in SEMM, the configuration file is read and the settings specified in the file are applied to UEFI. When you run a configuration package on a device that is already enrolled in SEMM, the signature of the configuration file is checked against the certificate that is stored in the device firmware. If the signature does not match, no changes are applied to the device.
|
||||
|
||||
You can use Surface UEFI settings to enable or disable the operation of individual components, such as cameras, wireless communication, or docking USB port (as shown in Figure 3), and configure advanced settings (as shown in Figure 4).
|
||||
### Enable or disable devices in Surface UEFI with SEMM
|
||||
|
||||

|
||||
The built in devices that appear in the UEFI Devices page may vary depending on your device or corporate environment; for example, LTE only appears on devices equipped with LTE support.
|
||||
|
||||
*Figure 3. Enable or disable devices in Surface UEFI with SEMM*
|
||||
|
||||

|
||||
|
||||
*Figure 4. Configure advanced settings with SEMM*
|
||||
|
||||
You can enable or disable the following devices with SEMM:
|
||||
The following list shows all the available devices you can manage in SEMM:
|
||||
|
||||
* Docking USB Port
|
||||
* On-board Audio
|
||||
@ -86,31 +82,38 @@ You can enable or disable the following devices with SEMM:
|
||||
* Wi-Fi and Bluetooth
|
||||
* LTE
|
||||
|
||||
You can configure the following advanced settings with SEMM:
|
||||
### Configure advanced settings with SEMM
|
||||
**Table 1. Advanced settings**
|
||||
|
||||
| Setting | Description |
|
||||
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| IPv6 for PXE Boot | Allows you to manage Ipv6 support for PXE boot. If you do not configure this setting, IPv6 support for PXE boot is disabled. |
|
||||
| Alternate Boot | Allows you to manage use of an Alternate boot order to boot directly to a USB or Ethernet device by pressing both the Volume Down button and Power button during boot. If you do not configure this setting, Alternate boot is enabled. |
|
||||
| Boot Order Lock | Allows you to lock the boot order to prevent changes. If you do not configure this setting, Boot Order Lock is disabled. |
|
||||
| USB Boot | Allows you to manage booting to USB devices. If you do not configure this setting, USB Boot is enabled. |
|
||||
| Network Stack | Allows you to manage Network Stack boot settings. If you do not configure this setting, the ability to manage Network Stack boot settings is enabled. |
|
||||
| Auto Power On | Allows you to manage Auto Power On boot settings. If you do not configure this setting, Auto Power on is enabled. |
|
||||
| Simultaneous Multi-Threading (SMT) | Allows you to manage Simultaneous Multi-Threading (SMT) to enable or disable hyperthreading. If you do not configure this setting, SMT is enabled. |
|
||||
|Enable Battery limit| Allows you to manage Battery limit functionality. If you do not configure this setting, Battery limit is enabled |
|
||||
| Security | Displays the Surface UEFI **Security** page. If you do not configure this setting, the Security page is displayed. |
|
||||
| Devices | Displays the Surface UEFI **Devices** page. If you do not configure this setting, the Devices page is displayed. |
|
||||
| Boot | Displays the Surface UEFI **Boot** page. If you do not configure this setting, the DateTime page is displayed. |
|
||||
| DateTime | Displays the Surface UEFI **DateTime** page. If you do not configure this setting, the DateTime page is displayed. |
|
||||
|
||||
|
||||
* IPv6 support for PXE boot
|
||||
* Alternate boot order, where the Volume Down button and Power button can be pressed together during boot, to boot directly to a USB or Ethernet device
|
||||
* Lock the boot order to prevent changes
|
||||
* Support for booting to USB devices
|
||||
* Enable Network Stack boot settings
|
||||
* Enable Auto Power On boot settings
|
||||
* Display of the Surface UEFI **Security** page
|
||||
* Display of the Surface UEFI **Devices** page
|
||||
* Display of the Surface UEFI **Boot** page
|
||||
* Display of the Surface UEFI **DateTime** page
|
||||
|
||||
>[!NOTE]
|
||||
>When you create a SEMM configuration package, two characters are shown on the **Successful** page, as shown in Figure 5.
|
||||
>When you create a SEMM configuration package, two characters are shown on the **Successful** page, as shown in Figure 3.
|
||||
|
||||

|
||||
|
||||
*Figure 5. Display of the last two characters of the certificate thumbprint on the Successful page*
|
||||
*Figure 3. Display of the last two characters of the certificate thumbprint on the Successful page*
|
||||
|
||||
These characters are the last two characters of the certificate thumbprint and should be written down or recorded. The characters are required to confirm enrollment in SEMM on a Surface device, as shown in Figure 6.
|
||||
These characters are the last two characters of the certificate thumbprint and should be written down or recorded. The characters are required to confirm enrollment in SEMM on a Surface device, as shown in Figure 4.
|
||||
|
||||

|
||||
|
||||
*Figure 6. Enrollment confirmation in SEMM with the SEMM certificate thumbprint*
|
||||
*Figure 4. Enrollment confirmation in SEMM with the SEMM certificate thumbprint*
|
||||
|
||||
>[!NOTE]
|
||||
>Administrators with access to the certificate file (.pfx) can read the thumbprint at any time by opening the .pfx file in CertMgr. To view the thumbprint with CertMgr, follow this process:
|
||||
@ -132,11 +135,11 @@ A Surface UEFI reset package is used to perform only one task — to unenroll a
|
||||
|
||||
### Recovery request
|
||||
|
||||
In some scenarios, it may be impossible to use a Surface UEFI reset package. (For example, if Windows becomes unusable on the Surface device.) In these scenarios you can unenroll the Surface device from SEMM through the **Enterprise Management** page of Surface UEFI (shown in Figure 7) with a Recovery Request operation.
|
||||
In some scenarios, it may be impossible to use a Surface UEFI reset package. (For example, if Windows becomes unusable on the Surface device.) In these scenarios you can unenroll the Surface device from SEMM through the **Enterprise Management** page of Surface UEFI (shown in Figure 5) with a Recovery Request operation.
|
||||
|
||||

|
||||
|
||||
*Figure 7. Initiate a SEMM recovery request on the Enterprise Management page*
|
||||
*Figure 5. Initiate a SEMM recovery request on the Enterprise Management page*
|
||||
|
||||
When you use the process on the **Enterprise Management** page to reset SEMM on a Surface device, you are provided with a Reset Request. This Reset Request can be saved as a file to a USB drive, copied as text, or read as a QR Code with a mobile device to be easily emailed or messaged. Use the Microsoft Surface UEFI Configurator Reset Request option to load a Reset Request file or enter the Reset Request text or QR Code. Microsoft Surface UEFI Configurator will generate a verification code that can be entered on the Surface device. If you enter the code on the Surface device and click **Restart**, the device will be unenrolled from SEMM.
|
||||
|
||||
|
@ -9,9 +9,11 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 03/20/2019
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# System SKU reference
|
||||
@ -39,6 +41,11 @@ System Model and System SKU are variables that are stored in the System Manageme
|
||||
| Surface Pro 6 Commercial | Surface Pro 6 | Surface_Pro_6_1796_Commercial |
|
||||
| Surface Laptop 2 Consumer | Surface Laptop 2 | Surface_Laptop_2_1769_Consumer |
|
||||
| Surface Laptop 2 Commercial | Surface Laptop 2 | Surface_Laptop_2_1769_Commercial |
|
||||
| Surface Pro 7 | Surface Pro 7 | Surface_Pro_7_1866 |
|
||||
| Surface Pro X | Surface Pro X | Surface_Pro_X_1876 |
|
||||
| Surface Laptop 3 13" Intel | Surface Laptop 3 | Surface_Laptop_3_1867:1868 |
|
||||
| Surface Laptop 3 15" Intel | Surface Laptop 3 | Surface_Laptop_3_1872 |
|
||||
| Surface Laptop 3 15" AMD | Surface Laptop 3 | Surface_Laptop_3_1873 |
|
||||
|
||||
## Examples
|
||||
|
||||
|
@ -6,16 +6,15 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.audience: itpro
|
||||
ms.localizationpriority: normal
|
||||
ms.localizationpriority: medium
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 08/15/2019
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer: tokatz
|
||||
manager: dansimp
|
||||
---
|
||||
# Optimize Wi-Fi connectivity for Surface devices
|
||||
|
||||
## Introduction
|
||||
|
||||
To stay connected with all-day battery life, Surface devices implement wireless connectivity settings that balance performance and power conservation. Outside of the most demanding mobility scenarios, users can maintain sufficient wireless connectivity without modifying default network adapter or related settings.
|
||||
|
||||
@ -32,7 +31,7 @@ If you’re managing a wireless network that’s typically accessed by many diff
|
||||
- **802.11r.** “**Fast BSS Transition”** accelerates connecting to new wireless access points by reducing the number of frames required before your device can access another AP as you move around with your device.
|
||||
- **802.11k.** **“Neighbor Reports”** provides devices with information on current conditions at neighboring access points. It can help your Surface device choose the best AP using criteria other than signal strength such as AP utilization.
|
||||
|
||||
Surface Go devices can also use 802.11v “BSS Transition Management Frames,” which functions much like 802.11k in providing information on nearby candidate APs.
|
||||
Specific Surface devices can also use 802.11v “BSS Transition Management Frames,” which functions much like 802.11k in providing information on nearby candidate APs. These include Surface Go, Surface Pro 7, Surface Pro X, and Surface Laptop 3.
|
||||
|
||||
## Managing user settings
|
||||
|
||||
|
@ -12,6 +12,8 @@ ms.topic: article
|
||||
ms.date: 01/06/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Unenroll Surface devices from SEMM
|
||||
|
@ -9,9 +9,11 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 02/01/2017
|
||||
ms.date: 10/31/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
# Use System Center Configuration Manager to manage devices with SEMM
|
||||
@ -382,7 +384,7 @@ To configure Surface UEFI settings or permissions for Surface UEFI settings, you
|
||||
|
||||
The computer where ShowSettingsOptions.ps1 is run must have Microsoft Surface UEFI Manager installed, but the script does not require a Surface device.
|
||||
|
||||
The following tables show the available settings for Surface Pro 4 and Surface Book:
|
||||
The following tables show the available settings for Surface Pro 4 and later including Surface Pro 7, Surface Book, Surface Laptop 3, and Surface Go.
|
||||
|
||||
*Table 1. Surface UEFI settings for Surface Pro 4*
|
||||
|
||||
|
@ -46,14 +46,14 @@ Windows Update for Business provides management policies for several types of up
|
||||
|
||||
## Offering
|
||||
|
||||
You can control when updates are applied, for example by deferring when an update is installed on a device or by pausing updates for a certain period of time.
|
||||
You can control when updates are applied, for example by deferring when an update is installed on a device or by pausing updates for a certain period.
|
||||
|
||||
### Manage which updates are offered
|
||||
|
||||
Windows Update for Business offers you the ability to turn on or off both driver and Microsoft product updates.
|
||||
|
||||
- Drivers (on/off): When "on," this policy will not include drivers with Windows Update.
|
||||
- Microsoft product updates (on/off): When "on" this policy will install udpates for other Microsoft products.
|
||||
- Microsoft product updates (on/off): When "on" this policy will install updates for other Microsoft products.
|
||||
|
||||
|
||||
### Manage when updates are offered
|
||||
@ -90,11 +90,19 @@ The branch readiness level enables administrators to specify which channel of fe
|
||||
|
||||
Prior to Windows 10, version 1903, there are two channels for released updates: Semi-annual Channel and Semi-annual Channel (Targeted). Deferral days are calculated against the release date of the chosen channel. Starting with Windows 10, version 1903 there is only the one release channel: Semi-annual Channel. All deferral days will be calculated against a release’s Semi-annual Channel release date. To see release dates, visit [Windows Release Information](https://docs.microsoft.com/windows/release-information/). You can set the branch readiness level by using the **Select when Preview Builds and Feature Updates are Received** policy. In order to use this to manage pre-release builds, first enable preview builds by using the **Manage preview Builds** policy.
|
||||
|
||||
### Recommendations
|
||||
|
||||
For the best experience with Windows Update, follow these guidelines:
|
||||
|
||||
- Use devices for at least 6 hours per month, including at least 2 hours of continuous use.
|
||||
- Keep devices regularly charged. Plugging in devices overnight enables them to automatically update outside of active hours.
|
||||
- Make sure that devices have at least 10 GB of free space.
|
||||
- Give devices unobstructed access to the Windows Update service.
|
||||
|
||||
|
||||
## Monitor Windows Updates by using Update Compliance
|
||||
|
||||
Update Compliance provides a holistic view of operating system update compliance, update deployment progress, and failure troubleshooting for Windows 10 devices. This service uses diagnostic data including installation progress, Windows Update configuration, and other information to provide such insights, at no extra cost and without additional infrastructure requirements. Whether used with Windows Update for Business or other management tools, you can be assured that your devices are properly updated.
|
||||
Update Compliance provides a holistic view of operating system update compliance, update deployment progress, and failure troubleshooting for Windows 10 devices. This service uses diagnostic data including installation progress, Windows Update configuration, and other information to provide such insights, at no extra cost and without extra infrastructure requirements. Whether used with Windows Update for Business or other management tools, you can be assured that your devices are properly updated.
|
||||
|
||||

|
||||
|
||||
|
@ -97,14 +97,14 @@ The smart card reader device name is constructed in the form <*VendorName*>
|
||||
| 607 | Reader object failed to start monitor thread: %1 | This is an internal, unrecoverable error that indicates a failure in the smart card service. The most common cause is limited computer resources. Restarting the computer may resolve the issue.<br>%1 = Windows error code |
|
||||
| 608 | Reader monitor failed to create power down timer: %1 | This is an internal, unrecoverable error that indicates a failure in the smart card service. The most common cause is limited computer resources. Restarting the computer may resolve the issue.<br>%1 = Windows error code |
|
||||
| 609 | Reader monitor failed to create overlapped event: %1 | This is an internal, unrecoverable error that indicates a failure in the smart card service. The most common cause is limited computer resources. Restarting the computer may resolve the issue.<br>%1 = Windows error code |
|
||||
| 610 | Smart Card Reader '%2' rejected IOCTL %3: %1 If this error persists, your smart card or reader may not be functioning correctly.%n%nCommand Header: %4 | The reader cannot successfully transmit the indicated IOCTL to the smart card. This can indicate hardware failure, but this error can also occur if a smart card or smart card reader is removed from the system while an operation is in progress.<br>%1 = Windows error code<br>%2 = Name of the smart card reader<br>%3 = IOCTL that was sent<br>%4 = First 4 bytes of the command sent to the smart card |
|
||||
| 610 | Smart Card Reader '%2' rejected IOCTL %3: %1 If this error persists, your smart card or reader may not be functioning correctly.%n%nCommand Header: %4 | The reader cannot successfully transmit the indicated IOCTL to the smart card. This is a benign error that does not affect end use of a smart card and can be ignored.<br>%1 = Windows error code<br>%2 = Name of the smart card reader<br>%3 = IOCTL that was sent<br>%4 = First 4 bytes of the command sent to the smart card |
|
||||
| 611 | Smart Card Reader initialization failed | This is an internal, unrecoverable error that indicates a failure in the smart card service. The most common cause is limited computer resources. Restarting the computer may resolve this issue. |
|
||||
| 612 | Reader insertion monitor error retry threshold reached: %1 | This occurs when a smart card reader fails several times to respond properly to the IOCTL, which indicates whether a smart card is present in the reader. The smart card reader is marked as defective, and it is not recognized by the service until it is removed from the computer and reinserted or until the computer is restarted.<br>%1 = Windows error code |
|
||||
| 615 | Reader removal monitor error retry threshold reached: %1 | This occurs when a smart card reader fails several times to respond properly to the IOCTL, which indicates whether a smart card is present in the reader. The smart card reader is marked as defective, and it is not recognized by the service until it is removed from the computer and reinserted or until the computer is restarted.<br>%1 = Windows error code |
|
||||
| 616 | Reader monitor '%2' received uncaught error code: %1 | This occurs when a smart card reader fails several times to respond properly to the IOCTL, which indicates whether a smart card is present in the reader. The smart card reader is marked as defective, and it is not recognized by the service until it is removed from the computer and reinserted or until the computer is restarted.<br>%1 = Windows error code<br>%2 = Reader name |
|
||||
| 617 | Reader monitor '%1' exception -- exiting thread | An unknown error occurred while monitoring a smart card reader for smart card insertions and removals. The smart card reader is marked as defective, and it is not recognized by the service until it is removed from the computer and reinserted or until the computer is restarted.<br>%1 = Smart card reader name |
|
||||
| 618 | Smart Card Resource Manager encountered an unrecoverable internal error. | This is an internal, unrecoverable error that indicates a failure in the smart card service. The most common cause is limited computer resources. Restarting the computer may resolve the issue. |
|
||||
| 621 | Server Control failed to access start event: %1 | This is an internal, unrecoverable error that indicates a failure in the smart card service. The most common cause is limited computer resources. Restarting the computer may resolve the issue.<br>%1 = Windows error code |
|
||||
| 621 | Server Control failed to access start event: %1 | This is an internal, unrecoverable error that indicates a failure in the smart card service. The most common cause is limited computer resources. Restarting the computer may resolve the issue. This error may also occur if the event is queried before the smart card service is ready. In this case the error is benign and can be ignored.<br>%1 = Windows error code |
|
||||
| 622 | Server Control failed to access stop event: %1 | This is an internal, unrecoverable error that indicates a failure in the smart card service. The most common cause is limited computer resources. Restarting the computer may resolve the issue.<br>%1 = Windows error code |
|
||||
|
||||
## Smart card Plug and Play events
|
||||
|
@ -9,7 +9,7 @@
|
||||
#### [Exposure score](microsoft-defender-atp/tvm-exposure-score.md)
|
||||
#### [Configuration score](microsoft-defender-atp/configuration-score.md)
|
||||
#### [Security recommendation](microsoft-defender-atp/tvm-security-recommendation.md)
|
||||
#### [Remediation](microsoft-defender-atp/tvm-remediation.md)
|
||||
#### [Remediation and exception](microsoft-defender-atp/tvm-remediation.md)
|
||||
#### [Software inventory](microsoft-defender-atp/tvm-software-inventory.md)
|
||||
#### [Weaknesses](microsoft-defender-atp/tvm-weaknesses.md)
|
||||
#### [Scenarios](microsoft-defender-atp/threat-and-vuln-mgt-scenarios.md)
|
||||
@ -122,10 +122,13 @@
|
||||
##### [NetworkCommunicationEvents](microsoft-defender-atp/advanced-hunting-networkcommunicationevents-table.md)
|
||||
##### [ProcessCreationEvents](microsoft-defender-atp/advanced-hunting-processcreationevents-table.md)
|
||||
##### [RegistryEvents](microsoft-defender-atp/advanced-hunting-registryevents-table.md)
|
||||
##### [DeviceTvmSoftwareInventoryVulnerabilities](microsoft-defender-atp/advanced-hunting-tvm-softwareinventory-table.md)
|
||||
##### [DeviceTvmSoftwareVulnerabilitiesKB](microsoft-defender-atp/advanced-hunting-tvm-softwarevulnerability-table.md)
|
||||
##### [DeviceTvmSecureConfigurationAssessment](microsoft-defender-atp/advanced-hunting-tvm-configassessment-table.md)
|
||||
##### [DeviceTvmSecureConfigurationAssessmentKB](microsoft-defender-atp/advanced-hunting-tvm-secureconfigkb-table.md)
|
||||
#### [Apply query best practices](microsoft-defender-atp/advanced-hunting-best-practices.md)
|
||||
#### [Stream Advanced hunting events to Azure Event Hubs](microsoft-defender-atp/raw-data-export-event-hub.md)
|
||||
|
||||
|
||||
#### [Custom detections]()
|
||||
##### [Understand custom detection rules](microsoft-defender-atp/overview-custom-detections.md)
|
||||
##### [Create and manage custom detections rules](microsoft-defender-atp/custom-detection-rules.md)
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Threat Protection (Windows 10)
|
||||
description: Learn how Microsoft Defender ATP helps protect against threats.
|
||||
keywords: threat protection, Microsoft Defender Advanced Threat Protection, attack surface reduction, next generation protection, endpoint detection and response, automated investigation and response, microsoft threat experts, secure score, advanced hunting, cyber threat hunting
|
||||
keywords: threat protection, Microsoft Defender Advanced Threat Protection, attack surface reduction, next generation protection, endpoint detection and response, automated investigation and response, microsoft threat experts, secure score, advanced hunting, cyber threat hunting, web threat protection
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -64,7 +64,7 @@ The attack surface reduction set of capabilities provide the first line of defen
|
||||
- [Application control](windows-defender-application-control/windows-defender-application-control.md)
|
||||
- [Device control](device-guard/introduction-to-device-guard-virtualization-based-security-and-windows-defender-application-control.md)
|
||||
- [Exploit protection](microsoft-defender-atp/exploit-protection.md)
|
||||
- [Network protection](microsoft-defender-atp/network-protection.md), [Web protection](microsoft-defender-atp/web-protection-overview.md)
|
||||
- [Network protection](microsoft-defender-atp/network-protection.md), [web protection](microsoft-defender-atp/web-protection-overview.md)
|
||||
- [Controlled folder access](microsoft-defender-atp/controlled-folders.md)
|
||||
- [Network firewall](windows-firewall/windows-firewall-with-advanced-security.md)
|
||||
- [Attack surface reduction rules](microsoft-defender-atp/attack-surface-reduction.md)
|
||||
|
@ -25,6 +25,8 @@ ms.date: 10/08/2019
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-advancedhuntingref-abovefoldlink)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
The [Advanced hunting](advanced-hunting-overview.md) schema is made up of multiple tables that provide either event information or information about machines and other entities. To effectively build queries that span multiple tables, you need to understand the tables and the columns in the Advanced hunting schema.
|
||||
|
||||
## Schema tables
|
||||
@ -45,6 +47,10 @@ Table and column names are also listed within the Microsoft Defender Security Ce
|
||||
| **[LogonEvents](advanced-hunting-logonevents-table.md)** | Sign-ins and other authentication events |
|
||||
| **[ImageLoadEvents](advanced-hunting-imageloadevents-table.md)** | DLL loading events |
|
||||
| **[MiscEvents](advanced-hunting-miscevents-table.md)** | Multiple event types, including events triggered by security controls such as Windows Defender Antivirus and exploit protection |
|
||||
| **[DeviceTvmSoftwareInventoryVulnerabilities](advanced-hunting-tvm-softwareinventory-table.md)** | Vulnerabilities in your software inventory |
|
||||
| **[DeviceTvmSoftwareVulnerabilitiesKB ](advanced-hunting-tvm-softwarevulnerability-table.md)** | Publicly-available vulnerabilities and whether they exist in your software inventory |
|
||||
| **[DeviceTvmSecureConfigurationAssessment](advanced-hunting-tvm-configassessment-table.md)** | Security configuration assessment information |
|
||||
| **[DeviceTvmSecureConfigurationAssessmentKB](advanced-hunting-tvm-secureconfigkb-table.md)** | Basis of security configuration assessment such as security industry standards and benchmarks |
|
||||
|
||||
## Related topics
|
||||
- [Advanced hunting overview](advanced-hunting-overview.md)
|
||||
|
@ -0,0 +1,53 @@
|
||||
---
|
||||
title: DeviceTvmSecureConfigurationAssessment table in the Advanced hunting schema
|
||||
description: Learn about the DeviceTvmSecureConfigurationAssessment table in the Advanced hunting schema, such as machine ID, computer name, operating system platform, security configuration details, impact, and compliance information.
|
||||
keywords: advanced hunting, atp query, device management, query atp data, query tvm data, query security configuration, intellisense, atp telemetry, events, events telemetry, azure log analytics, description, DeviceTvmSecureConfigurationAssessment
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 10/27/2019
|
||||
---
|
||||
|
||||
# DeviceTvmSecureConfigurationAssessment
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-advancedhuntingref-abovefoldlink)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
Each row in the DeviceTvmSecureConfigurationAssessment table contains an assessment event for a specific security configuration. Use this reference to check the latest assessment results and determine whether device are compliant.
|
||||
|
||||
For information on other tables in the Advanced hunting schema, see [the Advanced hunting reference](advanced-hunting-reference.md).
|
||||
|
||||
| Column name | Data type | Description |
|
||||
|-------------|-----------|-------------|
|
||||
| MachineId | string | Unique identifier for the machine in the service |
|
||||
| ComputerName | string | Fully qualified domain name (FQDN) of the machine |
|
||||
| OSPlatform | string | Platform of the operating system running on the machine. This indicates specific operating systems, including variations within the same family, such as Windows 10 and Windows 7.|
|
||||
| Timestamp | datetime |Date and time when the record was generated|
|
||||
| ConfigurationId | string | Unique identifier for a specific configuration |
|
||||
| ConfigurationCategory | string | Category or grouping to which the configuration belongs: Application, OS, Network, Accounts, Security controls|
|
||||
| ConfigurationSubcategory | string |Subcategory or subgrouping to which the configuration belongs. In many cases, this describes specific capabilities or features. |
|
||||
| ConfigurationImpact | string | Rated impact of the configuration to the overall configuration score (1-10) |
|
||||
| IsCompliant | boolean | Indicates whether the configuration or policy is properly configured |
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Advanced hunting overview](overview-hunting.md)
|
||||
- [All Advanced hunting tables](advanced-hunting-reference.md)
|
||||
- [Advanced hunting query best practices](advanced-hunting-best-practices.md)
|
||||
- [Query data using Advanced hunting](advanced-hunting.md)
|
@ -0,0 +1,53 @@
|
||||
---
|
||||
title: DeviceTvmSecureConfigurationAssessmentKB table in the Advanced hunting schema
|
||||
description: Learn about the DeviceTvmSecureConfigurationAssessmentKB table in the Advanced hunting schema, security configuration details, and the associated industry benchmarks that it adheres to.
|
||||
keywords: advanced hunting, atp query, device management, query atp data, query tvm data, query security configuration, intellisense, atp telemetry, events, events telemetry, azure log analytics, description, MITRE ATT&CK framework, DeviceTvmSecureConfigurationAssessmentKB
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 10/27/2019
|
||||
---
|
||||
|
||||
# DeviceTvmSecureConfigurationAssessmentKB
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-advancedhuntingref-abovefoldlink)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
The DeviceTvmSecureConfigurationAssessmentKB table in the Advanced hunting schema contains information about the various secure configuration TVM checks during assessments related to your organization. An example of a security configuration is to block JavaScript or VBScript from launching downloaded executable content to prevent accidentally downloading malicious files in your network. Use this reference to construct queries that return information from the table.
|
||||
|
||||
For information on other tables in the Advanced hunting schema, see [the Advanced hunting reference](advanced-hunting-reference.md).
|
||||
|
||||
| Column name | Data type | Description |
|
||||
|-------------|-----------|-------------|
|
||||
| ConfigurationId | string | Unique identifier for a specific configuration |
|
||||
| ConfigurationImpact | string | Rated impact of the configuration to the overall configuration score (1-10) |
|
||||
| ConfigurationName | string | Display name of the configuration |
|
||||
| ConfigurationDescription | string | Description of the configuration |
|
||||
| RiskDescription | string | Description of the associated risk |
|
||||
| ConfigurationCategory | string | Category or grouping to which the configuration belongs: Application, OS, Network, Accounts, Security controls|
|
||||
| ConfigurationSubcategory | string |Subcategory or subgrouping to which the configuration belongs. In many cases, this describes specific capabilities or features. |
|
||||
| ConfigurationBenchmarks | string | List of industry benchmarks recommending the same or similar configuration |
|
||||
| RelatedMitreTechniques | string | List of Mitre ATT&CK framework techniques related to the configuration |
|
||||
| RelatedMitreTactics | string | List of Mitre ATT&CK framework tactics related to the configuration|
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Advanced hunting overview](overview-hunting.md)
|
||||
- [All Advanced hunting tables](advanced-hunting-reference.md)
|
||||
- [Advanced hunting query best practices](advanced-hunting-best-practices.md)
|
||||
- [Query data using Advanced hunting](advanced-hunting.md)
|
@ -0,0 +1,56 @@
|
||||
---
|
||||
title: DeviceTvmSoftwareInventoryVulnerabilities table in the Advanced hunting schema
|
||||
description: Learn about the DeviceTvmSoftwareInventoryVulnerabilities table in the Advanced hunting schema, such as operating system platform, version, and architecture, software vendor, name, and version, CVE ID, vulnerability severity, and descriptions
|
||||
keywords: advanced hunting, atp query, device management, query atp data, query tvm data, query software inventory, query software vulnerability inventory, intellisense, atp telemetry, events, events telemetry, azure log analytics, description, DeviceTvmSoftwareInventoryVulnerabilities
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 10/27/2019
|
||||
---
|
||||
|
||||
# DeviceTvmSoftwareInventoryVulnerabilities
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-advancedhuntingref-abovefoldlink)
|
||||
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
The DeviceTvmSoftwareInventoryVulnerabilities table in the Advanced hunting schema contains an inventory of the software on your devices as well as any known vulnerabilities in the software products. Use this reference to construct queries that return information from the table.
|
||||
|
||||
For information on other tables in the Advanced hunting schema, see [the Advanced hunting reference](advanced-hunting-reference.md).
|
||||
|
||||
| Column name | Data type | Description |
|
||||
|-------------|-----------|-------------|
|
||||
| MachineId | string | Unique identifier for the machine in the service |
|
||||
| ComputerName | string | Fully qualified domain name (FQDN) of the machine |
|
||||
| OSPlatform | string | Platform of the operating system running on the machine. This indicates specific operating systems, including variations within the same family, such as Windows 10 and Windows 7.|
|
||||
| OSVersion | string | Version of the operating system running on the machine |
|
||||
| OSArchitecture | string | Architecture of the operating system running on the machine|
|
||||
| SoftwareVendor | string | Severity level assigned to the security vulnerability based on the CVSS score and dynamic factors influenced by the threat landscape|
|
||||
| SoftwareName | string | Name of the software product|
|
||||
|SoftwareVersion | string | Version number of the software product|
|
||||
| CveId | string | Unique identifier assigned to the security vulnerability under the Common Vulnerabilities and Exposures (CVE) system|
|
||||
| VulnerabilitySeverityLevel | string | Severity level assigned to the security vulnerability based on the CVSS score and dynamic factors influenced by the threat landscape|
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Advanced hunting overview](overview-hunting.md)
|
||||
- [All Advanced hunting tables](advanced-hunting-reference.md)
|
||||
- [Advanced hunting query best practices](advanced-hunting-best-practices.md)
|
||||
- [Query data using Advanced hunting](advanced-hunting.md)
|
@ -0,0 +1,51 @@
|
||||
---
|
||||
title: DeviceTvmSoftwareVulnerabilitiesKB table in the Advanced hunting schema
|
||||
description: Learn about the DeviceTvmSoftwareVulnerabilitiesKB table in the Advanced hunting schema, such as CVE ID, CVSS score, exploit availability, vulnerability severity, last modified time, date the vulnerability was disclosed to public, and affected software in your network.
|
||||
keywords: advanced hunting, atp query, device management, query atp data, query tvm data, query software vulnerability inventory, intellisense, atp telemetry, events, events telemetry, azure log analytics, description, DeviceTvmSoftwareVulnerabilitiesKB
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 10/27/2019
|
||||
---
|
||||
|
||||
# DeviceTvmSoftwareVulnerabilitiesKB
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-advancedhuntingref-abovefoldlink)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
The DeviceTvmSoftwareInventoryVulnerabilities table in the Advanced hunting schema contains information about the vulnerabilities Threat & Vulnerability Management assesses devices for. Use this reference along with DeviceTvmSoftwareInventoryVulnerabilities to construct queries that return information on the metadata related to the vulnerabilities in your inventory.
|
||||
|
||||
For information on other tables in the Advanced hunting schema, see [the Advanced hunting reference](advanced-hunting-reference.md).
|
||||
|
||||
| Column name | Data type | Description |
|
||||
|-------------|-----------|-------------|
|
||||
| CveId | string | Unique identifier assigned to the security vulnerability under the Common Vulnerabilities and Exposures (CVE) system|
|
||||
| CvssScore | string | Severity score assigned to the security vulnerability under th Common Vulnerability Scoring System (CVSS)|
|
||||
| IsExploitAvailable | boolean | Indicates whether exploit code for the vulnerability is publicly available|
|
||||
| VulnerabilitySeverityLevel | string | Severity level assigned to the security vulnerability based on the CVSS score and dynamic factors influenced by the threat landscape|
|
||||
| LastModifiedTime | datetime | Date and time the item or related metadata was last modified|
|
||||
| PublishedDate | datetime | Date vulnerability was disclosed to public|
|
||||
| VulnerabilityDescription | string | Description of vulnerability and associated risks|
|
||||
| AffectedSoftware | string | List of all software products affected by the vulnerability|
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Advanced hunting overview](overview-hunting.md)
|
||||
- [All Advanced hunting tables](advanced-hunting-reference.md)
|
||||
- [Advanced hunting query best practices](advanced-hunting-best-practices.md)
|
||||
- [Query data using Advanced hunting](advanced-hunting.md)
|
@ -60,7 +60,7 @@ See how you can [improve your security configuration](https://docs.microsoft.com
|
||||
>- RS3 customers | [KB 4516071](https://support.microsoft.com/help/4516071/windows-10-update-kb4516071)
|
||||
>
|
||||
>To download the security updates:
|
||||
>1. Go to [Microsoft Update Catalog](http://www.catalog.update.microsoft.com/home.aspx).
|
||||
>1. Go to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/home.aspx).
|
||||
>2. Key-in the security update KB number that you need to download, then click **Search**.
|
||||
|
||||
## Related topics
|
||||
@ -68,7 +68,7 @@ See how you can [improve your security configuration](https://docs.microsoft.com
|
||||
- [Threat & Vulnerability Management dashboard overview](tvm-dashboard-insights.md)
|
||||
- [Exposure score](tvm-exposure-score.md)
|
||||
- [Security recommendations](tvm-security-recommendation.md)
|
||||
- [Remediation](tvm-remediation.md)
|
||||
- [Remediation and exception](tvm-remediation.md)
|
||||
- [Software inventory](tvm-software-inventory.md)
|
||||
- [Weaknesses](tvm-weaknesses.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
|
After Width: | Height: | Size: 24 KiB |
After Width: | Height: | Size: 17 KiB |
After Width: | Height: | Size: 42 KiB |
After Width: | Height: | Size: 82 KiB |
After Width: | Height: | Size: 20 KiB |
After Width: | Height: | Size: 63 KiB |
After Width: | Height: | Size: 24 KiB |
After Width: | Height: | Size: 80 KiB |
After Width: | Height: | Size: 37 KiB |
After Width: | Height: | Size: 56 KiB |
After Width: | Height: | Size: 65 KiB |
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 64 KiB |
After Width: | Height: | Size: 28 KiB |
Before Width: | Height: | Size: 1.3 KiB After Width: | Height: | Size: 1.2 KiB |
Before Width: | Height: | Size: 1.2 KiB After Width: | Height: | Size: 1.1 KiB |
@ -37,7 +37,7 @@ Microsoft Defender Advanced Threat Protection requires one of the following Micr
|
||||
- Windows 10 Enterprise E5
|
||||
- Windows 10 Education E5
|
||||
- Microsoft 365 E5 (M365 E5) which includes Windows 10 Enterprise E5
|
||||
- Microsoft 365 E3 (M365 E3) with Identity and Threat Protection package
|
||||
|
||||
|
||||
For more information on the array of features in Windows 10 editions, see [Compare Windows 10 editions](https://www.microsoft.com/windowsforbusiness/compare).
|
||||
|
||||
|
@ -62,7 +62,7 @@ Microsoft Defender ATP’s Threat & Vulnerability Management allows security adm
|
||||
- [Exposure score](tvm-exposure-score.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Security recommendations](tvm-security-recommendation.md)
|
||||
- [Remediation](tvm-remediation.md)
|
||||
- [Remediation and exception](tvm-remediation.md)
|
||||
- [Software inventory](tvm-software-inventory.md)
|
||||
- [Weaknesses](tvm-weaknesses.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
|
@ -46,6 +46,12 @@ The following features are included in the preview release:
|
||||
|
||||
- [Threat & Vulnerability Management Report inaccuracy](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation#report-inaccuracy) <BR> You can report a false positive when you see any vague, inaccurate, incomplete, or already remediated [security recommendation](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation#report-inaccuracy), [software inventory](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-software-inventory#report-inaccuracy), and [discovered vulnerabilities](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-weaknesses#report-inaccuracy).
|
||||
|
||||
- [Threat & Vulnerability Management Advanced Hunting Schemas](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-registryevents-table) <BR> You can now use the Threat & Vulnerability Management tables in the Advanced hunting schema to query about software inventory, vulnerability knowledgebase, security configuration assessment, and security configuration knowledgebase.
|
||||
|
||||
- [Threat & Vulnerability Management role-based access controls](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/user-roles#create-roles-and-assign-the-role-to-an-azure-active-directory-group) <BR> You can now use the new permissions to allow maximum flexibility to create SecOps-oriented roles, Threat & Vulnerability Management-oriented roles, or hybrid roles so only authorized users are accessing specific data to do their task. You can also achieve even further granularity by specifying whether a Threat & Vulnerability Management role can only view vulnerability-related data, or can create and manage remediation and exceptions.
|
||||
|
||||
- [Threat & Vulnerability Management granular exploit details](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-weaknesses) <BR> You can now see a comprehensive set of details on the vulnerabilities found in your machine to give you informed decision on your next steps. The threat insights icon now shows more granular details, such as if the exploit is a part of an exploit kit, connected to specific advanced persistent campaigns or activity groups for which, Threat Analytics report links are provided that you can read, has associated zero-day exploitation news, disclosures, or related security advisories.
|
||||
|
||||
- [Machine health and compliance report](machine-reports.md) The machine health and compliance report provides high-level information about the devices in your organization.
|
||||
|
||||
- [Information protection](information-protection-in-windows-overview.md)<BR>
|
||||
|
@ -143,12 +143,40 @@ When an exception is created for a recommendation, the recommendation is no long
|
||||
2. Click the top-most recommendation. A flyout panel opens with the recommendation details.
|
||||
|
||||
3. Click **Exception options**.
|
||||

|
||||
|
||||
4. Select your justification for the exception you need to file instead of remediating the security recommendation in question. Fill out the justification context, then set the exception duration.
|
||||
|
||||
> 
|
||||
|
||||
5. Click **Submit**. A confirmation message at the top of the page indicates that the exception has been created.
|
||||

|
||||
|
||||
6. Navigate to the **Remediation** page under the **Threat & Vulnerability Management** menu and click the **Exceptions** tab to view all your exceptions (current and past).
|
||||

|
||||
|
||||
## Use Advanced hunting query to search for machines with High active alerts or critical CVE public exploit
|
||||
|
||||
1. Go to **Advanced hunting** from the left-hand navigation pane.
|
||||
|
||||
2. Scroll down to the TVM advanced hunting schemas to familiarize yourself with the column names.
|
||||
|
||||
3. Enter the following queries:
|
||||
|
||||
```
|
||||
// Search for machines with High active alerts or Critical CVE public exploit
|
||||
DeviceTvmSoftwareInventoryVulnerabilities
|
||||
| join kind=inner(DeviceTvmSoftwareVulnerabilitiesKB) on CveId
|
||||
| where IsExploitAvailable == 1 and CvssScore >= 7
|
||||
| summarize NumOfVulnerabilities=dcount(CveId),
|
||||
ComputerName=any(ComputerName) by MachineId
|
||||
| join kind =inner(AlertEvents) on MachineId
|
||||
| summarize NumOfVulnerabilities=any(NumOfVulnerabilities),
|
||||
ComputerName=any(ComputerName) by MachineId, AlertId
|
||||
| project ComputerName, NumOfVulnerabilities, AlertId
|
||||
| order by NumOfVulnerabilities desc
|
||||
|
||||
```
|
||||
|
||||
## Related topics
|
||||
- [Risk-based Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)
|
||||
@ -156,6 +184,8 @@ When an exception is created for a recommendation, the recommendation is no long
|
||||
- [Exposure score](tvm-exposure-score.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Security recommendations](tvm-security-recommendation.md)
|
||||
- [Remediation](tvm-remediation.md)
|
||||
- [Remediation and exception](tvm-remediation.md)
|
||||
- [Software inventory](tvm-software-inventory.md)
|
||||
- [Weaknesses](tvm-weaknesses.md)
|
||||
- [Advanced hunting overview](overview-hunting.md)
|
||||
- [All Advanced hunting tables](advanced-hunting-reference.md)
|
||||
|
@ -53,7 +53,7 @@ Area | Description
|
||||
(2) Threat & Vulnerability Management navigation pane | Use the navigation pane to move across the **Threat and Vulnerability Management Dashboard**, **Security recommendations**, **Remediation**, **Software inventory**, and **Weaknesses**.
|
||||
**Dashboards** | Get a high-level view of the organization exposure score, organization configuration score, machine exposure distribution, top security recommendations, top vulnerable software, top remediation activities, and top exposed machines data.
|
||||
**Security recommendations** | See the list of security recommendations, their related components, insights, number or exposed devices, impact, and request for remediation. You can click each item on the list, a flyout panel opens with vulnerability details, open the software page, see the remediation, and exception options. You can also open a ticket in Intune if your machines are joined through Azure Active Directory and you have enabled your Intune connections in Microsoft Defender ATP. See [Security recommendations](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation) for more information.
|
||||
**Remediation** | See the remediation activity, related component, remediation type, status, due date, option to export the remediation and process data to CSV, and active exceptions. See [Remediation](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-remediation) for more information.
|
||||
**Remediation** | See the remediation activity, related component, remediation type, status, due date, option to export the remediation and process data to CSV, and active exceptions. See [Remediation and exception](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-remediation) for more information.
|
||||
**Software inventory** | See the list of applications, versions, weaknesses, whether there’s an exploit found on the application, prevalence in the organization, how many were installed, how many exposed devices are there, and the numerical value of the impact. You can select each item in the list and opt to open the software page which shows the associated vulnerabilities, misconfigurations, affected machine, version distribution details, and missing KBs or security updates. See [Software inventory](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-software-inventory) for more information.
|
||||
**Weaknesses** | See the list of common vulnerabilities and exposures, the severity, its common vulnerability scoring system (CVSS) V3 score, related software, age, when it was published, related threat alerts, and how many exposed machines are there. You can select each item in the list and it opens a flyout panel with the vulnerability description and other details. See [Weaknesses](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-weaknesses) for more information.
|
||||
(3) Threat & Vulnerability Management dashboard | Access the **Exposure score**, **Configuration score**, **Exposure distribution**, **Top security recommendations**, **Top vulnerable software**, **Top remediation activities**, and **Top exposed machines**.
|
||||
@ -73,7 +73,7 @@ See [Microsoft Defender ATP icons](https://docs.microsoft.com/windows/security/t
|
||||
- [Exposure score](tvm-exposure-score.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Security recommendations](tvm-security-recommendation.md)
|
||||
- [Remediation](tvm-remediation.md)
|
||||
- [Remediation and exception](tvm-remediation.md)
|
||||
- [Software inventory](tvm-software-inventory.md)
|
||||
- [Weaknesses](tvm-weaknesses.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
|
@ -42,7 +42,7 @@ Reduce the exposure score by addressing what needs to be remediated based on the
|
||||
- [Threat & Vulnerability Management dashboard overview](tvm-dashboard-insights.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Security recommendations](tvm-security-recommendation.md)
|
||||
- [Remediation](tvm-remediation.md)
|
||||
- [Remediation and exception](tvm-remediation.md)
|
||||
- [Software inventory](tvm-software-inventory.md)
|
||||
- [Weaknesses](tvm-weaknesses.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Remediation
|
||||
description: You can lower down your organization's exposure from vulnerabilities and increase your security configuration by remediating the security recommendations. Threat & Vulnerability Management bridges the gap between security administration and IT administration during remediation process. It does so by creating a security task or ticket through integration with Microsoft Intune and Microsoft System Center Configuration Manager (SCCM).
|
||||
title: Remediation and exception
|
||||
description: You can lower down your organization's exposure from vulnerabilities and increase your security configuration by remediating the security recommendations or filing exceptions provided there are compensation controls. Threat & Vulnerability Management bridges the gap between security administration and IT administration during remediation process. It does so by creating a security task or ticket through integration with Microsoft Intune and Microsoft System Center Configuration Manager (SCCM).
|
||||
keywords: microsoft defender atp tvm remediation, mdatp tvm, threat & vulnerability management, threat & vulnerability management remediation, tvm remediation intune, tvm remediation sccm
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -17,7 +17,7 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/11/2019
|
||||
---
|
||||
# Remediation
|
||||
# Remediation and exception
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
@ -47,11 +47,62 @@ When you submit a remediation request from Threat & Vulnerability Management, it
|
||||
|
||||
It creates a security task which will be tracked in Threat & Vulnerability Management **Remediation** page, and it also creates a remediation ticket in Microsoft Intune.
|
||||
|
||||
You also have the option to export all remediation activity data to CSV for records, reporting purposes, or if you want to notify your IT administration counterpart that a remediation ticket has been submitted.
|
||||
|
||||
The dashboard will show that status of your top remediation activities. Click any of the entries and it will take you to the **Remediation** page. You can mark the remediation activity as completed after the IT administration team remediates the task.
|
||||
|
||||
However, if the security recommendation stemmed from a false positive report, or if there are existing business justification that blocks the remediation, such as compensating control, productivity needs, compliance, or if there's already a planned remediation grace period, you can file an exception and indicate the reason. The exceptions you've filed will also show up in the **Remediation** page, in the **Exceptions** tab.
|
||||
## When to file for exception instead of remediating issues
|
||||
You can file exceptions to exclude certain recommendation from showing up in reports and affecting risk scores or secure scores.
|
||||
|
||||
When you select a security recommendation, it opens up a flyout screen with details and options for your next step. You can either **Open software page**, choose from **Remediation options**, go through **Exception options** to file for exceptions, or **Report inaccuracy**.
|
||||
|
||||
Select **Exception options** and a flyout screen opens.
|
||||
|
||||

|
||||
|
||||
### Exception justification
|
||||
If the security recommendation stemmed from a false positive report, or if there are existing business justification that blocks the remediation, such as compensating control, productivity needs, compliance, or if there's already a planned remediation grace period, you can file an exception and indicate the reason. The following list details the justifications behind the exception options:
|
||||
|
||||
- **Compensating/alternate control** - A 3rd party control that mitigates this recommendation exists, for example, if Network Firewall - - prevents access to a machine, third party antivirus
|
||||
- **Productivity/business need** - Remediation will impact productivity or interrupt business-critical workflow
|
||||
- **Accept risk** - Poses low risk and/or implementing a compensating control is too expensive
|
||||
- **Planned remediation (grace)** - Already planned but is awaiting execution or authorization
|
||||
- **Other** - False positive
|
||||
|
||||
|
||||

|
||||
|
||||
### Exception visibility
|
||||
The exceptions you've filed will show up in the **Remediation** page, in the **Exceptions** tab.
|
||||
However, you also have the option to filter your view based on exception justification, type, and status.
|
||||
|
||||

|
||||
|
||||
Aside from that, there's also an option to **Show exceptions** at the bottom of the **Top security recommendations** card in the dashboard.
|
||||
|
||||

|
||||
|
||||
Clicking the link opens up to the **Security recommendations** page, where you can select the item exempted item with details.
|
||||
|
||||

|
||||
|
||||
### Actions on exceptions
|
||||
- Cancel - You can cancel the exceptions you've filed any time
|
||||
- Resurface - Your exception automatically becomes void and resurfaces in the security recommendation list when dynamic environmental factors change, which adversely affect the exposure impact associated with a recommendation that had previously been excluded
|
||||
|
||||
### Exception status
|
||||
- **Canceled** - The exception has been canceled and is no longer in effect
|
||||
- **Expired** - The exception that you've filed is no longer in effect
|
||||
- **In effect** - The exception that you've filed is in progress
|
||||
|
||||
### Exception impact on scores
|
||||
Creating an exception can potentially affect the Exposure Score (for both types of weaknesses) and Secure Score (for configurations) of your organization in the following manner:
|
||||
- **No impact** - Removes the recommendation from the lists (which can be reverse through filters), but will not affect the scores
|
||||
- **Mitigation-like impact** - As if the recommendation was mitigated (and scores will be adjusted accordingly) when you select it as a compensating control.
|
||||
- **Hybrid** - Provides visibility on both No impact and Mitigation-like impact. It shows both the Exposure Score and Secure Score results out of the exception option that you made
|
||||
|
||||
The exception impact shows on both the Security recommendations page column and in the flyout pane.
|
||||
|
||||

|
||||
|
||||
## Related topics
|
||||
- [Risk-based Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)
|
||||
|
@ -79,14 +79,12 @@ You can report a false positive when you see any vague, inaccurate, incomplete,
|
||||
6. Click **Submit**. Your feedback is immediately sent to the Threat & Vulnerability Management experts with its context.
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
- [Risk-based Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)
|
||||
- [Threat & Vulnerability Management dashboard overview](tvm-dashboard-insights.md)
|
||||
- [Exposure score](tvm-exposure-score.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Remediation](tvm-remediation.md)
|
||||
- [Remediation and exception](tvm-remediation.md)
|
||||
- [Software inventory](tvm-software-inventory.md)
|
||||
- [Weaknesses](tvm-weaknesses.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
|
@ -63,6 +63,6 @@ You can report a false positive when you see any vague, inaccurate version, inco
|
||||
- [Exposure score](tvm-exposure-score.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Security recommendation](tvm-security-recommendation.md)
|
||||
- [Remediation](tvm-remediation.md)
|
||||
- [Remediation and exception](tvm-remediation.md)
|
||||
- [Weaknesses](tvm-weaknesses.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
|
@ -15,25 +15,32 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/11/2019
|
||||
ms.date: 10/31/2019
|
||||
---
|
||||
# Weaknesses
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
Threat & Vulnerability Management leverages the same signals in Microsoft Defender ATP's endpoint protection to scan and detect vulnerabilities.
|
||||
|
||||
The **Weaknesses** page lists down the vulnerabilities found in the infected software running in your organization, their severity, Common Vulnerability Scoring System (CVSS) rating, its prevalence in your organization, corresponding breach, and threat insights.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>To boost your vulnerability assessment detection rates, download the following mandatory security updates and deploy them in your network:
|
||||
>To boost your vulnerability assessment detection rates, you can download the following mandatory security updates and deploy them in your network:
|
||||
>- 19H1 customers | [KB 4512941](https://support.microsoft.com/help/4512941/windows-10-update-kb4512941)
|
||||
>- RS5 customers | [KB 4516077](https://support.microsoft.com/help/4516077/windows-10-update-kb4516077)
|
||||
>- RS4 customers | [KB 4516045](https://support.microsoft.com/help/4516045/windows-10-update-kb4516045)
|
||||
>- RS3 customers | [KB 4516071](https://support.microsoft.com/help/4516071/windows-10-update-kb4516071)
|
||||
><P>Downloading the above-mentioned security updates will be mandatory starting Patch Tuesday, October 8, 2019.
|
||||
|
||||
## Navigate through your organization's weaknesses page
|
||||
You can see the list of vulnerabilities in four ways:
|
||||
You can access the list of vulnerabilities in a few places in the portal:
|
||||
- Global search
|
||||
- Weaknesses option in the navigation menu
|
||||
- Top vulnerable software widget in the dashboard
|
||||
- Discovered vulnerabilities page in the machine page
|
||||
|
||||
*Vulnerabilities in global search*
|
||||
1. Click the global search drop-down menu.
|
||||
@ -46,12 +53,13 @@ You can see the list of vulnerabilities in four ways:
|
||||
|
||||
*Weaknesses page in the menu*
|
||||
1. Go to the Threat & Vulnerability Management navigation menu and select **Weaknesses** to open up the list of vulnerabilities found in your organization.
|
||||
2. Select the vulnerability that you want to investigate to open up a flyout panel with the vulnerability details, such as: CVE description, CVE ID, exploits available, CVSS V3 rating, severity, publish, and update dates.
|
||||
2. Select the vulnerability that you want to investigate to open up a flyout panel with the vulnerability details, such as: CVE description, CVE ID, exploits available, CVSS V3 rating, severity, dates when it was published and updated, related software, exploit kits available, vulnerability type, link to useful reference, and number of exposed machines which users can also export.
|
||||

|
||||
|
||||
*Top vulnerable software widget in the dashboard*
|
||||
1. Go to the Threat & Vulnerability Management dashboard and scroll down to the **Top vulnerable software** widget. You will see the number of vulnerabilities found in each software along with threat information and a high-level view of the device exposure trend over time.
|
||||

|
||||
2. Click the software that you want to investigate and it takes you to the software page. You will the weaknesses found in your machine per severity level, in which machines are they installed, version distribution, and the corresponding security recommendation.
|
||||
2. Click the software that you want to investigate and it takes you to the software page. You will see the weaknesses found in your machine per severity level, in which machines are they installed, version distribution, and the corresponding security recommendation.
|
||||
3. Select the **Discovered vulnerabilities** tab.
|
||||
4. Select the vulnerability that you want to investigate to open up a flyout panel with the vulnerability details, such as: CVE description, CVE ID, exploits available, CVSS V3 rating, severity, publish, and update dates.
|
||||
|
||||
@ -68,22 +76,25 @@ You can see the list of vulnerabilities in four ways:
|
||||
5. Select the vulnerability that you want to investigate to open up a flyout panel with the vulnerability details, such as: CVE description, CVE ID, exploits available, CVSS V3 rating, severity, publish, and update dates.
|
||||
|
||||
## How it works
|
||||
When new vulnerabilities are released, you would want know how many of your assets are exposed. You can see the list of vulnerabilities and the details in the **Weaknesses** page.
|
||||
When new vulnerabilities are released, you would want to know how many of your assets are exposed. You can see the list of vulnerabilities and the details in the **Weaknesses** page.
|
||||
|
||||
If the **Exposed Machines** column shows 0, that means you are not infected.
|
||||
If the **Exposed Machines** column shows 0, that means you are not at risk.
|
||||
|
||||
If there's a number in the **Exposed Machines**, that means you need to remediate the vulnerabilities in those machines because they put the rest of your assets and your organization at risk.
|
||||
If exposed machines exist, that means you need to remediate the vulnerabilities in those machines because they put the rest of your assets and your organization at risk.
|
||||
|
||||
You can also see the related alert and threat insights in the **Threat** column.
|
||||
|
||||
The breach insights icons are highlighted if there are active alerts associated with the vulnerability found in your organization.
|
||||
The breach insights icon is highlighted if there is a vulnerability found in your organization. Prioritize an investigation because it means there might be a breach in your organization.
|
||||
|
||||

|
||||
|
||||
The threat insights icons are highlighted if there are associated exploits in the vulnerability found in your organization. It also shows whether the threat is connected to specific campaign for which, Threat Analytics report links are provided that you can read.
|
||||
The threat insights icons are highlighted if there are associated exploits in the vulnerability found in your organization. It also shows whether the threat is a part of an exploit kit, connected to specific advanced persistent campaigns or activity groups for which, Threat Analytics report links are provided that you can read, has zero-day exploitation news, disclosures, or related security advisories.
|
||||
|
||||

|
||||
|
||||
|
||||
>[!NOTE]
|
||||
> Always prioritize recommendations that are associated with ongoing threats. These recommendations are marked with the threat insight  icon and possible active alert  icon.
|
||||
> Always prioritize recommendations that are associated with ongoing threats. These recommendations are marked with the threat insight  icon and breach insight  icon.
|
||||
|
||||
## Report inaccuracy
|
||||
|
||||
@ -115,6 +126,6 @@ You can report a false positive when you see any vague, inaccurate, missing, or
|
||||
- [Exposure score](tvm-exposure-score.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Security recommendation](tvm-security-recommendation.md)
|
||||
- [Remediation](tvm-remediation.md)
|
||||
- [Remediation and exception](tvm-remediation.md)
|
||||
- [Software inventory](tvm-software-inventory.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
|
@ -19,12 +19,12 @@ ms.topic: article
|
||||
|
||||
# Create and manage roles for role-based access control
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-roles-abovefoldlink)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
## Create roles and assign the role to an Azure Active Directory group
|
||||
The following steps guide you on how to create roles in Microsoft Defender Security Center. It assumes that you have already created Azure Active Directory user groups.
|
||||
|
||||
@ -37,25 +37,31 @@ The following steps guide you on how to create roles in Microsoft Defender Secur
|
||||
- **Role name**
|
||||
- **Description**
|
||||
- **Permissions**
|
||||
- **View data** - Users can view information in the portal.
|
||||
- **Alerts investigation** - Users can manage alerts, initiate automated investigations, collect investigation packages, manage machine tags, and export machine timeline.
|
||||
- **Active remediation actions** - Users can take response actions and approve or dismiss pending remediation actions.
|
||||
- **Manage portal system settings** - Users can configure storage settings, SIEM and threat intel API settings (applies globally), advanced settings, automated file uploads, roles and machine groups.
|
||||
- **View data** - Users can view information in the portal.
|
||||
>[!NOTE]
|
||||
>To view Threat & Vulnerability Management data, select **Threat and vulnerability management**.
|
||||
|
||||
- **Alerts investigation** - Users can manage alerts, initiate automated investigations, collect investigation packages, manage machine tags, and export machine timeline.
|
||||
- **Active remediation actions** - Users can take response actions and approve or dismiss pending remediation actions.
|
||||
>[!NOTE]
|
||||
>To enable your Security operation personnel to choose remediation options and file exceptions, select **Threat and vulnerability management - Remediation handling**, and **Threat and vulnerability management - Exception handling**.
|
||||
|
||||
- **Manage portal system settings** - Users can configure storage settings, SIEM and threat intel API settings (applies globally), advanced settings, automated file uploads, roles and machine groups.
|
||||
|
||||
> [!NOTE]
|
||||
> This setting is only available in the Microsoft Defender ATP administrator (default) role.
|
||||
|
||||
- **Manage security settings** - Users can configure alert suppression settings, manage allowed/blocked lists for automation, create and manage custom detections, manage folder exclusions for automation, onboard and offboard machines, and manage email notifications.
|
||||
- **Manage security settings** - Users can configure alert suppression settings, manage allowed/blocked lists for automation, create and manage custom detections, manage folder exclusions for automation, onboard and offboard machines, and manage email notifications.
|
||||
|
||||
- **Live response capabilities** - Users can take basic or advanced live response commands.
|
||||
- Basic commands allow users to:
|
||||
- Start a live response session
|
||||
- Run read only live response commands on a remote machine
|
||||
- Advanced commands allow users to:
|
||||
- Run basic actions
|
||||
- Download a file from the remote machine
|
||||
- View a script from the files library
|
||||
- Run a script on the remote machine from the files library take read and write commands.
|
||||
- **Live response capabilities** - Users can take basic or advanced live response commands.
|
||||
- Basic commands allow users to:
|
||||
- Start a live response session
|
||||
- Run read only live response commands on a remote machine
|
||||
- Advanced commands allow users to:
|
||||
- Run basic actions
|
||||
- Download a file from the remote machine
|
||||
- View a script from the files library
|
||||
- Run a script on the remote machine from the files library take read and write commands.
|
||||
|
||||
For more information on the available commands, see [Investigate machines using Live response](live-response.md).
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Monitoring web browsing security in Microsoft Defender ATP
|
||||
description: Use web protection in Microsoft Defender ATP to monitor web browsing security
|
||||
keywords: web protection, web browsing, monitoring, reports, cards, domain list, security, phishing, malware, exploit, websites, network protection, Edge, Internet Explorer, Chrome, Firefox, web browser
|
||||
keywords: web protection, web threat protection, web browsing, monitoring, reports, cards, domain list, security, phishing, malware, exploit, websites, network protection, Edge, Internet Explorer, Chrome, Firefox, web browser
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -22,9 +22,7 @@ ms.date: 08/30/2019
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-main-abovefoldlink&rtc=1)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
Web protection lets you monitor your organization’s web browsing security through reports under **Reports > Web protection** in the Microsoft Defender Security Center. The report contains the following cards that provide web threat detection statistics:
|
||||
Web protection lets you monitor your organization’s web browsing security through reports under **Reports > Web protection** in the Microsoft Defender Security Center. The report contains cards that provide web threat detection statistics.
|
||||
|
||||
- **Web threat protection detections over time** — this trending card displays the number of web threats detected by type during the selected time period (Last 30 days, Last 3 months, Last 6 months)
|
||||
|
||||
@ -44,7 +42,7 @@ Web protection categorizes malicious and unwanted websites as:
|
||||
- **Custom indicator** — websites whose URLs or domains you've added to your [custom indicator list](manage-indicators.md) for blocking
|
||||
|
||||
## View the domain list
|
||||
Clicking on a specific web threat category in the **Web threat protection summary** card opens the **Domains** page, which shows a list of the domains prefiltered under that threat category. The page provides the following information for each domain:
|
||||
Select a specific web threat category in the **Web threat protection summary** card to open the **Domains** page and display the list of the domains under that threat category. The page provides the following information for each domain:
|
||||
|
||||
- **Access count** — number of requests for URLs in the domain
|
||||
- **Blocks** — number of times requests were blocked
|
||||
@ -52,7 +50,7 @@ Clicking on a specific web threat category in the **Web threat protection summar
|
||||
- **Threat category** — type of web threat
|
||||
- **Machines** — number of machines with access attempts
|
||||
|
||||
Selecting a domain opens a panel that shows the list of URLs in that domain that have been accessed. The panel also lists machines that have attempted to access URLs in the domain.
|
||||
Select a domain to view the list of machines that have attempted to access URLs in that domain as well as the list of URLs.
|
||||
|
||||
## Related topics
|
||||
- [Web protection overview](web-protection-overview.md)
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Overview of web protection in Microsoft Defender ATP
|
||||
description: Learn about web protection in Microsoft Defender ATP and how it can protect your organization
|
||||
keywords: web protection, web browsing, security, phishing, malware, exploit, websites, network protection, Edge, Internet Explorer, Chrome, Firefox, web browser
|
||||
keywords: web protection, web threat protection, web browsing, security, phishing, malware, exploit, websites, network protection, Edge, Internet Explorer, Chrome, Firefox, web browser
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -22,18 +22,16 @@ ms.date: 08/30/2019
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-main-abovefoldlink&rtc=1)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
Web protection in Microsoft Defender ATP uses [network protection](network-protection.md) to secure your machines against web threats. By integrating with Microsoft Edge and popular third-party browsers like Chrome and Firefox, web protection stops web threats without a web proxy and can protect machines while they are away or on premises. Web protection stops access to phishing sites, malware vectors, exploit sites, untrusted or low-reputation sites, as well as sites that you have blocked in your [custom indicator list](manage-indicators.md).
|
||||
|
||||
Web protection in Microsoft Defender ATP leverages [network protection](network-protection.md) to secure your machines against web threats without relying on a web proxy, providing security for devices that are either away or on premises. By integrating with Microsoft Edge as well as popular third-party browsers like Chrome and Firefox, web protection stops access to phishing sites, malware vectors, exploit sites, untrusted or low-reputation sites, as well as sites that you have blocked in your [custom indicator list](manage-indicators.md).
|
||||
>[!Note]
|
||||
>It can take up to an hour for machines to receive new customer indicators.
|
||||
|
||||
With web protection, you also get:
|
||||
- Comprehensive visibility into web threats affecting your organization
|
||||
- Investigation capabilities over web-related threat activity through alerts and comprehensive profiles of URLs and the machines that access these URLs
|
||||
- A full set of security features that track general access trends to malicious and unwanted websites
|
||||
|
||||
>[!Note]
|
||||
>It can take up to an hour for machines to receive new customer indicators.
|
||||
|
||||
## Prerequisites
|
||||
Web protection uses network protection to provide web browsing security on Microsoft Edge and third-party web browsers.
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Respond to web threats in Microsoft Defender ATP
|
||||
description: Respond to alerts related to malicious and unwanted websites. Understand how web threat protection informs end users through their web browsers and Windows notifications
|
||||
keywords: web protection, web browsing, alerts, response, security, phishing, malware, exploit, websites, network protection, Edge, Internet Explorer, Chrome, Firefox, web browser, notifications, end users, Windows notifications, blocking page,
|
||||
keywords: web protection, web threat protection, web browsing, alerts, response, security, phishing, malware, exploit, websites, network protection, Edge, Internet Explorer, Chrome, Firefox, web browser, notifications, end users, Windows notifications, blocking page,
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -22,8 +22,6 @@ ms.date: 08/30/2019
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-main-abovefoldlink&rtc=1)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
|
||||
Web protection in Microsoft Defender ATP lets you efficiently investigate and respond to alerts related to malicious websites and websites in your custom indicator list.
|
||||
|
||||
## View web threat alerts
|
||||
@ -62,10 +60,10 @@ You can also check the machine that attempted to access a blocked URL. Selecting
|
||||
With web protection in Microsoft Defender ATP, your end users will be prevented from visiting malicious or unwanted websites using Microsoft Edge or other browsers. Because blocking is performed by [network protection](network-protection.md), they will see a generic error from the web browser. They will also see a notification from Windows.
|
||||
|
||||

|
||||
*Web threat blocked by Microsoft Edge*
|
||||
*Web threat blocked on Microsoft Edge*
|
||||
|
||||

|
||||
*Web threat blocked by the Chrome web browser*
|
||||

|
||||
*Web threat blocked on Chrome*
|
||||
|
||||
## Related topics
|
||||
- [Web protection overview](web-protection-overview.md)
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Installing Microsoft Defender ATP for Mac manually
|
||||
ms.reviewer:
|
||||
description: Describes how to install Microsoft Defender ATP for Mac manually, from the command line.
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, mojave, high sierra, sierra
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, catalina, mojave, high sierra
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Installing Microsoft Defender ATP for Mac with Microsoft Intune
|
||||
ms.reviewer:
|
||||
description: Describes how to install Microsoft Defender ATP for Mac, using Microsoft Intune.
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, mojave, high sierra, sierra
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, catalina, mojave, high sierra
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -295,7 +295,7 @@ Once the Intune changes are propagated to the enrolled devices, you can see them
|
||||
2. Select **App type=Other/Line-of-business app**.
|
||||
3. Select **file=wdav.pkg.intunemac**. Select **OK** to upload.
|
||||
4. Select **Configure** and add the required information.
|
||||
5. Use **macOS Sierra 10.12** as the minimum OS and set *Ignore app version* to **Yes**. Other settings can be any arbitrary value.
|
||||
5. Use **macOS High Sierra 10.13** as the minimum OS and set *Ignore app version* to **Yes**. Other settings can be any arbitrary value.
|
||||
|
||||
> [!CAUTION]
|
||||
> Failure to set *Ignore app version* to **Yes** impacts the ability of the application to receive updates through Microsoft AutoUpdate. See [Deploy updates for Microsoft Defender ATP for Mac](microsoft-defender-atp-mac-updates.md) for additional information about how the product is updated.
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Installing Microsoft Defender ATP for Mac with JAMF
|
||||
ms.reviewer:
|
||||
description: Describes how to install Microsoft Defender ATP for Mac, using JAMF.
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, mojave, high sierra, sierra
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, catalina, mojave, high sierra
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Installing Microsoft Defender ATP for Mac with different MDM product
|
||||
description: Describes how to install Microsoft Defender ATP for Mac on other management solutions.
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, macos, mojave, high sierra, sierra
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, macos, catalina, mojave, high sierra
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Set preferences for Microsoft Defender ATP for Mac
|
||||
ms.reviewer:
|
||||
description: Describes how to configure Microsoft Defender ATP for Mac in enterprises.
|
||||
keywords: microsoft, defender, atp, mac, management, preferences, enterprise, intune, jamf, macos, mojave, high sierra, sierra
|
||||
keywords: microsoft, defender, atp, mac, management, preferences, enterprise, intune, jamf, macos, catalina, mojave, high sierra
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Microsoft Defender ATP for Mac Resources
|
||||
ms.reviewer:
|
||||
description: Describes resources for Microsoft Defender ATP for Mac, including how to uninstall it, how to collect diagnostic logs, CLI commands, and known issues with the product.
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, mojave, high sierra, sierra
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, catalina, mojave, high sierra
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
|
@ -20,6 +20,10 @@ ms.topic: conceptual
|
||||
|
||||
# What's new in Microsoft Defender Advanced Threat Protection for Mac
|
||||
|
||||
## 100.72.15
|
||||
|
||||
- Bug fixes
|
||||
|
||||
## 100.70.99
|
||||
|
||||
- Addressed an issue that impacts the ability of some users to upgrade to macOS Catalina when real-time protection is enabled. This sporadic issue was caused by Microsoft Defender ATP locking files within Catalina upgrade package while scanning them for threats, which led to failures in the upgrade sequence.
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Microsoft Defender ATP for Mac
|
||||
ms.reviewer:
|
||||
description: Describes how to install and use Microsoft Defender ATP for Mac.
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, mojave, high sierra, sierra
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, catalina, mojave, high sierra
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
@ -43,8 +43,10 @@ If you have any feedback that you would like to share, submit it by opening Micr
|
||||
|
||||
> [!CAUTION]
|
||||
> The three most recent major releases of macOS are supported. Beta versions of macOS are not supported.
|
||||
>
|
||||
> macOS Sierra (10.12) support will end on January 1, 2020.
|
||||
|
||||
- Supported macOS versions: 10.14 (Mojave), 10.13 (High Sierra), 10.12 (Sierra)
|
||||
- Supported macOS versions: 10.15 (Catalina), 10.14 (Mojave), 10.13 (High Sierra)
|
||||
- Disk space: 650 MB
|
||||
|
||||
After you've enabled the service, you may need to configure your network or firewall to allow outbound connections between it and your endpoints.
|
||||
|
@ -36,19 +36,44 @@ The general steps for expanding the S mode base policy on your devices are to ge
|
||||
|
||||
Refer to [Deploy multiple Windows Defender Application Control Policies](deploy-multiple-windows-defender-application-control-policies.md) for guidance on creating supplemental policies and [Deploy Windows Defender Application Control policy rules and file rules](select-types-of-rules-to-create.md) to choose the right type of rules to create for your policy.
|
||||
|
||||
> [!Note]
|
||||
> Policies which are supplementing the S mode base policy must use **-SupplementsBasePolicyID 5951A96A-E0B5-4D3D-8FB8-3E5B61030784**, as this is the S mode policy ID.
|
||||
Below are a basic set of instructions for creating an S mode supplemental policy:
|
||||
- Create a new base policy using [New-CIPolicy](https://docs.microsoft.com/powershell/module/configci/new-cipolicy?view=win10-ps)
|
||||
|
||||
```powershell
|
||||
New-CIPolicy -MultiplePolicyFormat -ScanPath <path> -UserPEs -FilePath "<path>\SupplementalPolicy.xml" -Level Publisher -Fallback Hash
|
||||
```
|
||||
- Change it to a supplemental policy using [Set-CIPolicyIdInfo](https://docs.microsoft.com/powershell/module/configci/set-cipolicyidinfo?view=win10-ps)
|
||||
|
||||
```powershell
|
||||
Set-CIPolicyIdInfo -SupplementsBasePolicyID 5951A96A-E0B5-4D3D-8FB8-3E5B61030784 -FilePath "<path>\SupplementalPolicy.xml"
|
||||
```
|
||||
Policies which are supplementing the S mode base policy must use **-SupplementsBasePolicyID 5951A96A-E0B5-4D3D-8FB8-3E5B61030784**, as this is the S mode policy ID.
|
||||
- Put the policy in enforce mode using [Set-RuleOption](https://docs.microsoft.com/powershell/module/configci/set-ruleoption?view=win10-ps)
|
||||
|
||||
```powershell
|
||||
Set-RuleOption -FilePath "<path>\SupplementalPolicy.xml>" -Option 3 –Delete
|
||||
```
|
||||
This deletes the ‘audit mode’ qualifier.
|
||||
- Convert to .bin using [ConvertFrom-CIPolicy](https://docs.microsoft.com/powershell/module/configci/convertfrom-cipolicy?view=win10-ps)
|
||||
|
||||
```powershell
|
||||
ConvertFrom-CIPolicy -XmlFilePath "<path>\SupplementalPolicy.xml" -BinaryFilePath "<path>\SupplementalPolicy.bin>
|
||||
```
|
||||
|
||||
2. Sign policy
|
||||
|
||||
Supplemental S mode policies must be digitally signed. To sign your policy, you can choose to use the Device Guard Signing Service or your organization's custom Public Key Infrastructure (PKI). Refer to [Use the Device Guard Signing Portal in the Microsoft Store for Business](use-device-guard-signing-portal-in-microsoft-store-for-business.md) for guidance on using DGSS and [Create a code signing cert for WDAC](create-code-signing-cert-for-windows-defender-application-control.md) for guidance on signing using an internal CA.
|
||||
|
||||
Once your policy is signed, you must authorize the signing certificate you used to sign the policy and optionally one or more additional signers that can be used to sign updates to the policy in the future. Use Add-SignerRule to add the signing certificate to the WDAC policy, filling in the correct path and filenames for `<policypath>` and `<certpath>`:
|
||||
Once your policy is signed, you must authorize the signing certificate you used to sign the policy and optionally one or more additional signers that can be used to sign updates to the policy in the future. Use Add-SignerRule to add the signing certificate to the WDAC policy:
|
||||
|
||||
```powershell
|
||||
Add-SignerRule -FilePath <policypath> -CertificatePath <certpath> -User -Update`
|
||||
```
|
||||
Rename your policy to "{PolicyID}.p7b" after you've signed it. PolicyID can be found by inspecting the Supplemental Policy XML
|
||||
|
||||
`Add-SignerRule -FilePath <policypath> -CertificatePath <certpath> -User -Update`
|
||||
3. Deploy the signed supplemental policy using Microsoft Intune
|
||||
|
||||
Upload the signed policy to Intune and assign it to user or device groups. Intune will generate tenant- and device- specific authorization tokens. Intune then deploys the corresponding authorization token and supplemental policy to each device in the assigned group. Together, these expand the S mode base policy on the device.
|
||||
<!-- Intune link?-->
|
||||
Go to the Azure portal online and navigate to the Microsoft Intune page, then go to the Client apps blade and select 'S mode supplemental policies'. Upload the signed policy to Intune and assign it to user or device groups. Intune will generate tenant- and device- specific authorization tokens. Intune then deploys the corresponding authorization token and supplemental policy to each device in the assigned group. Together, these expand the S mode base policy on the device.
|
||||
|
||||
> [!Note]
|
||||
> When updating your supplemental policy, ensure that the new version number is strictly greater than the previous one. Using the same version number is not allowed by Intune. Refer to [Set-CIPolicyVersion](https://docs.microsoft.com/powershell/module/configci/set-cipolicyversion?view=win10-ps) for information on setting the version number.
|
||||
@ -153,7 +178,7 @@ Below is a sample policy that allows kernel debuggers, PowerShell ISE, and Regis
|
||||
```
|
||||
# Policy Removal
|
||||
> [!Note]
|
||||
> There is currently a policy deletion error, with a fix expected in the 2D update in late February 2020. Devices of users who are unenrolled will still have their WDAC policies removed. In the mentime, IT Pros are recommended to update their policy with the below 'empty' policy which makes no changes to S mode.
|
||||
> This feature currently has a known a policy deletion bug, with a fix expected in the 2D update in late February 2020. Devices of users who are unenrolled will still have their WDAC policies removed. In the mentime, IT Pros are recommended to update their policy with the below 'empty' policy which makes no changes to S mode.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
@ -24,9 +24,6 @@ ms.date: 05/17/2019
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
The restriction of only having a single code integrity policy active on a system at any given time has felt limiting for customers in situations where multiple policies with different intents would be useful. Beginning with Windows 10 version 1903, WDAC supports multiple simultaneous code integrity policies for one device in order to enable the following scenarios:
|
||||
|
||||
1. Enforce and Audit Side-by-Side
|
||||
@ -53,7 +50,7 @@ Note that multiple policies will not work on pre-1903 systems.
|
||||
In order to allow multiple policies to exist and take effect on a single system, policies must be created using the new Multiple Policy Format. The "MultiplePolicyFormat" switch in [New-CIPolicy](https://docs.microsoft.com/powershell/module/configci/new-cipolicy?view=win10-ps) results in 1) random GUIDs being generated for the policy ID and 2) the policy type being specified as base. The below is an example of creating a new policy in the multiple policy format.
|
||||
|
||||
```powershell
|
||||
New-CIPolicy -MultiplePolicyFormat -ScanPath '.\temp\' -UserPEs -FilePath ".\policy.xml" -Level Publisher -Fallback Hash
|
||||
New-CIPolicy -MultiplePolicyFormat -ScanPath "<path>" -UserPEs -FilePath ".\policy.xml" -Level Publisher -Fallback Hash
|
||||
```
|
||||
|
||||
Optionally, you can choose to make the new base policy supplementable (allow supplemental policies).
|
||||
@ -70,19 +67,19 @@ Add-SignerRule -FilePath <string> -CertificatePath <string> [-Kernel] [-User] [-
|
||||
|
||||
### Supplemental Policy Creation
|
||||
|
||||
In order to create a supplemental policy, begin by creating a new policy in the Multiple Policy Format. From there, use Set-CIPolicyIdInfo to convert it to a supplemental policy and specify which base policy it expands.
|
||||
- "SupplementsBasePolicyID": guid of new supplemental policy
|
||||
- "BasePolicyToSupplementPath": base policy that the supplemental policy applies to
|
||||
In order to create a supplemental policy, begin by creating a new policy in the Multiple Policy Format. From there, use Set-CIPolicyIdInfo to convert it to a supplemental policy and specify which base policy it expands. You can use either SupplementsBasePolicyID or BasePolicyToSupplementPath to specify the base policy.
|
||||
- "SupplementsBasePolicyID": GUID of base policy that the supplemental policy applies to
|
||||
- "BasePolicyToSupplementPath": path to base policy file that the supplemental policy applies to
|
||||
|
||||
```powershell
|
||||
Set-CIPolicyIdInfo [-FilePath] <string> [-PolicyName <string>] [-SupplementsBasePolicyID <guid>] [-BasePolicyToSupplementPath <string>] [-ResetPolicyID] [-PolicyId <string>] [<CommonParameters>]
|
||||
```
|
||||
|
||||
Note that "ResetPolicyId" reverts a supplemental policy to a base policy, and resets the policy guids back to a random guid.
|
||||
Note that "ResetPolicyId" reverts a supplemental policy to a base policy, and resets the policy GUIDs back to a random GUID.
|
||||
|
||||
### Merging policies
|
||||
|
||||
When merging, the policy type and ID of the leftmost/first policy specified is used. If the leftmost is a base policy with ID \<ID>, then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID \<ID>.
|
||||
When merging, the policy type and ID of the leftmost/first policy specified is used. If the leftmost is a base policy with ID \<ID>, then regardless of what the GUIDs and types are for any subsequent policies, the merged policy will be a base policy with ID \<ID>.
|
||||
|
||||
### Deploying policies
|
||||
|
||||
|