Microsoft has released security updates for vulnerabilities found in:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
These updates are available for the following specific...
Updated May 04, 2021
Version 8.0
Blog Post
Nino_Bilic
Microsoft
MicrosoftGregS410 - we can now confirm that the change that broke several 3rd party products as well as some home-grown code calling .AddScript() is not going to be rolled back and .AddCommand() is a way forward. I have just added the Known Issues section to the blog post to reflect this (a KB article will follow next week)
jsab5 - uninstallation should be simple via the add/remove; why would you?
ddovnar - At this time, the $ issue is still under investigation; we know what the work around is (rename accounts) but we do realize it is a workaround. It is unclear where this will go, sorry to be vague but that is how it is right now.
Corbett_Enders - we definitely recommend that you update all of your servers; you have made some assumptions but they might not be correct. It is understandable that it is really bad that we do not have a full answer on the $ situation at this time (still under investigation) but protecting the environment should be the primary concern.