Microsoft recently released Cumulative Update 6 for Exchange Server 2013, and it's important to know what changes come with it before installing. Unlike previous updates, Exchange 2013 CU6 doesn't bring any major features or changes. Instead, this update is more of a routine update; something that definitely fits the model of these (almost) quarterly updates. You can see this by reviewing the list of fixes included in this update. Many...
admins should be pleased to see the fix for the failing Hybrid Configuration Wizard. Even though an interim update was made available already, I know this problem affected quite a few customers.
Next to the regular fixes, I'm sure many people will be thrilled to hear this Cumulative Update closes the gap in public folder performance and scalability, which was recently introduced with an Exchange Online update. Similar to the update in Office 365, CU6 enables you to install 100,000 public folders, which increased 10X over previous versions.
While this might not be enough for some of the large customers who intensively use public folders, Microsoft promised it will continue improving the overall performance and scalability in future updates. Read through Microsoft's announcement here for more details.
What's new in Exchange 2007 and Exchange 2010
The latest update to Exchange 2013 wasn't the only update Microsoft released that day. The company also included updates for Exchange 2010 and Exchange 2007.
The last update for Exchange 2007 was released in February of this year. Since then, not much has changed. This update doesn't add much to the equation, either. According to the official KB article, Update Rollup 14 for Exchange 2007 only contains one single change, and that addresses Daylight Savings Time changes introduced this year.
Along with the same Daylight Savings Time update, Update Rollup 7 for Exchange 2010 is a bit heavier on the fixes. But there doesn't appear to be one fix that stands out from the rest. The full list of fixes can be viewed here.
Even though I just finished installing the update without any problems, I urge you to properly test the update before deploying it in production -- it wouldn't be the first time an Exchange Server update caused trouble.
About the author:
Michael Van Horenbeeck is a technology consultant, Microsoft Certified Trainer and Exchange MVP from Belgium, mainly working with Exchange Server, Office 365, Active Directory and a bit of Lync. He has been active in the industry for 12 years and is a frequent blogger, a member of the Belgian Unified Communications User Group Pro-Exchange and a regular contributor to The UC Architects podcast.
Dig deeper on Microsoft Exchange Server 2013