Email Stuck in Exchange On-premises Transport Queues

Wanted to come back here and udpate with my experience on our Exchange 2019 Server Core servers running CU11.

We orginally disabled the Anti-Malware service using the "Disable-AntimalwareScanning.ps1 -ForceRestart" option on 12/31/21.

Deciding to deffer this fix until our monthly maintence window, I proceeded with doing the following on our (2) Exchange servers hosting passive copies of our mailbox databases BEFORE attempting to run the automated script in this post:

• Enable-AntimalwareScanning.ps1

I was then presented with several "Checking for Engine Update" messages over the course of 20-30min.

Once the update was completed, I restarted the MSExchangeTransport service as instructed. 

When the service finished restarting, I attempted to run the automated script in this post: 

• Reset-ScanEngineVersion.ps1

I was then informed that our scanning engine was up to date and that the script was not needed.

Performing a "Add-PSSnapin Microsoft.Forefront.Filtering.Management.Powershell" followed by a "Get-EngineUpdateInformation" provided me with the following results:

Engine : Microsoft
LastChecked : 01/13/2022 09:30:31 AM -08:00
LastUpdated : 01/13/2022 06:36:47 AM -08:00
EngineVersion : 1.1.18800.4
SignatureVersion : 1.355.1844.0
SignatureDateTime : 01/13/2022 12:23:00 AM -08:00
UpdateVersion : 2112330084
UpdateStatus : UpdateAttemptNoUpdate

At this moment, since out version is "2112330084" which is above the documented "2112330001", we assume there is nothing more that we need to do. There are also no FIPS error messages within the Application event logs.

Just thought I would post this as I found it unusual that the automated script was not needed for us to fix this issue, but just a matter of re-enabling the Anti-Malware Scanning and restarting the MSExchangeTransport service.