The Exchange Team announced Cumulative Update 9 earlier this month.
As always, test these updates in a lab first!
It doesn’t have to be anything elaborate. In fact, I used to do a lot of testing from a Windows 8.1 laptop where I had Hyper-V installed. My laptop ran 3 VMs–Exchange 2010, 2013 and a DC. Hyper-V comes included with Windows 8. Its comparable to VMware Workstation in functionality.
Enough about labs! What are these updates and where can I get them?
The updates are as follows:
Exchange Server 2013 Cumulative Update 9
UM Language Packs for Cumulative Update 9
Exchange Server 2010 SP3 Update Rollup 10
Exchange Server 2007 SP3 Update Rollup 17
So what’s new?
This update is a culmination of bug fixes and feature tweaks. Cumulative Update 9 also included changes to the behavior of saving Sent Items when using Shared Mailboxes; more info on that here.
Aside from that, no new features. It is pretty apparent that with Exchange 2016 looming on the horizon that all enhancements are being held for it.
Required for hybrid
Microsoft requires that anyone in a hybrid environment be up to date.
Schema Updates Needed
If upgrading from Cumulative Update 7/8 to Cumulative Update 9, then there are no schema changes. However, if migrating from an earlier update you will need to perform a schema update. Microsoft documents that update process here. For a quick reference on schema and build versions check here.
Any insight into Cumulative Update 10?
Based on sessions at Microsoft Ignite–and the preview for Exchange 2016 looming ever closer–it would be surprising if Cumulative Update 10 didn’t include official coexistence support.
Exchange 2007 & 2010
With Exchange 2010 in Extended Support, we only saw a handful of fixes for it. You can read more about Update Rollup 10 here.
In fact, the Exchange Team further announced.
Exchange 2007 only received one hotfix in Update Rollup 17.
Ready?
Would love to hear about your update experience. Did it go smoothly? Any hiccups?
What are your thoughts on Exchange 2010 now end of life? Drop a comment below.
Leave a Reply