Exchange Updates – December 2020

Posted on December 15, 2020 by Michel de Rooij

The Exchange Team released the quarterly Cumulative Updates for Exchange Server 2019 as well as Exchange 2016. Be advised that Exchange 2016 will receive its final CU in March, 2021.

Links to the updates as well as a description of changes and fixes are described below.

Version	Build	KB	Download	UMLP	Schema	PrepareAD
Exchange 2019 CU8	15.2.792.3	KB4588885	VLSC		N	Y
Exchange 2016 CU19	15.1.2176.2	KB4588884	Download	UMLP	N	Y

Exchange 2019 CU8 fixes:

4588297 Attachments can’t be downloaded or previewed from Outlook Web App
4583531 Design change about inline images will be forced to download but not open in a new tab of OWA in Exchange Server 2019
4583532 ELC MRM archiving fails due to DomainName in AuthServer in Exchange Server 2019
4583533 Exchange Server 2019 installation fails with error “The user has insufficient access rights”
4583534 Event ID 65535 System.Runtime.Serialization errors in Application log in Exchange Server 2019
4583535 New-Moverequest, Resume-Moverequest, and Remove-Moverequest not logged in Audit logs in Exchange Server 2019
4583536 Set-MailboxFolderPermission is included in Mail Recipient Creation in Exchange Server 2019
4583537 Update Korean word breaker in Exchange Server 2019
4583538 Microsoft Teams REST calls exceed the default value of maxQueryStringLength in Exchange Server 2019
4583539 Non-breaking space is visible in message body in Outlook in Exchange Server 2019
4583542 Server assisted search in Outlook doesn’t return more than 175 items in Exchange Server 2019
4583544 Lots of LDAP requests for FE MAPI w3wp lead to DDoS on DCs in Exchange Server 2019
4583545 Make DomainName in Authserver a multivalued parameter in Exchange Server 2019
4593465 Description of the security update for Microsoft Exchange Server 2019 and 2016: December 8, 2020

Exchange 2016 CU19 fixes:

4588297 Attachments can’t be downloaded or previewed from Outlook Web App
4583531 Design change about inline images will be forced to download but not open in a new tab of OWA in Exchange Server 2016
4583532 ELC MRM archiving fails due to DomainName in AuthServer in Exchange Server 2016
4583533 Exchange Server 2016 installation fails with error “The user has insufficient access rights”
4583534 Event ID 65535 System.Runtime.Serialization errors in Application log in Exchange Server 2016
4583535 New-Moverequest, Resume-Moverequest, and Remove-Moverequest not logged in Audit logs in Exchange Server 2016
4583536 Set-MailboxFolderPermission is included in Mail Recipient Creation in Exchange Server 2016
4583537 Update Korean word breaker in Exchange Server 2016
4583538 Microsoft Teams REST calls exceed the default value of maxQueryStringLength in Exchange Server 2016
4583539 Non-breaking space is visible in message body in Outlook in Exchange Server 2016
4583545 Make DomainName in Authserver a multivalued parameter in Exchange Server 2016
4593465 Description of the security update for Microsoft Exchange Server 2019 and 2016: December 8, 2020

Notes:

These Cumulative Updates contain schema changes compared to the previous Cumulative Update. This requires you to run /PrepareSchema. Also, Active Directory changes require you to run PrepareAD (which also can perform the schema update, depending permissions). Consult the Exchange schema versions page for object version numbers.
When upgrading from an n-2 or earlier version of Exchange, or an early version of the .NET Framework, consult Upgrade Paths for CU’s & .NET.
Don’t forget to put the Exchange server in maintenance mode prior to updating. Regardless, setup will put the server in server-wide offline mode post-analysis, before making actual changes.
When using Exchange hybrid deployments or Exchange Online Archiving (EOA), you are allowed to trail at most one version (n-1).
If you want to speed up the update process for systems without internet access, you can follow the procedure described here to disable publisher’s certificate revocation checking.
Cumulative Updates can be installed directly; no need to install RTM prior to installing Cumulative Updates.
Once installed, you can’t uninstall a Cumulative Update nor any of the installed Exchange server roles.
The order of installation shouldn’t matter with the “every server is an island” concept, yet recommended is to upgrade internet-facing, non-internet-facing servers first, followed by Edge Transports.

