March 2021 Quarterly Exchange Updates

Mitglied: Dani
Today we are announcing the availability of quarterly servicing cumulative updates (CUs) for Exchange Server 2016 and Exchange Server 2019. These CUs include fixes for customer reported issues as well as all previously released security updates. Although we mentioned in a previous announcement that this release would be the final cumulative update for Exchange 2016, we do expect to release one more CU for Exchange 2016 next quarter which will includes all fixes made for customer reported and accepted issues received before the end of mainstream support.

A full list of fixes is contained in the KB article for each CU, but we wanted to highlight that these latest CUs contain the fixes that were previously released as Exchange Server Security Updates on March 2, 2021. This means you don’t have to install the March 2021 Security Updates after installing the March 2021 CUs.

The KB articles that describe the fixes in each release and product downloads are as follows:

Exchange Server 2019 Cumulative Update 9 (KB4602570), VLSC Download
Exchange Server 2016 Cumulative Update 20 (KB4602569), Download, UM Lang Packs

Microsoft recommends all customers test the deployment of any update in their lab environment to determine the proper installation process for your production environment. These updates may contain schema and directory changes and so require you prepare Active Directory (AD) and all domains. You can find more information on that process here. Schema changes can be tracked here.

Also, to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to Unrestricted on the server being upgraded or installed. To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the machine being upgraded. If the policies are NOT set to Unrestricted you should use these resolution steps to adjust the settings.

Additionally, a reminder that if you plan to install any Cumulative Update using the unattended option with either PowerShell or Command Prompt, make sure you specify either the full path to the setup.exe file or use a “.” in front of the command if you are running it directly from directory containing the update. If you do not the Exchange Server Setup program may indicate that it completed successfully when it did not. Read more here.

Reminder: Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, and those using Exchange Online Archiving with their on-premises Exchange deployment are required to deploy the currently supported CU for the product version in use.

For the latest information on the Exchange Server and product announcements please see What's New in Exchange Server and Exchange Server Release Notes.

Original Thread

Content-Key: 663809

Url: https://administrator.pro/contentid/663809

Printed on: November 30, 2021 at 05:11 o'clock

Mitglied: em-pie
em-pie Mar 17, 2021 at 20:20:56 (UTC)
Goto Top
Mal sehen, ob es tatsächlich nun doch beim CU20 als letztes Mainstrem-Support-Package bleibt, oder ob es, u.U. nicht doch noch ein CU21 geben könnte. Mit Stand Februar hatte man dies offenbar noch angedacht: https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-serve ...

Könnte aber sein, dass die Punkte, die man glaubte, nicht mehr bis ins CU20 zu fixen nun doch geschafft haben!?
Mitglied: beidermachtvongreyscull
beidermachtvongreyscull Mar 18, 2021 at 09:01:17 (UTC)
Goto Top
Gott, ich liebe so was

Microsoft recommends all customers test the deployment of any update in their lab environment to determine the proper installation process for your production environment. These updates may contain schema and directory changes and so require you prepare Active Directory (AD) and all domains. You can find more information on that process here. Schema changes can be tracked here.

:-D face-big-smile
Mitglied: Th0mKa
Th0mKa Mar 18, 2021 updated at 12:16:45 (UTC)
Goto Top
Zitat von @em-pie:

Mal sehen, ob es tatsächlich nun doch beim CU20 als letztes Mainstrem-Support-Package bleibt, oder ob es, u.U. nicht doch noch ein CU21 geben könnte.

Zitat von @Dani:

Although we mentioned in a previous announcement that this release would be the final cumulative update for Exchange 2016, we do expect to release one more CU for Exchange 2016 next quarter which will includes all fixes made for customer reported and accepted issues received before the end of mainstream support.

/Thomas
Mitglied: Th0mKa
Th0mKa Mar 18, 2021 at 12:18:43 (UTC)
Goto Top
Zitat von @beidermachtvongreyscull:

Gott, ich liebe so was

Naja, es ist eine Empfehlung. Niemand hindert dich das Update einfach so in deine Produktivumgebung zu deployen.

/Thomas
Mitglied: beidermachtvongreyscull
beidermachtvongreyscull Mar 18, 2021 updated at 13:11:51 (UTC)
Goto Top
Zitat von @Th0mKa:

Naja, es ist eine Empfehlung. Niemand hindert dich das Update einfach so in deine Produktivumgebung zu deployen.

/Thomas

Wie wahr.
"Zu Risiken und Nebenwirkungen fragen Sie Ihren Arzt oder Apotheker." ist auch eine, aber bei einem notwendigen Übel wird es doch eher zu einer Farce für mich, ähnlich wie "Musste halt machen, kann aber Kacke werden.".
Mitglied: Th0mKa
Th0mKa Mar 18, 2021 at 13:24:13 (UTC)
Goto Top
Zitat von @beidermachtvongreyscull:

aber bei einem notwendigen Übel wird es doch eher zu einer Farce für mich, ähnlich wie "Musste halt machen, kann aber Kacke werden.".

Ist es das bei der Empfehlung deines Arztes nicht auch?

/Thomas
Mitglied: beidermachtvongreyscull
beidermachtvongreyscull Mar 18, 2021 at 14:13:59 (UTC)
Goto Top
Dem ist so.
Nur im medzinischen Bereich steht auch jemand, ob er will oder nicht, für Fehler gerade, meine ich.
Mitglied: Th0mKa
Th0mKa Mar 18, 2021 at 14:20:03 (UTC)
Goto Top
Zitat von @beidermachtvongreyscull:
Nur im medzinischen Bereich steht auch jemand, ob er will oder nicht, für Fehler gerade, meine ich.

Na klar, viel Spaß beim Versuch das durchzusetzen. Aber egal, eh OT.
Hot discussed articles