Exchange 2016 – EAC (ECP) Works But OWA Does Not
KB ID 0001225 Problem During an Exchange 2010 to Exchange 2016 Migration, I was busy migrating mailboxes into the 2016 mailbox database. I noticed that while the Exchange Admin Center worked fine (I was doing the migration from there!) Outlook Web Access did not. I got a ‘Something Went Wrong” error. 🙁 Something Went Wrong We Cant get the information right now. Please try again later. More Details Refresh the page...
Exchange 2016 (& 2013) Enable Circular Logging
KB ID 0001224 Problem Let’s be clear about this, the correct way to flush/clear the Exchange logs is to perform a backup of the mailbox database in question, with an ‘Exchange aware’ piece of backup software. This will clear down the logs properly. Why Do We Need Logs? Well I’m glad you asked, if there’s a problem, and we lose the database, we can ‘play’ the log files back into the database to...
The name of the security certificate is invalid or does not match the name of the site
KB ID 0000036 Problem Seen in Outlook when connecting to a mailbox on an Exchange Server, its caused by using a self signed certificate OR a purchased certificate, where the internal and external names are different. The name of the security certificate is invalid or does not match the name of the site. Solution Before proceeding if you have an A or CNAME record in your DNS for autodiscover then DELETE it and setup an SRV record!...
Exchange 2016 Install Error ‘Skipping creating Discovery Arbitration Mailbox because of insufficient permission”
KB ID 0001221 Problem Note: Can also be seen on Exchange 2013. While installing a new Exchange 2016 Server into a clients Exchange 2010 infrastructure last week, the setup failed with the following error. A cutdown version of the error; Write-ExchangeSetupLog -Info (“Cannot find E-discovery arbitration mailbox with name=$name.”); } } else { write-exchangesetuplog -info “Skipping creating Discovery Arbitration...
Migrate Exchange 2010 to Exchange 2016 or 2013
Part 2 Migrate Public Folders Exchange 2010 to Exchange 2013 / 2016 KB ID 0000789 Problem Continued from Migration From Exchange 2010 to Exchange 2016 / 2013 Part 1 Solution Exchange 2016 / 2013 Migration Step 7 “Migrate Public Folders” Note: This article uses the newer ‘Batch Migration’ method. Make sure your exchange server is patched and up to date or the process will not work. Minimum Patch Levels Source:...