Microsoft has released Security Updates (SUs) for vulnerabilities found in:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
SUs are available in a self-extracting auto-elev...
Updated Mar 03, 2023
Version 13.0
Blog Post
Could you please explain the Note / Statement
"Note: Build availability issues have been resolved. If your server downloaded the February SU via Windows/ Microsoft update before February 15 8 AM Pacific time, you might see the February update be offered again. Installing the updated package will bring your server forward to current February builds (verify using Health Checker after installation). The Download Center .exe update packages were (and still are) correct."
We installed the Download Center .exe update packages in our test environments.
Though we did not apply the Registry Workaround, we do not have any issues with EWS.
Is the Download Center .exe update package already OK, meaning that there is no problem with EWS and no workaround is needed in this package?
Or do we need the Workaround with the Download Center .exe update package as well?
In this case, will there be a "final fix" available and when?