THANKSSSSS I’ve been searching for a solution everywhere and all I could find is craps like reinstalling IIS and things like that. Just hit the dreaded OWA blank page issue after Exchange 2010 SP1 Update Rollup 5 . Then m-u-c-h longer researching any number of ‘it worked for me’ solutions, many of which involve uninstalling & reinstalling the Rollup.This one has done the job and I’m finally able to access my OWA site. When all along, we could have simply run the updatecas.ps1 script. I just finished an SBS 2003 to 2011 upgrade, which has been a nightmare.Emails going to users residing on our Exchange 2016 server were never delivered.They do show delivered on the Spam filter, but never hit the users mailbox.This update includes new fixes for the following server roles: Note: The above links may not be live at the time of this posting.
At present we are working through the process of modifying our installers to incorporate these two languages.
For those of you running Forefront, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup's installation process.
Without these steps, Exchange services for Information Store and Transport will not start back up.
New-Exchange Website.ps1 performs all the steps listed in the blog article in an automated fashion.
If the script detects that an OWA_SECONDARY folder already exists, it removes that existing configuration before configuring the new website.