EXCHANGE 2013 CU17 AND EXCHANGE 2016 CU6

On June 27, 2017 has released its quarterly updates for Exchange 2013 and Exchange 2016. The current version is now at Exchange 2013 CU17 (15.0.1320.4) and (15.1.1034.26) . But this time there are some interesting things I’d like to point out.

A couple of days before the release of CU6 (15.1.1034.26)
Microsoft blogged about Sent Items Behavior Control and Original Folder Item Recovery. With the Sent Items Behavior Control, a message that’s sent using the Send As or Send on behalf of permission is not only stored in the mailbox of the user that actually sent the message, but a copy is also stored in the delegator mailbox sent items. This was already possible for shared mailboxes, but now it’s also possible for regular mailboxes (like manager/assistant scenarios).

The Original Item Recovery feature is I guess on of the most requested features. In the past (before Exchange 2010) when items were restored after they were deleted, they were restored to their original location. With the Dumpster 2.0 that was introduced with this was no longer possible, and items were restored to the deleted items folder. In this case the items had to be moved manually to their original location. With the introduction of the Original Item Recovery the restore of deleted items again takes place in the original folder.

Unfortunately, both Sent Items Behavior Control and Original Item Recovery are only available in CU6 (and NOT in Exchange 2013 CU17).

When it comes to security TLS 1.2 is a hot topic. Microsoft is aware of this and working hard towards an Exchange environment that only uses TLS 1.2 (so that TLS 1.1 and TLS 1.0 can be disabled). We are not yet at that stage. does have improved support for TLS 1.2, but Microsoft is not encouraging customers to move to a TLS 1.2 environment only.

.NET Framework and Exchange continues to be a difficult scenario. This is understandable, Exchange is just a consumer of and .NET so the Exchange Product Group does not have much influence on the .NET (and Windows) Product Group.

does NOT support.NET Framework 4.7 at this moment, and you should NOT install .NET Framework on a running Exchange 2016. Not before and not after the installation of CU6. This is also true for CU17. More information regarding .NET Framework and Exchange server can be found here: https://blogs.technet.microsoft.com/exchange/2017/06/13/net-framework-4-7-and-exchange-server/.

The .NET Framework 4.6.2 is supported by CU3 and higher and and higher. For a complete overview of which scenarios are supported, navigate to the Exchange Supportability Matrix on https://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx.

KB articles that describe the fixes, features and information in each release are available as follows:

Version

Build

KB Article

Download

UMLP

Schema Changes

15.1.1034.26

KB4012108

Download

UMLP

Yes

15.0.1320.4

KB4012114

Download

UMLP

No

Source: jaapwesselius

Translate »
%d bloggers like this: