From 0cc0bc0da3a7723723e0c2fe15540fc75584f6f7 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Thu, 6 Aug 2020 16:08:49 -0700 Subject: [PATCH] add note --- .../microsoft-defender-atp/configure-endpoints-sccm.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm.md b/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm.md index 9f8783af04..3033df5316 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm.md +++ b/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm.md @@ -82,7 +82,10 @@ For more information, see [Configure Detection Methods in System Center 2012 R2 For each device, you can set a configuration value to state whether samples can be collected from the device when a request is made through Microsoft Defender Security Center to submit a file for deep analysis. -This is typically done through Configuration Manager. You can set a compliance rule for configuration item in Configuration Manager to change the sample share setting on a device. +>[!NOTE] +>These configuration settings are typically done through Configuration Manager. + +You can set a compliance rule for configuration item in Configuration Manager to change the sample share setting on a device. This rule should be a *remediating* compliance rule configuration item that sets the value of a registry key on targeted devices to make sure they’re complaint.