Microsoft has released its quarterly updates for Exchange:
- Exchange 2016 CU17.
- Exchange 2013 CU18.
It has been quiet around these updates, and they do not bring a whole lot of features.
Important to note is that the minimum Forest Functional Level (FFL) has been raised to Windows Server 2008 R2. Personally I think this is an indication that more exciting stuff is along the way, especially around Exchange 2016 (my personal expectation, don’t shoot the messenger :-))
There are schema changes in Exchange 2016 CU17, so when installing this update you have to execute the following commands:
Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
Setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms
When it comes to the .NET Framework, Microsoft is working on a new .NET Framework release (version 4.7.1). The upcoming quarterly update of December 2018 will support this version of the .NET Framework.
More information (well, not a lot more) can be found here: https://blogs.technet.microsoft.com/exchange/2017/09/19/released-september-2017-quarterly-exchange-updates/
Some customers have an Active Directory domain in their DMZ (for management purposes) and the Exchange 2013 Edge Transport server can be a member of this domain as well.
Unfortunately starting with Exchange 2013 CU5 the Edge Transport server won’t install anymore when the server is a member of such a domain. Setup crashes with the following error message:
“Active Directory failed on localhost. This error is not retriable. Additional information: the parameter is incorrect.” And “Active Directory response: 00000057: LdapErr: DSID-0C090D8A, comment: Error in attribute conversion operation, data 0, v2580 —> System.DirectoryServices.Protocols.DirectoryOperationException: The requested attribute does not exist.”
At this moment (up to Exchange 2013 CU7) there’s no other workaround that to remove the Edge Transport server from the domain, install the Edge Transport server role (make sure you got the FQDN of the server correct!) and after installing rejoin the Active Directory domain. This works fine.
I noticed however that upgrading an Exchange 2013 CU6 Edge Transport server that’s domain joined to CU7 doesn’t hit this issue, there was no need to remove it from the domain before upgrading.
On Tuesday December 9, 2014 Microsoft released Exchange Server 2013 Cumulative Update 7 and the UM Language Packs for Cumulative Update 7, 105 days after the release of the previous CU6 update. This release is a little overdue because of a last minute issue that was found moments before the original release date of CU7. As long as it improves the quality of the release this shouldn’t be a problem though.
CU7 contains fixes for issues reported by customers, including the Russian Time Zone issue and fixes for issues identified in MS14-075. Updates for MS14-075 are also available for Exchange Server 2013 Service Pack 1 and Exchange Server 2013 Cumulative Update 6. Because of the Microsoft (N-1) support policy this hotfix won’t be available for CU5.
Continue reading Exchange Server 2013 CU7