Microsoft has released Hotfix Updates (HUs) that address issues in earlier updates for:
Exchange Server 2019
Exchange Server 2016
HUs are available for the following specific versions of Ex...
Updated Jun 04, 2025
Version 3.0
Blog Post
Can you guys comment on the functionality of a 2 node dag + witness server with exchange 2019 cu15 and server 2025. If i shut down 1 server the second server immediately fails. The issue seems to stem from the windows clustering side of things, get-cluster and get-clustergroup both return: remote server has been paused or is in the process of being started.
The remote server has been paused or is in the process of being started
this never clears or changes.
If i manually move the cluster off the node i intend to shut down everything works, but i have to do that proactively, i cant find a way to recover the second node with the other off. Turning the other server back on does fix the issue. I am not alone in this, per this forum: https://learn.microsoft.com/en-us/answers/questions/2247840/dag-failover-not-working-with-2-node-exchange-serv
ill be honest though i am not convinced its specifically server 2025, i had this problem with server 2022 and attributed it to many in-place upgrades over the years. I just rebuilt this in a test environment from scratch and have the same issue immediately. I read the cluster logs before I wiped the original servers and unfortunately, i dont have the exact error, but it was basically saying, cant hit the other node, we have priority according to the quorum fileserver, but we arent going to do anything.
Bhalchandra_Atre-MSFTMicrosoft
This issue is fixed in August 2025 Windows Update
I'm currently trying to deploy a two-node DAG with Exchange Server SE + Windows Server 2025 Core. Servers are patched with updated July 2025 CU (KB5063666).
I can create the DAG with New-DatabaseAvailabilityGroup cmdlet. But as soon as I try to add a member inside the DAG with the Add-DatabaseAvailabilityGroupServer, I get the following error (after 15 minutes of processing) :
A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "CreateCluster() failed with 0x5b4. Error: This operation returned because the timeout period expired".I've looked to all evidences (Exchange Trusted Subsystem is a member of the witness' server local admin groups, firewalls ports opened, trying to pre-stage the CNO object....), but whatever I try, I always end with the above error.
Do you know if this issue can be related with the fix you mention?
BTW, are you mentioning a Windows Server update (like a CU) or an Exchange hotfix?
- Bhalchandra_Atre-MSFT
Can you please run exchange health checker and fix any issues reported there?
nothing is reported, i really think this isnt working right for anyone in a 2 node dag.
- Bhalchandra_Atre-MSFT
Can you try this and check if it works?
- Move the cluster group to working node before shutting the node
