mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 08:17:23 +00:00
Merge branch 'master' into patch-2
This commit is contained in:
commit
91871c05e9
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Onboard Windows servers to the Microsoft Defender ATP service
|
title: Onboard Windows servers to the Microsoft Defender for Endpoint service
|
||||||
description: Onboard Windows servers so that they can send sensor data to the Microsoft Defender ATP sensor.
|
description: Onboard Windows servers so that they can send sensor data to the Microsoft Defender for Endpoint sensor.
|
||||||
keywords: onboard server, server, 2012r2, 2016, 2019, server onboarding, device management, configure Windows ATP servers, onboard Microsoft Defender Advanced Threat Protection servers
|
keywords: onboard server, server, 2012r2, 2016, 2019, server onboarding, device management, configure Windows ATP servers, onboard Microsoft Defender Advanced Threat Protection servers, onboard Microsoft Defender for Endpoint servers
|
||||||
search.product: eADQiWindows 10XVcnh
|
search.product: eADQiWindows 10XVcnh
|
||||||
search.appverid: met150
|
search.appverid: met150
|
||||||
ms.prod: m365-security
|
ms.prod: m365-security
|
||||||
@ -118,7 +118,7 @@ If your servers need to use a proxy to communicate with Defender for Endpoint, u
|
|||||||
|
|
||||||
- [Configure Windows to use a proxy server for all connections](configure-proxy-internet.md)
|
- [Configure Windows to use a proxy server for all connections](configure-proxy-internet.md)
|
||||||
|
|
||||||
If a proxy or firewall is in use, please ensure that servers can access all of the Microsoft Defender ATP service URLs directly and without SSL interception. For more information, see [enable access to Defender for Endpoint service URLs](configure-proxy-internet.md#enable-access-to-microsoft-defender-for-endpoint-service-urls-in-the-proxy-server). Use of SSL interception will prevent the system from communicating with the Defender for Endpoint service.
|
If a proxy or firewall is in use, please ensure that servers can access all of the Microsoft Defender for Endpoint service URLs directly and without SSL interception. For more information, see [enable access to Defender for Endpoint service URLs](configure-proxy-internet.md#enable-access-to-microsoft-defender-for-endpoint-service-urls-in-the-proxy-server). Use of SSL interception will prevent the system from communicating with the Defender for Endpoint service.
|
||||||
|
|
||||||
Once completed, you should see onboarded Windows servers in the portal within an hour.
|
Once completed, you should see onboarded Windows servers in the portal within an hour.
|
||||||
|
|
||||||
@ -161,7 +161,7 @@ You can onboard Windows Server (SAC) version 1803, Windows Server 2019, or Windo
|
|||||||
|
|
||||||
Support for Windows Server provides deeper insight into server activities, coverage for kernel and memory attack detection, and enables response actions.
|
Support for Windows Server provides deeper insight into server activities, coverage for kernel and memory attack detection, and enables response actions.
|
||||||
|
|
||||||
1. Configure Defender for Endpoint onboarding settings on the Windows server. For more information, see [Onboard Windows 10 devices](configure-endpoints.md).
|
1. Configure Defender for Endpoint onboarding settings on the Windows server using the same tools and methods for Windows 10 devices. For more information, see [Onboard Windows 10 devices](configure-endpoints.md).
|
||||||
|
|
||||||
2. If you're running a third-party antimalware solution, you'll need to apply the following Microsoft Defender AV passive mode settings. Verify that it was configured correctly:
|
2. If you're running a third-party antimalware solution, you'll need to apply the following Microsoft Defender AV passive mode settings. Verify that it was configured correctly:
|
||||||
|
|
||||||
|
@ -35,6 +35,13 @@ ms.technology: mde
|
|||||||
|
|
||||||
Follow the corresponding instructions depending on your preferred deployment method.
|
Follow the corresponding instructions depending on your preferred deployment method.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
> The status of a device will be switched to [Inactive](fix-unhealthy-sensors.md#inactive-devices) 7 days after offboarding. <br>
|
||||||
|
> Offboarded devices' data (such as Timeline, Alerts, Vulnerabilities, etc.) will remain in the portal until the configured [retention period](data-storage-privacy.md#how-long-will-microsoft-store-my-data-what-is-microsofts-data-retention-policy) expires. <br>
|
||||||
|
> The device's profile (without data) will remain in the [Devices List](machines-view-overview.md) for no longer than 180 days.
|
||||||
|
> In addition, devices that are not active in the last 30 days are not factored in on the data that reflects your organization's threat and vulnerability management [exposure score](tvm-exposure-score.md) and Microsoft Secure Score for Devices. <br>
|
||||||
|
> To view only active devices, you can filter by [health state](machines-view-overview.md#health-state), [device tags](machine-tags.md) or [machine groups](machine-groups.md).
|
||||||
|
|
||||||
## Offboard Windows 10 devices
|
## Offboard Windows 10 devices
|
||||||
- [Offboard devices using a local script](configure-endpoints-script.md#offboard-devices-using-a-local-script)
|
- [Offboard devices using a local script](configure-endpoints-script.md#offboard-devices-using-a-local-script)
|
||||||
- [Offboard devices using Group Policy](configure-endpoints-gp.md#offboard-devices-using-group-policy)
|
- [Offboard devices using Group Policy](configure-endpoints-gp.md#offboard-devices-using-group-policy)
|
||||||
@ -46,7 +53,3 @@ Follow the corresponding instructions depending on your preferred deployment met
|
|||||||
## Offboard non-Windows devices
|
## Offboard non-Windows devices
|
||||||
- [Offboard non-Windows devices](configure-endpoints-non-windows.md#offboard-non-windows-devices)
|
- [Offboard non-Windows devices](configure-endpoints-non-windows.md#offboard-non-windows-devices)
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
> Offboarded devices will remain in the portal until [retention period](data-storage-privacy.md#how-long-will-microsoft-store-my-data-what-is-microsofts-data-retention-policy) for the device's data expires. The status will be switched to ['Inactive'](fix-unhealthy-sensors.md#inactive-devices) 7 days after offboarding. <br>
|
|
||||||
> In addition, [Devices that are not active in the last 30 days are not factored in on the data that reflects your organization's threat and vulnerability management exposure score and Microsoft Secure Score for Devices.](tvm-dashboard-insights.md) <br>
|
|
||||||
> To view only active devices, you can filter by [health state](machines-view-overview.md#health-state) or by [device tags](machine-tags.md) and [groups](machine-groups.md) etc.
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user