Can you believe the end of the first quarter of 2017 has come and gone. Where in the world does the time go? Wherever it does go, it’s taking Exchange 2007 with it, as with this release of Exchange Server 2007 Service Pack 3 Update Rollup 23 (dang! 23?) we are a month away from the end of all support for Exchange 2007. Yes, you, the guy in the corner who still hasn’t made up his mind what to do with his aging email system. You’re weeks away from end of life! Get busy! For the rest of you, let’s take a look at what the Exchange Team has put out for our Q1 updates.
Exchange 2016’s latest update is Cumulative Update 5, which is kind of a milestone to some since that means both that it’s been a year since 2016 came out, and in the old way of reckoning things, you might have called this SP1. First up, with this CU comes a requirement for .Net Framework 4.6.2. If you’re not on CU4 already, apply CU4, then apply .Net Framework 4.6.2, then finally you can apply CU5, which you can download from https://www.microsoft.com/en-us/download/details.aspx?id=54930. This CU contains the latest changes to Daylight Saving Time, and fixes the following issues with Exchange 2016.
- KB 4015665 SyncDelivery logging folders and files are created in wrong location in Exchange Server 2016
- KB 4015664 A category name that has different case-sensitivity than an existing name is not created in Exchange Server 2016
- KB 4015663 “The message content has become corrupted” exception when email contains a UUE-encoded attachment in Exchange Server 2016
- KB 4015662 Deleted inline picture is displayed as attachment after you switch the message to plain text in Exchange Server 2016
- KB 4015213 Email is still sent to Inbox when the sender is deleted from the Trusted Contacts list in Exchange Server 2016
- KB 4013606 Search fails on Exchange Server 2016 or Exchange Server 2013
- KB 4012994 PostalAddressIndex element isn’t returning the correct value in Exchange Server 2016
But what it doesn’t fix includes a few issues we’ll need to wait on until CU6 this summer. These include:
- When attempting to enable Birthday Calendars in Outlook for the Web, an error occurs and Birthday Calendars are not enabled.
- When failing over a public folder mailbox to a different server, public folder hierarchy replication may stop until the Microsoft Exchange Service Host is recycled on the new target server.
Exchange 2013 Cumulative Update 16 brings a number of fixes to 2013, as well as a significant change. Like Exchange 2016, the .Net Framework 4.6.2 is now required for Exchange 2013 and should be applied before applying this CU. If you are not current on your CUs already, apply CU15, upgrade .Net to 4.6.2, then apply this CU. This CU includes Daylight Saving Time updates, and one fix;
You can download CU 16 from https://www.microsoft.com/en-us/download/details.aspx?id=54931.
Exchange 2010 Service Pack 3 gets Update Rollup 17 this time around. Downloadable from https://www.microsoft.com/en-us/download/details.aspx?id=54934, this update includes the latest Daylight Saving Time changes, as well as fixes for four issues;
- KB 4014076 Migration ends and errors reported when you on-board or off-board a mailbox through Exchange Online in an Exchange Server 2010 hybrid environment
- KB 4014075 UNC path does not open in OWA when the path contains non-ASCII characters in an Exchange Server 2010 environment
- KB 4013917 You cannot search in a shared mailbox through OWA in an Exchange Server 2010 Service Pack 3 (Update Rollup 15 or 16) environment
- KB 4012911 Culture element is added in the wrong order when you use the ResolveNames operation in EWS in Exchange Server 2010
As usual, if you applied an interim update to address one of these issues, you will want to uninstall that before applying this update rollup.
One more time…Exchange 2007 goes end of life next month, on May 11. If you’re still on 2007, you might see some security patches next month, but then that is it. If you are not already well on your way to getting your users off 2007, I predict one of two things in your future. Either a cutover to a new platform, or a catastrophic failure. It’s not that 2007 has a half-life or an expiration date and will start to smell funky in a few more weeks, but more that either a new vulnerability will be found, or a hardware failure will occur, or something else will go wrong and you won’t have anywhere to turn. Check out our post Time to start thinking of the Exchange 2007 EOL and get busy upgrading! But since you do have to keep care of your existing 2007 servers, at least for another month or so, you can download Update Rollup 23 from http://www.microsoft.com/downloads/details.aspx?FamilyID=0d13d7c1-4ab1-4028-99e5-39bfeafa368b. This update, the last ever CU for Exchange 2007, doesn’t add much other than the latest updates for Daylight Saving Time. But that’s something to consider itself. If you are planning on staying with Exchange 2007 for some reason, keep in mind that different countries change their DST start and end dates all the time. There’s a chance that a future change will render all of your users’ calendars an hour off one way or another. I wouldn’t want to field those phone calls!
So as with every quarter’s RU/CUs, test them in your lab environment and then get them deployed to production in a timely fashion. Apply from the outside in, starting with Edge, then Mailbox, Hub Transport, and finally CAS, with UM falling in there wherever you want, and of course 2016 admins are laughing because they just have Exchange servers without all those funny roles going on. Plan on reboots all around though, so 2016 admins shouldn’t get too cocky!
In the next CU cycle, of course we won’t see jack for Exchange 2007 (okay, I’ll stop beating the dead horse for now) but we will see improvements in TLS capabilities including support for TLS 1.2 which should make everyone happy.