From 28c80731486674578e30cd8046d6f1eea8252a13 Mon Sep 17 00:00:00 2001 From: Dolcita Date: Tue, 19 Apr 2016 15:40:21 +1000 Subject: [PATCH] Update configure-endpoints-windows-advanced-threat-protection.md --- .../configure-endpoints-windows-advanced-threat-protection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/configure-endpoints-windows-advanced-threat-protection.md b/windows/keep-secure/configure-endpoints-windows-advanced-threat-protection.md index 197e07483d..b246b53e3e 100644 --- a/windows/keep-secure/configure-endpoints-windows-advanced-threat-protection.md +++ b/windows/keep-secure/configure-endpoints-windows-advanced-threat-protection.md @@ -68,7 +68,7 @@ For additional settings, see the [Additional configuration settings section](add Naama note: If it’s a package we create then we’ll set the necessary privileges, otherwise provide guidance (Omri: what is the necessary privileges?) ## Configure endpoints manually with registry changes -You can also manually onboard individual endpoints to Windows Defender ATP. You might want to do this when testing the service before you commit to onboarding all endpoints in your network. +You can also manually onboard individual endpoints to Windows Defender ATP. You might want to do this first when testing the service before you commit to onboarding all endpoints in your network. 1. Extract the contents of the configuration package to a location on the endpoint you want to onboard (for example, the Desktop).