Caution:

As for any update, I recommend to thoroughly test updates in a test environment prior to implementing them in production. When you lack such facilities, hold out a few days and monitor the comments on the original publication or forums for any issues.

Exchange Updates – December 2017

Posted on December 19, 2017 by Michel de Rooij

The Exchange Team released the December updates for Exchange Server 2013 and 2016. Apart from the usual set of fixes, these Cumulative Updates also have the following enhancements:

Like announced earlier, these quartely updates introduce support for .NET Framework 4.7.1. Be advised that .NET Framework 4.7.1 will be required for the quarterly updates to be released in June 2018.
Upgrading an existing Exchange deployment with these Cumulative Updates will preserve TLS cryptography settings.
Support for Hybrid Modern Authentication (Info).

Version	Build	KB Article	Download	UMLP	Schema Changes
Exchange 2016 CU8	15.1.1415.2	KB4035145	Download	UMLP	Yes
Exchange 2013 CU19	15.0.1365.1	KB4037224	Download	UMLP	No

Exchange 2016 CU8 fixes:

4056329 Can’t access EWS from Outlook/OWA add-ins via makeEwsRequestAsync in Exchange Server 2016 and Exchange Server 2013
4054516 “Your request can’t” error when accessing an archive mailbox via OWA in Exchange Server 2016
4055953 The recipient scope setting doesn’t work for sibling domains in Exchange Server 2016
4055435 No MAPI network interface is found after you install Exchange Server 2016 CU7
4056609 Event ID 4999 and mailbox transport delivery service does not start after you install Exchange Server 2016 CU7
4045655 Description of the security update for Microsoft Exchange: December 12, 2017
4057248 Many Watson reports for StoragePermanentException in Exchange Server 2016

Exchange 2013 CU19 fixes:

4046316 MAPI over HTTP can’t remove client sessions timely if using OAuth and the resource has a master account in Exchange Server 2013
4046205 W3wp high CPU usage in Exchange Server 2013
4046182 Event ID 4999 or 1007 if diagnostics service crashes repeatedly in Exchange Server 2013
4056329 Can’t access EWS from Outlook/OWA add-ins via makeEwsRequestAsync in Exchange Server 2016 and Exchange Server 2013
4045655 Description of the security update for Microsoft Exchange: December 12, 2017

Exchange 2010
In addition the Cumulative Updates, Exchange Server 2010 SP3 also received an important update, which fixes the issue described in KB4054456. You can download Rollup 19 here, which will raise the version number to 14.3.382.0. The related KB article is KB4035162.

Notes:

Exchange 2016 CU7 and later requires Forest Functionality Level 2008R2 or later.
Exchange 2016 CU8 and Exchange 2013 CU18 do not contain schema changes compared to their previous Cumulative Update. However, they may introduce RBAC changes in your environment. Use setup /PrepareSchema to manually update the schema, or use /PrepareAD to apply RBAC changes, before deploying or updating Exchange servers. To see if you need to update the schema compared to your version or verify the update has been performed, consult the Exchange schema overview.
When upgrading your Exchange 2013 or 2016 installation, don’t forget to put the server in maintenance mode when required. Regardless, setup will put the server in server-wide offline mode post-analysis, before making actual changes.
Using Windows Management Framework (WMF)/PowerShell version 5 or later on anything earlier than Windows Server 2016 is not supported. Don’t install WMF5 on your Exchange servers running on Windows Server 2012 R2 or earlier.
When using Exchange hybrid deployments or Exchange Online Archiving (EOA), you are required to stay at most one version behind (n-1).
If you want to speed up the update process for systems without internet access, you can follow the procedure described here to disable publisher’s certificate revocation checking.
Cumulative Updates can be installed directly, i.e. no need to install RTM prior to installing Cumulative Updates.
Once installed, you can’t uninstall a Cumulative Update nor any of the installed Exchange server roles.
The order in which you upgrade servers with Cumulative Updates is irrelevant.

Caution: As for any update, I recommend to thoroughly test updates in a test environment prior to implementing them in production. When you lack such facilities, hold out a few days and monitor the comments on the original publication or forums for any issues.

Exchange 2013 Cumulative Update 8

Posted on March 19, 2015 by Michel de Rooij

