From 3d9b6772ce578fcecc6bae58b71aac1e2a92b764 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Mon, 9 May 2016 20:44:30 +1000 Subject: [PATCH] add topic links --- windows/keep-secure/other-troubleshooting.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/windows/keep-secure/other-troubleshooting.md b/windows/keep-secure/other-troubleshooting.md index aae7819b77..16bdc09fb1 100644 --- a/windows/keep-secure/other-troubleshooting.md +++ b/windows/keep-secure/other-troubleshooting.md @@ -23,6 +23,14 @@ You might need to troubleshoot the onboarding process if you encounter issues. If you have completed the endpoint onboarding process and don't see endpoints in the [Machines view](investigate-machines-windows-defender-advanced-threat-protection.md) after 20 minutes, it might indicate an endpoint onboarding or a connectivity problem. +Go through the following verification topics to address this issue: + +- [Ensure that the endpoint is onboarded successfully](#Ensure-that-the-endpoint-is-onboarded-successfully) +- [Ensure that the Windows Defender ATP service is enabled](#Ensure-that-the-Windows-Defender-ATP-service-is-enabled) +- [Ensure that the telemetry and diagnostics service is enabled](#Ensure-that-the-telemetry-and-diagnostics-service-is-enabled) +- [Ensure that the Windows Defender ATP endpoint has internet connection](#Ensure-that-the-Windows-Defender-ATP-endpoint-has-internet-connection) + + ### Ensure that the endpoint is onboarded successfully If the endpoints aren't reporting correctly, you might need to check that the Windows Defender Advanced Threat Protection service was successfully onboarded on the endpoint.