From a93c55d624c983a05549d7b5d242c3020b333907 Mon Sep 17 00:00:00 2001 From: jborsecnik Date: Sun, 2 Feb 2020 18:15:14 -0800 Subject: [PATCH] staging problem solving --- ...lanning-and-deploying-advanced-security-audit-policies.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/windows/security/threat-protection/auditing/planning-and-deploying-advanced-security-audit-policies.md b/windows/security/threat-protection/auditing/planning-and-deploying-advanced-security-audit-policies.md index 108e534b4f..03e6d4b3bb 100644 --- a/windows/security/threat-protection/auditing/planning-and-deploying-advanced-security-audit-policies.md +++ b/windows/security/threat-protection/auditing/planning-and-deploying-advanced-security-audit-policies.md @@ -200,11 +200,6 @@ By using Group Policy, you can apply your security audit policy to defined group - Advanced security audit policy settings were introduced in Windows Server 2008 R2 and Windows 7. These advanced audit policies can only be applied to those operating systems and later versions by using Group Policy. - -> [!IMPORTANT]   -> Whether you apply advanced audit policies by using Group Policy or logon scripts, don't use both the basic audit policy settings under **Local Policies\\Audit Policy** *and* the advanced settings under **Security Settings\\Advanced Audit Policy Configuration**. Using both basic and advanced audit policy settings can cause unexpected results in audit reporting. - - If you use **Advanced Audit Policy Configuration** settings or logon scripts to apply advanced audit policies, be sure to enable the **Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings** policy setting under **Local Policies\\Security Options**. This configuration will prevent conflicts between similar settings by forcing basic security auditing to be ignored.