mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client into FromPrivateRepo
This commit is contained in:
commit
745246fa44
@ -6,8 +6,12 @@ ms.mktglfcycl: deploy
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: security
|
ms.pagetype: security
|
||||||
author: aadake
|
author: aadake
|
||||||
ms.date: 12/20/2018
|
ms.author: justinha
|
||||||
ms.topic: article
|
manager: dansimp
|
||||||
|
audience: ITPro
|
||||||
|
ms.collection: M365-security-compliance
|
||||||
|
ms.topic: conceptual
|
||||||
|
ms.date: 03/26/2019
|
||||||
---
|
---
|
||||||
|
|
||||||
# Kernel DMA Protection for Thunderbolt™ 3
|
# Kernel DMA Protection for Thunderbolt™ 3
|
||||||
@ -98,12 +102,12 @@ No, Kernel DMA Protection only protects against drive-by DMA attacks after the O
|
|||||||
DMA-remapping is supported for specific device drivers, and is not universally supported by all devices and drivers on a platform. To check if a specific driver is opted into DMA-remapping, check the values corresponding to the DMA Remapping Policy property in the Details tab of a device in Device Manager*. A value of 0 or 1 means that the device driver does not support DMA-remapping. A value of 2 means that the device driver supports DMA-remapping.
|
DMA-remapping is supported for specific device drivers, and is not universally supported by all devices and drivers on a platform. To check if a specific driver is opted into DMA-remapping, check the values corresponding to the DMA Remapping Policy property in the Details tab of a device in Device Manager*. A value of 0 or 1 means that the device driver does not support DMA-remapping. A value of 2 means that the device driver supports DMA-remapping.
|
||||||
Please check the driver instance for the device you are testing. Some drivers may have varying values depending on the location of the device (internal vs. external).
|
Please check the driver instance for the device you are testing. Some drivers may have varying values depending on the location of the device (internal vs. external).
|
||||||
|
|
||||||
*For Windows 10 versions 1803 and 1809, the property field in Device Manager uses a GUID, as highlighted in the image below
|
*For Windows 10 versions 1803 and 1809, the property field in Device Manager uses a GUID, as highlighted in the following image.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
### What should I do if the drivers for my Thunderbolt™ 3 peripherals do not support DMA-remapping?
|
### What should I do if the drivers for my Thunderbolt™ 3 peripherals do not support DMA-remapping?
|
||||||
If the peripherals do have class drivers provided by Windows 10, please use these drivers on your systems. If there are no class drivers provided by Windows for your peripherals, please contact your peripheral vendor/driver vendor to update the driver to support this functionality.
|
If the peripherals do have class drivers provided by Windows 10, please use these drivers on your systems. If there are no class drivers provided by Windows for your peripherals, please contact your peripheral vendor/driver vendor to update the driver to support this functionality. Details for driver compatibility requirements can be found at the [Microsoft Partner Center](https://partner.microsoft.com/dashboard/collaborate/packages/4142).
|
||||||
|
|
||||||
### Do Microsoft drivers support DMA-remapping?
|
### Do Microsoft drivers support DMA-remapping?
|
||||||
In Windows 10 1803 and beyond, the Microsoft inbox drivers for USB XHCI (3.x) Controllers, Storage AHCI/SATA Controllers and Storage NVMe Controllers support DMA-remapping.
|
In Windows 10 1803 and beyond, the Microsoft inbox drivers for USB XHCI (3.x) Controllers, Storage AHCI/SATA Controllers and Storage NVMe Controllers support DMA-remapping.
|
||||||
|
@ -14,7 +14,6 @@ manager: dansimp
|
|||||||
audience: ITPro
|
audience: ITPro
|
||||||
ms.collection: M365-security-compliance
|
ms.collection: M365-security-compliance
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.date: 12/14/2018
|
|
||||||
---
|
---
|
||||||
|
|
||||||
# Onboard servers to the Windows Defender ATP service
|
# Onboard servers to the Windows Defender ATP service
|
||||||
@ -45,7 +44,22 @@ For a practical guidance on what needs to be in place for licensing and infrastr
|
|||||||
|
|
||||||
## Windows Server 2012 R2 and Windows Server 2016
|
## Windows Server 2012 R2 and Windows Server 2016
|
||||||
|
|
||||||
To onboard Windows Server 2012 R2 and Windows Server 2016 to Windows Defender ATP, you’ll need to:
|
There are two options to onboard Windows Server 2012 R2 and Windows Server 2016 to Windows Defender ATP:
|
||||||
|
|
||||||
|
- **Option 1**: Onboard through Azure Security Center
|
||||||
|
- **Option 2**: Onboard through Windows Defender Security Center
|
||||||
|
|
||||||
|
### Option 1: Onboard servers through Azure Security Center
|
||||||
|
1. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||||
|
|
||||||
|
2. Select Windows Server 2012 R2 and 2016 as the operating system.
|
||||||
|
|
||||||
|
3. Click **Onboard Servers in Azure Security Center**.
|
||||||
|
|
||||||
|
4. Follow the onboarding instructions in [Windows Defender Advanced Threat Protection with Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-wdatp).
|
||||||
|
|
||||||
|
### Option 2: Onboard servers through Windows Defender Security Center
|
||||||
|
You'll need to tak the following steps if you choose to onboard servers through Windows Defender Security Center.
|
||||||
|
|
||||||
- For Windows Server 2012 R2: Configure and update System Center Endpoint Protection clients.
|
- For Windows Server 2012 R2: Configure and update System Center Endpoint Protection clients.
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Minimum requirements for Windows Defender ATP
|
title: Minimum requirements for Windows Defender ATP
|
||||||
description: Minimum network and data storage configuration, machine hardware and software requirements, and deployment channel requirements for Windows Defender ATP.
|
description: Understand the licensing requirements and requirements for onboarding machines to the sercvie
|
||||||
keywords: minimum requirements, Windows Defender Advanced Threat Protection minimum requirements, network and data storage, machine configuration, deployment channel
|
keywords: minimum requirements, licensing, comparison table
|
||||||
search.product: eADQiWindows 10XVcnh
|
search.product: eADQiWindows 10XVcnh
|
||||||
search.appverid: met150
|
search.appverid: met150
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
@ -15,7 +15,6 @@ manager: dansimp
|
|||||||
audience: ITPro
|
audience: ITPro
|
||||||
ms.collection: M365-security-compliance
|
ms.collection: M365-security-compliance
|
||||||
ms.topic: conceptual
|
ms.topic: conceptual
|
||||||
ms.date: 11/20/2018
|
|
||||||
---
|
---
|
||||||
|
|
||||||
# Minimum requirements for Windows Defender ATP
|
# Minimum requirements for Windows Defender ATP
|
||||||
|
Loading…
x
Reference in New Issue
Block a user