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
Microsoft,
First off thank you all for coming up with quick workarounds and a solution to this unfortunate issue. It has been a long year of emergency fixes/security patches for Exchange.
This brings up the question about the retirement of Exchange hybrid servers. We've heard for a very long time of a future replacement for Exchange hybrid so we don't have to maintain an on-premise Exchange server which is required for O365 support with Azure AD Connect. We are tired of patching these hybrid servers and we see customers retiring such servers even though they move to an "unsupported" state.
When will there be another supported way to manage Exchange attributes on-premise and a substitute to more easily allow systems/devices to relay off an internal email server?
It is long overdue Microsoft and hoping someone from the Exchange team can comment on the plans to simplify our IT lives so we don't have have to upgrade/patch Exchange hybrid servers every 2 to 6 months to stay in support and stay secure.
thank you,
Larry Heier