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.

http://blogs.technet.com/b/exchange/archive/2016/02/16/exchange-2013-and-2016-exmon-tool-is-now-available.aspx

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:

http://windowsitpro.com/blog/exchange-says-no-net-framework-461


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.

http://blogs.technet.com/b/exchange/archive/2015/09/15/released-september-2015-quarterly-exchange-updates.aspx

Thursday, July 16, 2015

I recently was using Exmon to trace a troublesome user and it crashed during the trace.  When this happens a lot of the time the Exchange trace will be left running so you are unable to launch Exmon again.  If you google the error "unknown starttrace error (183)" you get many hits that tell you to use logman to query and then stop the trace.  The problem is they all use syntax that seems to no longer work:

Old syntax:  logman stop "exchange event trace" -ets

Trying to use this command only triggers an error:

H:\>logman stop "Exchange Event Trace" -ets
Argument 'Event' is unknown.
Argument 'Trace"' is unknown.

Error:
The parameter is incorrect.

Using the following syntax correctly stops the Exchange trace:

logman stop -name "exchange event trace" -ets

Not sure when this changed (maybe a service pack) but this was the only way to successfully
stop the trace on a Windows Server 2008 R2 box.  YMMV.

Friday, May 01, 2015

It's interesting Microsoft posted they no longer support running on repaired databases when it was common knowledge for years that you shouldn't do this.  Repair the database, move all the mailboxes off and then delete/recreate the database.  I'm guessing they got burned by this one too many times allowing customers to run on repaired databases and decided to make it official.

http://blogs.technet.com/b/exchange/archive/2015/05/01/new-support-policy-for-repaired-exchange-databases.aspx


Friday, January 09, 2015

Microsoft just announced support for using an Azure VM as a DAG Witness server in an Exchange 2013 stretched cluster.  This will be a nice option to have to allow automatic failover when you don't have a 3rd physical site to use.

http://blogs.technet.com/b/exchange/archive/2015/01/09/using-an-azure-vm-as-a-dag-witness-server.aspx


Friday, December 12, 2014

Been a long time since posting but thought I would throw this out there...... DO NOT install
RU8 for Exchange 2010 SP3.  MS just pulled it for a pretty big bug which caused Outlook clients
to not be able to connect with the server after the update.  Not sure how they missed this one in
testing on O365 but MS has been on a real downward spiral with Exchange updates lately.  I'm
holding off on CU7 for Exchange 2013 as well just in case.  YMMV.