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

Friday, February 28, 2014

Namespace planning in Exchange 2013

I really like the changes they made in Exchange 2013 to simplify namespace planning.  It's especially useful for site failovers when DAG's are used.  Check out part 1 of the series:

http://blogs.technet.com/b/exchange/archive/2014/02/28/namespace-planning-in-exchange-2013.aspx

Tuesday, February 12, 2013

CAUTION:  Microsoft released SP3 for Exchange 2010 and it has the same 'bug' that SP2 had.  If you
attempt to install the SP with an execution policy defined, the installation will fail and your server will be inoperable.  The only recourse is a /m:recoverserver.  Why they allow the install to run instead of just checking for this condition is crazy!

http://support.microsoft.com/kb/2810617/en-us?sd=rss&spid=13965

Friday, February 08, 2013

Another iOS-Activesync bug has been found that causes excessive log generation caused
by iOS 6.1 devices.  Apple really needs to get their act together on this as it's been a recurring
problem.

http://www.sharepointpromag.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/apple-ios-61-upgrade-excessive-transaction-log-growth-145223