From 0fdaf19fa12b69041e28878be969ba1eed0a9d6e Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Mon, 1 Aug 2016 23:13:45 +1000 Subject: [PATCH] add br --- ...ndpoints-sccm-windows-defender-advanced-threat-protection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/configure-endpoints-sccm-windows-defender-advanced-threat-protection.md b/windows/keep-secure/configure-endpoints-sccm-windows-defender-advanced-threat-protection.md index ff36349580..1d009b3943 100644 --- a/windows/keep-secure/configure-endpoints-sccm-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/configure-endpoints-sccm-windows-defender-advanced-threat-protection.md @@ -116,7 +116,7 @@ If there are failed deployments (endpoints with **Error**, **Requirements Not Me ![SCCM showing successful deployment with no errors](images/sccm-deployment.png) -**Check that the endpoints are compliant with the Windows Defender ATP service:** +**Check that the endpoints are compliant with the Windows Defender ATP service:**
You can set a compliance rule for configuration item in System Center Configuration Manager to monitor your deployment. This rule should be a *non-remediating* compliance rule configuration item that monitors the value of a registry key on targeted machines.