On September 15 Microsoft released two updates for their on-premises Exchange servers:
- Exchange 2019 Cumulative Update 7
- Exchange 2016 Cumulative Update 18
Note. This is the second-last Cumulative Update for Exchange 2016! As Microsoft has announced earlier, Exchange 2016 will be out of mainstream support this October. The last Cumulative Update is expected in December 2020.
Both updates contain security and nonsecurity updates, the recently released security update for Exchange 2016 and Exchange 2019 that addresses the CVE-2020-16875 vulnerability is also included in these CU’s.
Both updates also contain the latest Daylight Saving Time (DST) Updates.
In earlier posts it was mentioned that no changes in Active Directory are introduced, so there was no need to run Setup with the /PrepareAD and /PrepareDomain option. However, when you check the Microsoft documentation you’ll notice that AD and Domain versions are increased, so this time there is a need to run /PrepareAD and /PrepareDomain. If you run the /PrepareAD, make sure you have sufficient permission to execute this command (member of the Enterprise Admins Security Group).
The same is true when upgrading for Exchange 2016. you must run Setup.exe /PrepareSchema, Setup.exe /PrepareAD or Setup.exe /PrepareDomain.
Autodiscover EventID 1 can occur after installing Exchange 2019 CU3 or after installing Exchange 2016 CU14. I’ve blogged about this before on EventID 1 MSExchange Autodiscover. I am not sure if this still is the case 😉.
Updated on October 30, 2020
Most likely you’ve seen this information before, because of my vacation in Dallas and New Orleans I’m a bit behind with blogging 😊
But on October 16, 2018 Microsoft has released Cumulative Update 11 (CU11) for Exchange 2016, this is a little later than expected to align the release of Exchange 2016 Cumulative Updates with the upcoming release of Exchange 2019. . There’s only a release for Exchange 2016, there won’t be any new CU’s for Exchange 2013 since Exchange 2013 is already in extended support. There will be security updates for Exchange 2013 though.
Exchange server and .NET Framework is not a happy marriage and it continues to be a struggle, or at least it looks that way. Exchange 2016 CU11 now supports .NET Framework 4.7.2. This version of .NET Framework is not mandatory, installation of .NET Framework 4.7.2 can be before installing of CU11 or after CU11. The .NET Framework 4.7.2 will be required for a future CU of Exchange 2016.
Another dependency is Visual C++, you might have seen this in previous CU’s and also in Exchange 2010 Update Rollup 23 as well. To avoid any issue, install Visual C++ 2012 (https://www.microsoft.com/download/details.aspx?id=30679) before installing Exchange 2016 CU11.
Exchange 2016 CU11 does not have any schema changes. If you’re upgrading from an older version of Exchange 2016, Active Directory changes (in the configuration container) might be needed. These will automatically be applied by the setup application, but you can also choose to update the configuration partition manually by running setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
As always, you should test a Cumulative Update thoroughly before bringing it to production, it won’t be the first time something goes wrong in production with a CU. But I have to say, I haven’t seen any major blocking issues so far…
More information and downloads of Exchange 2016 CU11:
On Tuesday december 13, 2016 Microsoft has released its quaterly updates:
and Update Rollups:
Looking at Exchange 2016, what does this CU bring us?
There are minor changes to the user interface of Outlook on the Web or Outlook Web App, whatever you may call it. It’s not that dramatically, the formatting controls have been moved to the bottom of the frame containing the editing pane, as can be seen on the following screenshot.
And finally, there’s support for the .NET Framework 4.6.2. Using .NET Framework 4.6.2 is still optional (but recommended), but the upcoming release in March 2017 (Exchange 2016 CU5) will require the use of .NET Framework 4.6.2.
As you might have noticed, Exchange 2016 CU3 (the previous release) introduced support for Windows Server 2016. This was also announced at the Ignite 2016 in Atlanta. Unfortunately there was a major flaw in Windows 2016 clustering that caused issues with Exchange 2016 in a Database Availability Group configuration. This has now been fixed by the Windows team (KB3206632), and Exchange 2016 again fully supports Windows 2016. The hotfix is mentioned is mandatory, and the setup application does a check for this hotfix.
Exchange 2016 does not introduce any new schema changes, but you may execute setup.exe /prepareAD /IAcceptExchangeServerLicenseTerms to make sure any changes in the configuration partition are applied successfully.
As usual, and especially after the latest issues with Exchange 2016 CU3 and Windows 2016 I strongly encourage everybody to thoroughly test Exchange 2016 CU4 (or any other update that’s needed of course) in your lab environment before bringing it into production!
Microsoft has released Exchange 2013 CU9, three months after the release of CU8. Microsoft has made a solid Cumulative Update this time (just like CU8 by the way) and during testing not much issues were found.
There aren’t any new features in this Cumulative Update, and personally I don’t expect any new features anymore in future Cumulative Updates either. All development efforts at Microsoft are currently targeted towards Exchange Server 2016.
The official announcement of CU9 can be found on The Exchange Team Blog, CU9 itself can be downloaded from the Microsoft Download Center, just as the accompanying CU9 UM Language Packs.
Continue reading Install Exchange 2013 Cumulative Update 9