If the emails remain on the Exchange server and cannot be forwarded to the smarthost for sending, it may be because the certificate bound to the corresponding connector no longer exists or has been expired. Of course, it is also
Just recently I came across an interesting support case which involved an Exchange 2010 Offline Address Book (OAB) and Outlook 2010 clients trying to download it. The affected users received an error stating: Error 0x80190194 – The operation failed. Problem
Another Exchange 2016 migration, another error while trying to migrate custom Receiver Connectors from Exchange 2010 to 2016 … an analysis.
While migrating from Microsoft Exchange 2010 to Exchange 2016 we came upon a typical issue in which Outlook keeps giving the message: “The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook“. This means that users
As part of my Security Best Practices regarding Microsoft Exchange and Microsoft IIS I always implement a couple of configuration settings to harden the underlying IIS, e.g. disabling the “X-AspNet-Version” header, disabling deprecated and/or unsecure protocols, disabling deprecated and/or unsecure
Just recently I ran into an error during initial setup of Exchange 2016 on a newly installed Windows Server 2012 R2 stating: “Service ‘MpsSvc’ failed to reach status ‘Running’ on this server“. Further down the troubleshooting road I found out that
As I did quite some Exchange migrations (including single as well as multi tenancy environments) I was always wondering whether there are any additional post migration tasks that need to be addressed before you start removing your legacy Exchange server(s)
After logging into Exchange 2016’s ECP you receive an HTTP Error 500 (same goes with OWA): Searching the internet ends up with several possible solutions to this issue, ranging from missing System Attendant Mailboxes, to bogus ADSI settings regarding the
Exchange 2016 – Poor Outlook 2016 Performance – Troubleshooting – Server-side or Client-Side? Just recently I came across a newly installed Exchange 2016 environment and had to analyze a “poor performance issue”. I started my investigation by asking … Google! Of
After migrating to Exchange 2013 and/or 2016, and still having a couple of Microsoft Outlook 2007 installations left, the following issue started popping up: as soon as users launch their Outlook 2007 (while already being migrated to Exchange 2013/2016), they were