Today, Cumulative Update 8 for Exchange Server 2013 was released by the Exchange Team (KB3030080). This update raises Exchange 2013 version number to 15.0.1076.9.

This Cumulative Update introduces changes in the following areas:

Calendar and Contact Modern Public Folders favorites added in Outlook are now accessible in OWA.
Batch Migration of Public Folders to 2013 improves migration throughput and PF migration experience.
Increased support limits for Public Folders with Exchange on-premises deployments (500,000 for co-existence, or 1,000,000 for CU8-only deployments). Number of supported PF mailboxes stands at 100 though, with a per-PF mailbox limit of 100,000 Public Folders.
Supported EAS clients are now redirected to Office 365 upon successful Hybrid migration.

Next to DST corrections, this Cumulative Update introduces the following fixes:

3045301 SMTP is not transported over TLS 1.1 or TLS 1.2 protocol in an Exchange Server 2013 environment
3040681 MapiExceptionTimeout error during a hierarchy synchronization process of multiple public folders in Exchange Server 2013
3037417 Outlook cannot download an OAB file in an Exchange Server 2013 environment that mixes Exchange Server 2010
3037291 Can’t add members to Outlook contact group by using MAPI over HTTP
3036952 Mailbox quota warning messages are not sent out after you migrate from Exchange Server 2010 to Exchange Server 2013
3036374 Incorrect NDR size limit message is displayed for German localization in an Exchange Server 2013 environment
3036365 “The specified address is not recognized or does not exist” error message in an Exchange Server 2013 environment
3032153 Recurring events in Calendar over DST are not adjusted on all ActiveSync devices in all Exchange Server environments
3031133 Default folders are duplicated after you migrate mailboxes to Exchange Server 2013
3031069 Mails are spoofed in Office 365 or in an Exchange Server 2013 environment
3030629 Outlook cannot open a shared folder on which a group you attend has the Reviewer permission in Exchange Server 2013
3018518 Garbled text in the Japanese “From” field in a forwarded DBCS message
3016440 Public folder mailbox quarantined
3012266 Update to increase availability address spaces to 200 in Exchange Server 2013
3011579 SaveChanges fails and generates a MAPI_E_NOT_FOUND error message on a large message body in Exchange 2013 CU6
3006861 “The SMTP address has no mailbox associated with it” error when you access a user’s mailbox by using EWS application
3003974 Improved support for MSG files in an Exchange Server 2013 environment where OPENTEXT products are used
2988060 Cannot see the auditing results for an HttpModule-based extension for MAPI over HTTP protocol in Exchange Server 2013
2986941 “An Active Directory error 0x51 occurred” error when you run the “Setup /PrepareAD” command from a DC in Exchange 2013
2961741 Exchange Server 2013 delegated setup fails when the setup account is a member of Domain Admins

Notes:

When using Exchange hybrid deployments or Exchange Online Archiving (EOA), you are required to stay current.
Previously released CU7 introduced changes to prevent restoration of pre-CU7 databases. Pre-CU7 users are advised to perform a full backup post-upgrade to CU7 or later.
Previously released CU7 added support for hierarchies containing 250,000 modern public folders. Consult this article for co-existence scenarios.
Previously released CU5 introduced OAB architectural changes which are documented here. If you are affected, it is recommended to update CAS servers prior to Mailbox servers.

This Cumulative Update does not include schema or Active Directory changes when compared to Cumulative Update 7. If you have deployed a version earlier than CU7, make sure you run PrepareSchema /PrepareAD. If you want to speed up the Cumulative Update installation process, you can temporarily disable certificate revocation checking as described here.

Note that Cumulative Updates can be installed directly, i.e. no need to install RTM or Service Packs prior to installing Cumulative Updates. Note that once installed, you can’t uninstall a Cumulative Update nor any of the installed Exchange server roles. The order of upgrading servers is irrelevant, unlike with previous generations of Exchange.

Finally, and I can’t emphasize this enough: For any Hotfix, Rollup, Service Pack or Cumulative Update, I’d recommend to thoroughly test this in a test and acceptance environment first, prior to implementing it in production. When you lack such facilities, hold out a week or two and monitor the comments on the release article or TechNet forum for any issues.

You can download Exchange 2013 Cumulative Update 8 here; UM Language Packs can be found here.