Exchange 2016 CU9 Released!

The Exchange Team released the March updates for Exchange Server 2013 and 2016, and these Cumulative Updates contain a ton of fixes. Like the previous Cumulative Update for Exchange 2013 and Exchange 2016, these Cumulative Updates support .NET Framework 4.7.1. Be advised that .NET Framework 4.7.1 will be required for the next cycle of quarterly updates, to be released in June 2018.

Exchange 2016 CU9 fixes:

• 4054513 Mailbox usage status bar in OWA displays incorrect mailbox usage
• 4055433 User is added to an entire series when accepting a single instance through Exchange ActiveSync
• 4057216 Health mailbox’s password is exposed in logs for a failed probe in Exchange Server 2016 and 2013
• 4058373 “A parameter cannot be found” error when you run Install-AntiSpamAgents.ps1 in Exchange Server 2016 CU7
• 4058379 All cross-forest meeting updates have to be accepted again in Exchange Server 2016 and 2013
• 4058383 Exchange Control Panel (ECP) redirection fails in Exchange Server 2016
• 4058384 Get-CalendarDiagnosticAnalysis shows DateTime in 12-hour clock in Exchange Server 2016 and 2013
• 4058399 Disabling a mailbox can’t remove legacyExchangeDN from user’s properties in Exchange Server 2016
• 4073094 Emails outside a UID range are returned when you request for emails by using IMAP
• 4073095 “550 5.6.0 CAT.InvalidContent.Exception” and email isn’t delivered in Exchange Server 2016 and 2013
• 4073104 PIN can be reset on a Unified Messaging (UM)-enabled mailbox for a user outside a scoped OU
• 4073103 The Enable-Mailbox cmdlet doesn’t block migrated users from provisioning in Exchange Server 2016
• 4073107 Language can’t be changed when a user from a child domain tries to change language in OWA
• 4073111 Can’t access a CAS website such as OWA/ECP/Autodiscover in Exchange Server 2016
• 4073110 You can’t access OWA or ECP after you install Exchange Server 2016 CU8
• 4073109 Search-MailboxAuditLog -ShowDetails not showing all messages in Exchange Server 2016
• 4073114 “ADOperationException” error when OWA text verification fails in Exchange Server 2016
• 4073214 Can’t enable OWA offline access in Exchange Server 2016
• 4073531 CultureNotFoundException when selecting a LCID 4096 language in OWA for Exchange Server 2016
• 4076520 MatchSubdomains isn’t usable for Set-AcceptedDomain in Exchange Server 2016
• 4076741 Incorrect NDR when an administrator deletes a message from a queue in Exchange Server 2016
• 4077655 Event ID 258 “Unable to determine the installed file” after you uninstall Windows PowerShell 2.0
• 4057290 Incorrect user is returned in the ECP when one user’s display name matches another user’s alias
• 4058372 Blank page in Exchange Admin Center Audit Log in Exchange Server 2016
• 4058382 Can’t retrieve time slot information about private calendar items as a delegate on another user’s account in Exchange Server 2016
• 4058401 Administrator audit logging does not record Set-ServerComponentState cmdlet details in Exchange Server 2013 or 2016 environment
• 4073097 Monitoring probes of ECP.Proxy health checks fail on all CAS roles in Exchange Server 2013 and 2016
• 4073098 The ETS and EXS groups are incorrectly granted “SeDebugPrivilege” in Exchange Server 2016 on-premises
• 4073108 “There was a problem loading your options” error when a user accesses OWA Voice Mail options in Exchange Server 2016
• 4077924 Store Worker process crashes when you move, restore, or repair mailboxes that have issues with the logical index within the database in Exchange Server 2016
• 4091453 Update improves linguistics features and CJK handling for search in Exchange Server 2016
• 4073392 Description of the security update for Microsoft Exchange: March 13, 2018

Exchange 2013 CU20 fixes:

• 4073392 Description of the security update for Microsoft Exchange: March 13, 2018
• 4073094 Emails outside a UID range are returned when you request for emails by using IMAP
• 4073097 Monitoring probes of ECP.Proxy health checks fail on all CAS roles in Exchange Server 2013 and 2016
• 4057216 Health mailbox’s password is exposed in logs for a failed probe in Exchange Server 2016 and 2013
• 4058384 Get-CalendarDiagnosticAnalysis shows DateTime in 12-hour clock in Exchange Server 2016 and 2013
• 4057290 Incorrect user is returned in the ECP when one user’s display name matches another user’s alias
• 4055433 User is added to an entire series when accepting a single instance through Exchange ActiveSync
• 4058401 Administrator audit logging does not record Set-ServerComponentState cmdlet details in Exchange Server 2013 or 2016 environment
• 4073095 “550 5.6.0 CAT.InvalidContent.Exception” and email isn’t delivered in Exchange Server 2016 and 2013
• 4058379 All cross-forest meeting updates have to be accepted again in Exchange Server 2016 and 2013
• 4073093 Save issues occur when you use the plain Text Editor in OWA of Exchange Server 2013
• 4073096 Emails sent from a shared mailbox aren’t saved in Sent Items when MessageCopyForSentAsEnabled is True

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
• 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).
• 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.

Photo by Fab Lentz on Unsplash