Issues that this cumulative update fixes
This cumulative update also fixes the issues that are described in the following Microsoft Knowledge Base articles:
- 4076516 Email message body is garbled when the Russian version of Outlook is used in Exchange Server 2016
- 4095967 CultureNotFoundException when you select an LCID 4096 language in Exchange Server 2016
- 4456225 The image in a signature that's created in Outlook on the web isn't visible to external users in Exchange Server 2016
- 4456226 Require SSL setting of MAPI virtual directory is reset after you install a cumulative update of Exchange Server 2016
- 4456227 ActiveSync clients cannot connect or synchronizing is delayed in an Exchange Server environment
- 4456228 Add an option to control UseAscReqNoToken through app configuration for Exchange Server 2016
- 4456229 Irrelevant management role entries without parameters are displayed in Exchange Server 2016
- 4456230 Component/protocol level bypass option for InternetWebProxy to avoid unnecessary proxy traffic within internal networks
- 4456231 AdvancedDataGovernanceLogs is created on the D drive after deploying Exchange Server 2016
- 4456232 Outlook on the web enters an authentication loop when you use device registration in Exchange Server 2016
- 4456234 Email can't be delivered when the subject has an unknown character set in Exchange Server 2016
- 4456240 "CrimsonProbe has been poisoned repeatedly" error when migrating mailboxes to Exchange Server 2016
- 4456243 Hashed lines shown in scheduling assistant when Exchange Server 2016 tries to retrieve free/busy information across untrusted forests
- 4456244 Public folder forwards the new item that you create in Exchange Server 2016
- 4456245 Event ID 4999 and NullReferenceException when the New-MailboxRestoreRequest and New-MailboxExportRequest cmdlets fail in Exchange Server 2016
- 4456247 StoreDriver.config validation fails then meeting reminder can't be set to "None" in Exchange Server 2016
- 4456249 Message tracking logs can't be fully indexed in Exchange Server 2016
- 4456250 Users can download and view attachments that exceed the maximum attachment size setting in mobile device mailbox policy in Exchange Server 2016
- 4456259 Exchange Server 2016 user can't access a shared calendar from Exchange Server 2013
- 4456233 UAPStatisticsLog and RecordReview are created on the D drive after you deploy Exchange Server 2016
- 4459847 Can't send S/MIME encrypted mail or update the S/MIME control from Outlook on the web in Exchange Server 2016
- 4459266 Description of the security update for Microsoft Exchange Server 2013 and 2016: October 9, 2018
Get Cumulative Update 11 for Exchange Server 2016
- The Cumulative Update 11 package can be used to run a new installation of Exchange Server 2016 or to upgrade an existing Exchange Server 2016 installation to Cumulative Update 11.
- You don't have to install any previously released Exchange Server 2016 cumulative updates or service packs before you install Cumulative Update 11.
Cumulative update information
This cumulative update requires Microsoft .NET Framework 4.7.1.
A component that's used within Exchange Server requires a new Visual C++ component to be installed together with Exchange Server. This prerequisite can be downloaded at Visual C++ Redistributable Packages for Visual Studio 2013. For more information, see KB 4295081.
For more information about the prerequisites for the setup of Exchange Server 2016, see Exchange 2016 prerequisites.
You may have to restart the computer after you apply this cumulative update package.
You don't have to make any changes to the registry after you apply this cumulative update package.
After you install this cumulative update package, you can't uninstall the package to revert to an earlier version of Exchange Server 2016. If you uninstall this cumulative update package, Exchange Server 2016 is removed from the server.
Known issues in this cumulative update
After you install Cumulative Update 11 for Exchange Server 2016, the Accept button disappears in the invitation email message of a shared calendar in the Outlook on the web client (previously known as Outlook Web App). Therefore, you cannot add the shared calendar by clicking the Accept button directly. To work around this issue, you can use one of the following methods:
Open the invitation from the Notifications pane in Outlook on the web.
Add the shared calendar manually in Outlook on the web. For more information, see How to open a shared calendar from an Outlook sharing invitation.
Open the invitation in Outlook, and then add the shared calendar.
For more information about the deployment of Exchange Server 2016, see Release notes for Exchange 2016.
For more information about the coexistence of Exchange Server 2016 and earlier versions of Exchange Server in the same environment, see Exchange 2016 system requirements.
For more information about other Exchange updates, see Exchange Server Updates: Build numbers and release dates.