Exchange 2016:- Manage existing DAG Seed operation
In Exchange 2016, if you work a lot in the Exchange Management Shell (EMS) like I do and you busy with a seed operation and you by accident close the Management Shell you may...
Author: edward
Exchange 2016:- Symantec IPS issues
Symantec on a Windows Server just like ESET works great. When you throw Exchange 2016 or Exchange 2019 into the mix, things get more complicated with both products. If you are not aware, when...
Exchange 2010:- Journal email stuck in Submission queue
In my Exchange 2010 lab, I came across a handful of messages in the submission queue. All of them were for accepted and declined meeting invites and nothing else and all of them for...
Exchange 2016:- Updating from old CU’s to the latest one pointers
With the latest set of attacks on Exchange, many admins are scrambling to update their Exchange servers. If you coming from a CU that lower than CU13, you need to take note of the...
Exchange 2016:- Outlook OAB error 0x8004010F
The above error is a strange one. Upgrading to CU19 for Exchange 2016 in my lab went through without issues. In outlook the error below stated that the object could not be found: When...
Exchange 2013/2019 Coexistence Video series
I have started with a video series show casing how you can run Exchange 2013 and Exchange 2019 in coexistence. There are 18 parts to the video series. This blog will be updated as...
MacOS Big Sur:- OneDrive not syncing or delinking itself.
While this is not your regular Exchange or PowerShell blog post, I thought I would share some thought on OneDrive for Mac not working on MacOS Big Sur. In my own troubleshooting, here are...
Exchange 2016:- The SSL certificate contains a common name (cn) that does not match the hostname.
In Exchange 2016 or even later or earlier versions, you might have configured your virtual directories and have an error in it but did not notice the error. Here is a common error that...
Exchange 2016:- Change the server that the Exchange Management Shell (EMS) connects to.
When you open up the Exchange Management Shell (EMS), it should connect to the closest server. Sometimes you want to have it connect to a specific server to run scripts etc. If you right...
Exchange 2016:- The Server is busy and can’t respond to your request.
In Exchange 2016 OWA, you may have come across a similar window where it states that “Something went wrong” and if you expand more details you can view the Front and Backend servers. Here...
