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.

Friday, April 25, 2014

Ran in to an interesting issue/bug when retiring my last Exchange 2003 box.  Followed all the steps and everything went normal in retiring the last server.  Then proceeded to reboot one of my Exchange 2010 servers and started to see a few of these errors in the app log:

The store driver couldn't deliver the public folder replication message "Folder Content (servername@domain.com)" because the following error occurred: The Active Directory user wasn't found..

Found a similar issue on the Windows Server Essentials and Small business technet blog although the error was slightly different:

http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx

In any case, removing the empty server folder resolved my specific error as well.  Just throwing that out there in case somebody else sees the issue.

Wednesday, March 05, 2014

Part 2 of the series goes in to depth on different load balancing options with Exchange 2013:

http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx


I really like the changes being made in Exchange to simplify management, DAG configuration and
monitoring.  Keep it simple for sure.

Tuesday, March 04, 2014

Another nice article on some new features with Exchange 2013-sp1/Windows Server 2012 R2.  Creating
a DAG with no AAP sounds interesting and certainly makes things simpler.

http://blogs.technet.com/b/scottschnoll/archive/2014/02/25/database-availability-groups-and-windows-server-2012-r2.aspx