CU4 | EighTwOne (821)

The Exchange Team released the quarterly Cumulative Updates for Exchange Server 2019 as well as Exchange 2016. One significant change with these updates is the requirement for .NET Framework 4.8, as announced earlier. Also, Exchange 2019 CU4 comes with an updated Exchange calculator. Links to the updates as well as a description of changes and fixes are described below.

Version	Build	KB	Download	UMLP	Schema
Exchange 2019 CU4	15.2.529.5	KB4522149	VLSC		N
Exchange 2016 CU15	15.1.1913.5	KB4522150	Download	UMLP	N

Exchange 2019 CU4 fixes:

4528696 Exchange PowerShell cmdlets take longer time to run in Exchange Server 2019
4528695 Event ID 4009 when using SubjectOrBodyMatchesPatterns on Edge server in Exchange Server 2019
4528694 Can’t open .ics file in Outlook on the web in Exchange Server 2019
4528692 “A parameter was specified that isn’t valid” error when creating transport rule in Exchange Server 2019
4523519 Set-SendConnector doesn’t work for Exchange Server in hybrid scenarios with Edge Server installed
4528688 Only one recipient shows when saving draft by using Exchange ActiveSync version 16.0 in Exchange Server 2019
4528693 Get-CalendarDiagnosticLog is proxied for queries within the same forest in Exchange Server 2019
4528687 NotificationClient logs aren’t purged and consume lots of disk in Exchange Server 2019
4528689 Outlook on the web shows MailTip when recipients equal the large audience size in Exchange Server 2019
4528690 Can’t move or delete folder in Outlook online mode if the destination has a folder with the same name in Exchange Server 2019
4532744 System.ArgumentNullException when you use Set-user to assign block legacy auth policy in Exchange Server 2019
4532747 Address list separation not working for a user without a mailbox in Exchange Server 2019
4523171 Description of the security update for Microsoft Exchange Server 2019, 2016, and 2013: November 12, 2019

Exchange 2016 CU15 fixes:

4515256 “The function cannot be performed…” error when you send a message that’s open for a long time in Exchange Server 2016
4528693 Get-CalendarDiagnosticLog is proxied for queries within the same forest in Exchange Server 2016
4523519 Set-SendConnector doesn’t work for Exchange Server in hybrid scenarios with Edge Server installed
4528690 Can’t move or delete folder in Outlook online mode if the destination has a folder with the same name in Exchange Server 2016
4528687 NotificationClient logs aren’t purged and consume lots of disk in Exchange Server 2016
4528689 Outlook on the web shows MailTip when recipients equal the large audience size in Exchange Server 2016
4528688 Only one recipient shows when saving draft by using Exchange ActiveSync version 16.0 in Exchange Server 2016
4528695 Event ID 4009 when using SubjectOrBodyMatchesPatterns on Edge server in Exchange Server 2016
4528694 Can’t open .ics file in Outlook on the web in Exchange Server 2016
4528692 “A parameter was specified that isn’t valid” error when creating transport rule in Exchange Server 2016
4515257 Hash mismatch is reported for Exchange DLLs in the bin directory of Exchange Server 2016
4528696 Exchange PowerShell cmdlets take longer time to run in Exchange Server 2016
4532747 Address list separation not working for a user without a mailbox in Exchange Server 2016
4523171 Description of the security update for Microsoft Exchange Server 2019, 2016, and 2013: November 12, 2019

Notes:

These Cumulative Updates do not contain schema changes compared to their previous Cumulative Update.
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 required to delay installing 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.

Today, the Exchange Team released the December updates for Exchange Server 2013 and 2016, as well as Exchange Server 2010 and 2007.

Changes introduced in Exchange Server 2016 CU4 are an updated OWA composition window, and on Windows Server 2016, KB3206632 needs to be present before CU4 can be deployed. This KB fixes – among other things – the problem with DAG members experiencing crashing IIS application pools. Be advised that the KB3206632 update for Windows Server 2016 is a whopping 1 GB. You can download this update here.

The biggest change for Exchange Server 2013 is support for .NET 4.6.2. Be advised organizations running Exchange 2016 or 2013 on .NET 4.6.1 should start testing with and planning to deploy .NET 4.6.2, as the March updates will require .NET 4.6.2, which is currently still optional.

