From a87114c61cd1f3c7d34c1a2a32c8edca6a566e9b Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Tue, 26 Jul 2016 20:56:08 +1000 Subject: [PATCH] add 'local' to script --- ...ot-onboarding-windows-defender-advanced-threat-protection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md b/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md index 59aa4f699a..ebd9aecd30 100644 --- a/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md @@ -413,7 +413,7 @@ To ensure that sensor has service connectivity, follow the steps described in th If the verification fails and your environment is using a proxy to connect to the Internet, then follow the steps described in [Configure proxy and Internet connectivity settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md) topic. -## Troubleshoot onboarding issues using the script +## Troubleshoot onboarding issues using the local script If you configured your endpoints with a deployment tool that required a script, you can check the event viewer for the onboarding script results. **Check the result of the script**: