We have addressed the issue causing messages to be stuck in transport queues of on-premises Exchange Server 2016 and Exchange Server 2019. The problem relates to a date check failure with the change ...
Updated Jan 11, 2022
Version 36.0
Blog Post
Hi Everyone,
I'm running a farm of 6 Exchange 2016 (4 DAG nodes and 2 dedicated transport nodes) in hybrid with Office 365 and centralized transport.
Exact cu is 20 -> Build 2242.4.
Although I did see 5300 and 1106 a couple of times(5-10 times) on each server but not after 4:00am 01.Jan.2022, my mail flow does not seem to be altered at all.
I don't have any email in queues and I did receive mails as normal since new year.
Right now I'm wondering if I still need to apply the fix as I don't seem to have a mail flow issue.
It might make sense to fix the Anti Malware engine. Currently shows:
PS C:\Windows\system32> Get-EngineUpdateInformation
Engine : Microsoft
LastChecked : 01/01/2022 02:33:19 AM +01:00
LastUpdated : 01/01/2022 01:57:08 AM +01:00
EngineVersion : 1.1.18800.4
SignatureVersion : 1.355.1209.0
SignatureDateTime : 12/31/2021 08:14:11 PM +01:00
UpdateVersion : 2201010001
UpdateStatus : UpdateAttemptNoUpdate
Has anyone had the same scenario as me? Is it still mandatory to apply the fix?
Thanks,
Seb