Ensure 'Signature Warning' is set to 'Enabled: Always warn about invalid signatures'

So wird geprüft

Prüfmethode: Windows-Registrierung

$bad = @(); $bad += @(Get-ChildItem Registry::HKEY_USERS | Where-Object { $_.PSChildName -match '^S-1-5-21-\d+-\d+-\d+-\d+$' } | ForEach-Object { $v = (Get-ItemProperty -Path ('Registry::HKEY_USERS\' + $_.PSChildName + '\SOFTWARE\Policies\Microsoft\office\16.0\outlook\security') -Name 'warnaboutinvalid' -ErrorAction SilentlyContinue).'warnaboutinvalid'; if (-not ($null -ne $v -and @(1) -contains [int64]$v)) { $_.PSChildName + ':warnaboutinvalid=' + $v } }); if ($bad.Count -eq 0) { 'compliant' } else { 'non-compliant: ' + ($bad -join ', ') }

Erwartete Ausgabe

compliant

So wird behoben

Behebungsmethode: Anleitung oder Infrastruktur-Patch

To establish the recommended state via configuration profiles, set the following Settings Catalog path to Enabled: Always warn about invalid signatures: Microsoft Outlook 2016\Security\Security Form Settings\Outlook Security Mode > Signature Warning Important: For this setting to apply, the Outlook Security Mode setting must be enabled in Microsoft Outlook 2016\Security\Security Form Settings with Use Outlook Security Group Policy selected, as set in this benchmark.

Diesen Host prüfen

Führen Sie dies auf einem Rechner aus, den Sie prüfen dürfen. Der Scan ist schreibgeschützt.

tmaegis scan --target intune-office