Tuesday, June 13, 2017

.NET 4.7 will be released soon on Windows Update so if you have an Exchange server that pulls its updates down thru WU, be sure to block that action now since its not supported yet:


Finally, a reason to move to Exchange 2016:  Original Folder Item Recovery


It would be nice if they back ported this to Exchange 2013 but that probably won't happen. Hopefully there will be a way to do this in bulk (preferably from EMS) so admins can do this for users.

Thursday, May 18, 2017

DO NOT install .NET 4.7 on Exchange.  Place registry block in place once available.


Tuesday, May 31, 2016

The Exchange team just published an excellent article on client troubleshooting that is worth reviewing and keeping as a checklist:


Tuesday, February 16, 2016

One of my favorite admin tools finally came out for 2013/2016 - Exmon.  Great for identifying a specific users or set of users who are killing your server performance.


Thursday, February 11, 2016

For those running Exchange 2013, please make an effort to block automatic installation of .NET 4.6.1 to any of your servers.  There are known issues with this release and Exchange.  Tony talks more about it here:


Tuesday, September 15, 2015

Microsoft just released both CU10 for Exchange 2013 and RU11 for Exchange 2010.  These are both the minimum levels necessary to support a coexistence deployment with Exchange 2016.

I would hold off a few weeks for any fallout before installing these in a production environment.