From eddedd0b46f765ae93ec36ff17a3269b28483dd3 Mon Sep 17 00:00:00 2001 From: David Paulson Date: Tue, 30 Jan 2024 14:29:26 -0600 Subject: [PATCH] Updated wording when EP is not configured --- ...nvoke-AnalyzerSecurityExtendedProtectionConfigState.ps1 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Diagnostics/HealthChecker/Analyzer/Security/Invoke-AnalyzerSecurityExtendedProtectionConfigState.ps1 b/Diagnostics/HealthChecker/Analyzer/Security/Invoke-AnalyzerSecurityExtendedProtectionConfigState.ps1 index b4f70b6d35..5b3d5bfe99 100644 --- a/Diagnostics/HealthChecker/Analyzer/Security/Invoke-AnalyzerSecurityExtendedProtectionConfigState.ps1 +++ b/Diagnostics/HealthChecker/Analyzer/Security/Invoke-AnalyzerSecurityExtendedProtectionConfigState.ps1 @@ -47,10 +47,13 @@ function Invoke-AnalyzerSecurityExtendedProtectionConfigState { # This combination means that EP is not configured and the Exchange build doesn't support it. # Recommended action: Upgrade to a supported build (Aug 2022 SU+) and enable EP afterwards. $epDetails = "Your Exchange server is at risk. Install the latest SU and enable Extended Protection" - } else { + } elseif ($extendedProtection.ExtendedProtectionConfigured) { # This means that EP is supported but not configured for at least one vDir. # Recommended action: Enable EP for each vDir on the system by using the script provided by us. - $epDetails += "Extended Protection isn't configured as expected" + $epDetails = "Extended Protection isn't configured as expected" + } else { + # No Extended Protection is configured, provide a slightly different wording to avoid confusion of possible misconfigured EP. + $epDetails = "Extended Protection is not configured" } $epCveParams = $baseParams + @{