From 6a6252b3cab5f50e8b2f09d287a2ca6ebd6618e7 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Tue, 5 Dec 2017 11:29:33 -0800 Subject: [PATCH] updates --- ...indows-defender-advanced-threat-protection.md | 2 ++ ...indows-defender-advanced-threat-protection.md | 16 ++-------------- 2 files changed, 4 insertions(+), 14 deletions(-) diff --git a/windows/threat-protection/windows-defender-atp/configure-server-endpoints-windows-defender-advanced-threat-protection.md b/windows/threat-protection/windows-defender-atp/configure-server-endpoints-windows-defender-advanced-threat-protection.md index ba65c41f73..f4c6a1c0e1 100644 --- a/windows/threat-protection/windows-defender-atp/configure-server-endpoints-windows-defender-advanced-threat-protection.md +++ b/windows/threat-protection/windows-defender-atp/configure-server-endpoints-windows-defender-advanced-threat-protection.md @@ -40,6 +40,7 @@ To onboard your servers to Windows Defender ATP, you’ll need to: >[!TIP] > After onboarding the endpoint, you can choose to run a detection test to verify that an endpoint is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Windows Defender ATP endpoint](run-detection-test-windows-defender-advanced-threat-protection.md). + ### Turn on Server monitoring from the Windows Defender Security Center portal 1. In the navigation pane, select **Endpoint management** > **Servers**. @@ -48,6 +49,7 @@ To onboard your servers to Windows Defender ATP, you’ll need to: ![Image of server onboarding](images/atp-server-onboarding.png) + ### Install and configure Microsoft Monitoring Agent (MMA) to report sensor data to Windows Defender ATP diff --git a/windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md b/windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md index 1744a4efe7..6aa0dee94d 100644 --- a/windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md +++ b/windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md @@ -269,21 +269,9 @@ If the verification fails and your environment is using a proxy to connect to th ## Troubleshoot onboarding issues on a server If you encounter issues while onboarding a server, go through the following verification steps to address possible issues. -- Ensure that you have followed the guidance in the topic [Configure server endpoints](configure-server-endpoints-windows-defender-advanced-threat-protection.md) and have you've configured the necessary server endpoint proxy and Internet connectivity settings. +- [Ensure Microsoft Monitoring Agent (MMA) is installed and configured to report sensor data to the service](configure-server-endpoints-windows-defender-advanced-threat-protection.md#servermma) +- [Ensure that the server endpoint proxy and Internet connectivity settings are configured properly](configure-server-endpoints-windows-defender-advanced-threat-protection.md#servermma) -- Check that there is a Windows Defender Advanced Threat Protection Service running in the **Processes** tab in **Task Manager**. For example: - - ![Image of process view with Windows Defender Advanced Threat Protection Service running](images/atp-task-manager.png) - -- In **Event Viewer**, check **Event Viewer** > **Applications and Services Logs** > **Operation Manager** to see if there are any errors. - -- In **Services**, check if the **Microsoft Monitoring Agent** is running on the server. For example, - - ![Image of Services](images/atp-services.png) - -- Check to see that machines are reflected in the **Machines list** in the portal. - -- [Run a detection test](run-detection-test-windows-defender-advanced-threat-protection.md) on the server. ## Licensing requirements Windows Defender Advanced Threat Protection requires one of the following Microsoft Volume Licensing offers: