{"id":164617,"date":"2022-04-20T13:35:58","date_gmt":"2022-04-20T18:35:58","guid":{"rendered":"https:\/\/itblog.ldlnet.net\/?p=164617"},"modified":"2023-08-31T07:20:21","modified_gmt":"2023-08-31T12:20:21","slug":"exchange-2019-cu12-and-exchange-2016-cu23-for-first-half-of-2022-released","status":"publish","type":"post","link":"https:\/\/itblog.ldlnet.net\/index.php\/2022\/04\/20\/exchange-2019-cu12-and-exchange-2016-cu23-for-first-half-of-2022-released\/","title":{"rendered":"Exchange 2019 CU12 and Exchange 2016 CU23 for first half of 2022 released"},"content":{"rendered":"\n

This was just released this morning by the Exchange Team. I will always attempt to keep up with Exchange updates as they come out. This article is worth a read as there are MANY big changes to the product including Terms of Service and Hybrid Functionality. Looks like I’m going to be updating some articles on my blog! <\/strong><\/em><\/p>\n\n\n\n

\"The_Exchange_Team\"<\/a><\/figure>\n\n\n\n

The Exchange Team<\/a>
Published Apr 20 2022 10:00 AM<\/p>\n\n\n\n

\n\n\n\n

Today we are announcing the availability of Cumulative Updates (CUs) for Exchange Server 2016 and Exchange Server 2019. These CUs include fixes for customer reported issues along with all previously released Security Updates (SUs), including the updates released in the March 2022 SUs<\/a>. A full list of fixes is contained in the KB article for each CU, but we also want to highlight some important changes.<\/p>\n\n\n\n

We\u2019re thrilled to announce the availability of new features in the CU for Exchange Server 2019, such as an updated Exchange Management Tools role that enables customers who run Exchange server(s) only for recipient management purposes to shut down their last Exchange server(s) and use Windows PowerShell for recipient management. We\u2019re also excited to announce a change to the hybrid server license for Exchange Server 2019, as detailed below.<\/p>\n\n\n\n

Servicing Model Changes<\/strong><\/p>\n\n\n\n

First, we\u2019d like to share some changes to how we deliver updates (aka our servicing model) for Exchange Server. Historically, we have released quarterly CUs in March, June, September, and December. Customers have told us this is too frequent and that it hinders their ability to stay current (which for Exchange hybrid customers is a requirement<\/a>). Customers also tell us that December is not a good time to release a CU, which is why we didn\u2019t release any in December 2021.<\/p>\n\n\n\n

Today, we are announcing changes to our update delivery model<\/a> for Exchange Server. We are moving to a release cadence of two CUs per year \u2013 releasing in H1 and H2 of each calendar year, with general target release dates of March and September. But our release dates are driven by quality, so we might release updates in April or October, or some other month, depending on what we\u2019re delivering.<\/p>\n\n\n\n

The next CU will be released in H2 of 2022, and it will be for Exchange Server 2019 only; mainstream support has ended for Exchange Server 2013<\/a> and Exchange Server 2016<\/a>. We will release SUs as needed while those versions are in extended support.<\/p>\n\n\n\n

A CU release every 6 months might be too long to wait for some updates, so we may also release hotfixes between CU releases.<\/p>\n\n\n\n

With these service model changes, being current<\/em> still means running the latest CU or the one immediately preceding it (N or N-1), but the \u2018currency window\u2019 is now extended from 6 months to 1 year.<\/p>\n\n\n\n

Exchange Management Tools Update<\/strong><\/p>\n\n\n\n

Until today, organizations that have all their mailboxes in Exchange Online and use Active Directory (AD) for identity management must have a running Exchange server in their environment in order to perform recipient management activities.<\/p>\n\n\n\n

Today, we are excited to announce that Exchange Server 2019 CU12 includes an updated Exchange Management Tools role designed to address the specific customer scenario where an Exchange server is run only<\/em> because of recipient management requirements.<\/p>\n\n\n\n

The updated Management Tools role eliminates the need to have a running Exchange server for recipient management in this scenario. If you have only a single Exchange server that you use only for recipient management, you can install the updated tools on a domain-joined workstation, shut down your last Exchange server, and manage recipients using Windows PowerShell. For more information, see Manage recipients in Exchange Server 2019 Hybrid environments<\/a>.<\/p>\n\n\n\n

Hybrid Experience Updates<\/strong><\/p>\n\n\n\n

There are two more exciting updates for hybrid customers in Exchange Server 2019 CU12.<\/p>\n\n\n\n

  1. CU12 includes a change to the Exchange Server License Terms. We have updated our licensing to add a product key for Exchange 2019 hybrid servers at no additional charge! This was previously available only for Exchange 2010, Exchange 2013, and Exchange 2016. Exchange Server 2019 CU12 and the Hybrid Configuration wizard<\/a> have been updated to support this change.<\/li>
  2. CU12 also includes support for using MFA-enabled admin credentials with Hybrid Agent cmdlets. The Hybrid Management PowerShell module now works with MFA-enabled admin accounts. This module includes the following cmdlets which can now be used with MFA:<\/li><\/ol>\n\n\n\n
    Cmdlet<\/strong><\/td>Description<\/strong><\/td><\/tr>
    Get-HybridAgent<\/td>View installed Hybrid Agents<\/td><\/tr>
    Update-HybridApplication<\/td>Edit parameters of a Hybrid Application<\/td><\/tr>
    Get-HybridApplication<\/td>View all Hybrid Applications<\/td><\/tr>
    Remove-HybridApplication<\/td>Remove a Hybrid Application<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Support for Windows Server 2022<\/strong><\/p>\n\n\n\n

    CU12 also introduces support for running Exchange Server 2019 on Windows Server 2022 and in environments that use Windows Server 2022 Active Directory servers.<\/p>\n\n\n\n

    Servers running Exchange Server 2013 or Exchange Server 2016 can also be used in environments with Windows Server 2022 Active Directory servers as long as they are running the latest CU.<\/p>\n\n\n\n

    Support for Exchange Server and Windows Server 2022 is detailed below and documented in the Exchange Server supportability matrix<\/a> along with details on other Exchange Server operating system support.<\/p>\n\n\n\n

    Exchange Server Version<\/strong><\/td>Windows Server 2022 OS<\/strong><\/td>Windows Server 2022 AD<\/strong><\/td><\/tr><\/thead>
    Exchange Server 2019<\/td>X<\/td>X<\/td><\/tr>
    Exchange Server 2016<\/td> <\/td>X<\/td><\/tr>
    Exchange Server 2013<\/td> <\/td>X<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    New Microsoft Bounty Program for Exchange Server<\/strong><\/p>\n\n\n\n

    We strongly believe that close partnerships with security researchers help make customers more secure. Security researchers play an integral role in the ecosystem by discovering vulnerabilities missed in the software development process, and each year we partner together to better protect billions of users worldwide.<\/p>\n\n\n\n

    Today, we are also sharing that we have launched a security vulnerability bounty program for Microsoft Exchange Server<\/a> via the Microsoft Applications and On-Premises Servers Bounty Program. Individuals across the globe can now receive monetary rewards for submitting security vulnerabilities found in Exchange Server shipping on the latest, fully patched version of Windows. For the new bounty program, we request you submit bugs on any supported version of Exchange Server.<\/p>\n\n\n\n

    Release Details<\/p>\n\n\n\n

    The KB articles that describe the fixes in each release and product downloads are as follows:<\/p>\n\n\n\n