Blog Post

Exchange Team Blog
2 MIN READ

Released: September 2019 Quarterly Exchange Updates

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Sep 17, 2019

Today we are announcing the availability of quarterly servicing cumulative updates for Exchange Server 2016 and 2019. These updates include fixes for customer reported issues as well as all previously released security updates. 

Release Details

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

Additional Information

Microsoft recommends all customers test the deployment of any update in their lab environment to determine the proper installation process for your production environment. For information on extending the schema and configuring Active Directory, please review the appropriate documentation.

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 the resolution steps in KB981474 to adjust the settings.

Reminder: Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the currently supported cumulative update for the product version in use, e.g., 2013 Cumulative Update 23; 2016 Cumulative Update 14 or 13; 2019 Cumulative Update 3 or 2.

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

Note: Documentation may not be fully available at the time this post is published.

The Exchange Team

Updated Sep 17, 2019
Version 5.0

13 Comments

  • Martin_Aigner - They are not required for either of these CUs. 

    Sam_T  - We always make our best effort to call out when they are required. When they are not, we don't mention it. 

    (edited: please see my later reply)

  • Sam_T's avatar
    Sam_T
    Iron Contributor

    Yet another poorly thought out article. After all these years we're supposed to keep asking the same old questions about schema updates and /prepareAD and the other usual questions ?  After all these years you still cant be bothered to create a helpful article for the poor souls who have to go out and deploy these CUs?  Is the goal perhaps, as someone said earlier, for these updates to fail so that we'll all decide that we'd better move to the cloud asap ?

     

    Is there a button we can press here to express the intense loathing of an article or are we just supposed to just "like" all of these posts ?

  • Martin_Aigner's avatar
    Martin_Aigner
    Copper Contributor

    Thanks guys, seems some long expected fixes are included here. 

    Please allow me one question, as it was not 100% clear from the documentation provided. Do we need to run a /PrepareAD /PrepareDomain (/PrepareAllDomains) before we are able to roll out (update to) this release on Exchange 2016 CU13 or can this be skipped this time?

    It just includes a known issue in the KB that sounds familiar to me as valid already for previous releases