Microsoft has released Security Updates (SUs) for vulnerabilities found in:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
SUs are available in a self-extracting auto-elev...
Updated Sep 18, 2023
Version 9.0
Blog Post
Do we have to run these commands in an elevated Exchange PowerShell, or in a 'normal' one..?
New-SettingOverride -Name „EnableSigningVerification“ -Component Data -Section EnableSerializationDataSigning -Parameters @(„Enabled=true“) -Reason „Enabling Signing Verification“
Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh
Restart-Service -Name W3SVC, WAS -Force
On my test-server I've run these command in an elevated shell, everything works, BUT I noticed that if I use the command "Get-ExchangeCertificate" in a 'normal' Exchange shell after applying these settings, the command does generate an EMPTY output like...
Thumbprint Services Subject
———- ——– ——-
BUT if I use "Get-ExchangeCertificate" in an elevated shell it does generate the correct output showing all my certificates. Get-ExchangeCertificate have always worked before in an normal shell!
Is this intended behavior, or a bug? Was it caused by running these three commands in an elevated shell? Should I've better used these commands in a 'normal' (not elevated shell) to secure my server? What went wrong?