Today we are announcing the availability of Cumulative Updates (CUs) for Exchange Server 2016 and Exchange Server 2019. These CUs include fixes for customer reported issues along with all previously ...
Updated Apr 21, 2022
Version 9.0
Blog Post
I can confirm with BTW97 for Exchange 2016 CU23 that the DAG Set-DatabaseAvailabilityGroupNetwork cmdlets are still broken - shockingly this is something I've been working on for months, to no avail obviously, in a side bar article:
https://docs.microsoft.com/en-us/answers/questions/720167/is-anybody-familiar-with-the-error-34a-server-side.html
This is quite frustrating because we ordered several storage arrays months ago and I cannot put them into production because I cannot configure the our DAG to disable replication and ignore the iSCSI networks in the DAG. These are non-routable networks, yet Exchange wants to try to use them as such. Its turned my storage into $500k paperweights.
The_Exchange_Team Bhalchandra_Atre-MSFT - while I recognize the manual adjustments of DAG networks is probably generally considered a rarity, they are extremely fundamental to setting up a correct configuration from Exchange's systematic perspective. Please expedite a fix to these cmdlets. I'd gladly take an out-of-band update to fix this. I can also confirm this has been going on for longer than was stated in the Mar SU claim of it being caused by January 2022's SU...
Per Microsoft https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2022-exchange-server-security-updates/bc-p/3254731:
"Modifying DAG network settings failing with error 0xe0434352 after January SUs are installed - fixed in the March SU but Set-DatabaseAvailabilityGroupNetwork continues failing"
If you go to my first link, you'll notice that I've tried troubleshooting by rolling back SU's to at least Oct 2021 KB5007012, before giving up on that rabbit hole. This has been broken for far too long. The fact that this bug has not been addressed already is kind of appalling.