Note: this post is getting frequent updates; please keep checking back. Last update: 3/19/2021
Microsoft has released a set of out of band security updates for vulnerabilities for the following ver...
Updated Mar 19, 2021
Version 44.0
Blog Post
I had to update 6 Exchange servers today, from 2010 to 2019. Here's my feedback (also based on comments I've found here)
@EddieRowe - from an elevated Powershell, run "C:\Program Files\MicrosoftExchange ServerV14\Bin\UpdateCas.ps1" (or whatever drive letter Exchange is installed on), then restart IIS (IISReset). I also had to set the MS Exchange services back to Auto or manual on the Exchange 2010 deployment I manage. I went by this doc - https://docs.microsoft.com/en-us/previous-versions/office/exchange-server-2010/ee423542(v=exchg.141)?redirectedfrom=MSDN
SteveInReno - I had this issue on the first 2013 Exchange server I updated today as a result of not running the patch from an elevated command prompt. To Fix it, I ran C:\Program Files\Microsoft\Exchange Server\V15\Bin\UpdateCas.ps1 (this fixed OWA), and then had to correct the BinSearchFolders in IIS Application settings (to fix ECP):
1. Open IIS Manager. Expand Sites > Exchange Back End.
2. Click ecp. Open Application Settings in /ecp Home.
3. Please check whether the value for “BinSearchFolders” is changed to not absolute paths. If so, please change it to (adjust for the correct path/drive to Exchange Server):
C:\Program Files\Microsoft\Exchange Server\V15\bin;C:\Program Files\Microsoft\Exchange Server\V15\bin\CmdletExtensionAgents;C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\bin
4. Run IISReset