Both Cumulative Updates introduce an important fix for indexing of Public Folder when they were in the process of being migrated. To ensure proper indexing, it is recommended to move public folder mailboxes to a different database so they will get indexed properly.

The Cumulative Updates also include DST changes, which is also contained in the latest Rollups published for Exchange 2010 and 2007.

For a list of fixes in these updates, see below.

Exchange 2016 CU4	15.1.669.32	KB3177106	Download	UMLP
Exchange 2013 CU15	15.0.1263.5	KB3197044	Download	UMLP
Exchange 2010 SP3 Rollup 16	14.3.339.0	KB3184730	Download
Exchange 2007 SP3 Rollup 22	8.3.502.0	KB3184712	Download

Exchange 2016 CU4 fixes:

KB 3202691 Public folders indexing doesn’t work correctly after you apply latest cumulative updates for Exchange Server
KB 3201358 Set-Mailbox and New-Mailbox cmdlets prevent the use of the -Office parameter in Exchange Server 2016
KB 3202998 FIX: MSExchangeOWAAppPool application pool consumes memory when it recycles and is marked as unresponsive by Health Manager
KB 3208840 Messages for the health mailboxes are stuck in queue on Exchange Server 2016
KB 3186620 Mailbox search from Exchange Management Shell fails with invalid sort value in Exchange Server 2016
KB 3199270 You can’t restore items to original folders from Recoverable Items folder in Exchange Server 2016
KB 3199353 You can’t select the receive connector role when you create a new receive connector in Exchange Server 2016
KB 3193138 Update to apply MessageCopyForSentAsEnabled to any type of mailbox in Exchange Server 2016
KB 3201350 IMAP “unread” read notifications aren’t suppressed in Exchange Server 2016
KB 3209036 FIX: “Logs will not be generated until the problem is corrected” is logged in an Exchange Server 2016 environment
KB 3212580 Editing virtual directory URLs by using EAC clears all forms of authentication in Exchange Server 2016

Exchange 2013 CU15 fixes:

KB 3198092 Update optimizes how HTML tags in an email message are evaluated in an Exchange Server 2013 environment
KB 3189547 FIX: Event ID 4999 for a System.FormatException error is logged in an Exchange Server 2013 environment
KB 3198046 FIX: The UM mailbox policy is not honored when UM call answering rules setting is set to False in an Exchange Server 2013 environment
KB 3195995 FIX: Event ID 4999 with MSExchangerepl.exe crash in Exchange Server 2013
KB 3208886 Send As permission of a linked mailbox is granted to a user in the wrong forest in Exchange Server 2013
KB 3188315 Messages are stuck in outbox when additional mailboxes are configured in Outlook on Exchange Server 2013
KB 3202691 Public folders indexing doesn’t work correctly after you apply latest cumulative updates for Exchange Server
KB 3203039 PostalAddressIndex property isn’t returning the correct value in Exchange Server 2013
KB 3198043 Shadow OAB downloads don’t complete in Exchange Server 2013
KB 3208885 Microsoft.Exchange.Store.Worker.exe process crashes after mailbox is disabled in Exchange Server 2013
KB 3201966 MSExchangeOWAAppPool application pool consumes excessive memory on restart in Exchange Server 2013
KB 3209041 FIX: An ActiveSync device becomes unresponsive until the sync process is complete in an Exchange Server environment
KB 3209013 FIX: The LegacyDN of a user is displayed incorrectly in the From field in the Sent Items folder on an ActiveSync device
KB 3209018 FIX: Results exported through the eDiscovery PST Export Tool never finishes in an Exchange Server environment
KB 3199519 Inconsistent search results when email body contains both English and non-English characters in Exchange Server 2013
KB 3211326 “ConversionFailedException” error when emails are sent on the hour in Exchange Server 2013

Notes:

Exchange 2016 CU4 doesn’t incldue schema changes compared to CU4, however, Exchange 2016 CU4 as well as Exchange 2013 CU15 may introduce RBAC changes in your environment. Where applicable, use setup /PrepareSchema to update the schema or /PrepareAD to apply RBAC changes, before deploying or updating Exchange servers. To verify this step 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. Do note that upgrading, before installing the Exchange binaries, setup will put the server in server-wide offline-mode.
Using Windows Management Framework (WMF)/PowerShell version 5 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 allowed to stay at least 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 of upgrading 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 TechNet forum for any issues.