Mailbox migrations are among the most known tasks when you have an Exchange Server in…
Cumulative Update 14 for Exchange Server 2019
Microsoft released Cumulative Update 14 for Exchange Server 2019 (KB5035606) on February 13, 2024. Also known as Exchange Server 2019 CU14. This Cumulative Update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues. These fixes will also be included in later Cumulative Updates for Exchange Server 2019.
Table of contents
How to update Exchange Server 2019 to CU14?
It’s recommended to update the Exchange Server in the lab environment before updating it in the production environment.
- Download Cumulative Update CU14 for Exchange Server 2019 (KB5035606)
- Update to Microsoft .NET Framework 4.8
- Install Exchange Cumulative Update
Cumulative Update CU14 for Exchange Server 2019 is released as version 15.02.1544.004. Which version are you running now? Read more on how to find your Exchange version build number.
New features in Cumulative Update 14
- New daylight saving time (DST) updates for Exchange Server 2019. For more information about DST, see Daylight Saving Time Help and Support Center.
- Extended Protection enabled by default for Exchange Server 2019. For more information about prerequisites for enabling or disabling Extended Protection, see Configure Windows Extended Protection in Exchange Server.
- Support for .NET Framework 4.8.1 on Microsoft Windows Server 2022.
Vulnerabilities resolved in Cumulative Update 14
This update resolves vulnerabilities in Microsoft Exchange Server. To learn more about these vulnerabilities, see the following Common Vulnerabilities and Exposures (CVE):
Issues fixed in Cumulative Update 14
This Cumulative Update fixes the issues that are described in the following Microsoft Knowledge Base articles:
- 5035442 Exchange Mitigation Service does not log incremental updates
- 5035443 Read receipts are returned if ActiveSyncSuppressReadReceipt is “True” in Exchange Server 2019
- 5035444 System.argumentnullexception when you try to run an eDiscovery search
- 5035446 OAB shadow distribution fails if legacy authorization is blocked
- 5035448 MCDB fails and leads to lagged copy activation
- 5035450 Exchange 2019 setup installs a outdated JQuery library
- 5035452 Usernames are not displayed in Event ID 23 and 258
- 5035453 Issues in Exchange or Teams when you try to delegate information
- 5035455 MSExchangeIS stops responding and returns “System.NullReferenceExceptions” multiple times per day
- 5035456 “Deserialization blocked at location HaRpcError” error and Exchange replication stops responding
- 5035493 FIP-FS Proxy Customizations are disabled after a CU or an SU update
- 5035494 Modern attachment doesn’t work when web proxy is used in Exchange Server 2019
- 5035495 OWA displays junk operations even if junk mail reporting is disabled
- 5035497 Edit permissions option in the ECP can’t be edited
- 5035542 Remote equipment and room mailboxes can now be managed through EAC
- 5035616 Logon events failure after updating Windows Server
- 5035617 Transport rules aren’t applied to multipart or alternative messages
- 5035689 “High %Time in GC” and EWS doesn’t respond
Known issues in Cumulative Update 14
- When Setup.exe is used to run /PrepareAD, /PrepareSchema or /PrepareDomain, the installer reports that Extended Protection was configured by the installer, and it displays the following error message:
Exchange Setup has enabled Extended Protection on all the virtual directories on this machine.
File hash information
- File name: ExchangeServer2019-x64-cu14.iso
- SHA256 hash: 5A645313CF9662A12A32B48D0DE1BFDE70D93B61BD849059E1A9F27CC6ECA981
What Others Are Reading
After CU 14 on server exchange 2019, i have this message
Forbidden
You don’t have permission to access /owa/ on this server.
When I consult exchange OWA, via internet I get this message. When I consult Exchange OWA on the intranet it works. What is this message about?
Hello Ali, i have 4 Exchange server 2019 DAG Cluster, i installed cu14 on only one server and then all users have error while opening attachments in shared mailboxes in OWA. Shall i install cu14 on all the other servers, that would solve this issue?
Hi!
After installing CU14 in out Hybrid environment users have issues opening shared mailboxes via “open another mailbox” in OWA. Adding them to the left pane works fine, it’s just opening that doesn’t work.
I thought EP might be the issue but it persists after disabling it. Any ideas?
Disregard this, after about 2h after disabling EP the issue was resolved. Still unsure exactly what in EP that caused it though.
what is EP?
Hi Ali,
After i installed CU14 Windows Security log started to grow rapidly – >10.000 logging’s a day on a small Exchange installation.
I used your: “Exchange transaction logs growing rapidly” description, and figured out that “healthmailbox 0a9d551816144f5d9dca2b2d24a81d94” is causing 75% of the logging.
I tried to change the entries in “Local Policies/Audit Policies” to “no auditing” – but i didn’t help.
Hi Ali,
After installing CU14, i am unable to connect Exchange Management Shell with below error.
The WinRM client cannot process the request.
WinRM cannot complete the operation.
Also Transport Service is failing to start with error in event PoisonMessage registry not found.
Hi Ali,
We have updated Exchange 2019 to CU 14 , we faced an issue in outlook always requesting username and password , we rule back by disabled Extended Protection in Exchange Server , any please help on that ?
I have Same Problem.Please Help
Hello! That helped me:
https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/0xc000035b-when-you-use-lmcompatibility
on client computer update registry:
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
parameter lmcompatibilitylevel set to 3
and start outlook.
Hello ALI,
I hope you’re doing well.
Just one question: Every time a new CU is released, is it necessary to execute the command /PrepareSchema or can I skip direct to the /PrepareAD? My server already have a previous CU installed (CU12) and I want to install now the CU14.
Thank you
Hi Victor,
No, you don’t always have to run the /PrepareSchema command.
It depends on which schema the Active Directory is currently at. You can check that with the PowerShell script and compare it against the table.
If it’s already at the correct schema version, don’t run the /PrepareSchema command. If not set, run the /PrepareSchema command.
Remember to check if you need to run the /PrepareAD command. The PowerShell script and the table will also show you if you need to do that.
1. Check Exchange Schema version with PowerShell
2. Exchange schema versions (up to date list)
Ali, you said: “Remember to check if you need to run the /PrepareAD command.”
Question: PrepareAD or PrepareSchema?
Thanks
The /PrepareAD command.
The error referenced in the KB sounds scary
Cannot convert null to type” error and Exchange 2019 CU14 RecoverServer fails
The procedure calls for installing an entirely new exchange server with the same name, OS, etc!
Hi Ali,
When I run the Prepare AD Schema it runs in CU11 instead of CU14. Is this normal? I have downloaded Cumulative Update 14 for Exchange Server 2019 (KB5035606).
Hi Jason,
No, that’s not how it should be. This may be a cosmetic bug from your environment.
If it shows that Exchange Server CU14 is installed on the system, you are good. If not, rerun the setup using Command Prompt with administrator privileges.
i had the same issue Jason, running this line helped me a lot:
F:\Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataOff /PrepareAD
you must put the letter of your mounted ISO in the command. I don’t know why, but it worked for me.
Hi Ali,
We are still on CU11 currently, but SU version is FEB23. How can I resolve the CVE-2024-21410 vulnerability in our case?
Hi Tina,
1. Update to Exchange Server 2019 CU14 (2024H1).
2. Verify that Extended Protection is enabled
Everything is explained in the article Install Exchange Cumulative Update.
Hello ALi, when i run the setup, i have a error : [02/16/2024 16:56:30.0984] [1] Exception : Microsoft.Exchange.Management.Deployment.ScriptExecutionException: L’erreur suivante est survenue lors de l’ex..cution de “$error.Clear();
. “$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1”;
Enable-RpcOverTcpPortScaling;
Enable-ExtendedTcpPortRange -Role “ClientAccess” -RoleIsDatacenter $RoleIsDatacenter
and
” was run: “System.Management.Automation.ActionPreferenceStopException: L…ex..cution de la commande s…est arr..t..e, car la variable de pr..f..rence ….ErrorActionPreference…. ou le param..tre courant a la valeur Stop..: La cl.. de Registre n’existe pas .. l’emplacement sp..cifi…
I don’t see in your publication any regsitery key to create …..
Do you have information please ? or know a issue ?
Do the below:
1. Disable all antivirus/security software
2. Run the Exchange Server setup using Command Prompt as administrator (high privileges)
Hi Ali
I’m running Exch 2019 CU13. In update to CU14, I can run ‘upgrade’ parameter with /PrepareAD?
Like: D:\setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareAD
Thanks
Hi Diego,
No, it’s not possible.
I recommend going through the article Install Exchange Cumulative Update. Everything is explained step by step.
Does this cu14 require ad prep or not?
Yes, it requires.
You can find the Exchange Server schema versions in the table over here: Exchange schema versions.
Dear Ali,
an we upgrade the Exchange 2019 from CU12 to CU14 ? without upgrading to CU 13.
Thanks
Yes, you can update from Exchange Server 2019 CU12 directly to CU14.
Hi Ali,
Thank you for this valuable information.
How about for exchange server 2016? I see that no CU updates have been released yet.
Hi Karl,
There is no CU release for Exchange Server 2016.
What you’ll need to do is:
1. Check if Extended Protection is enabled
2. Enable Extended Protection if it’s not enabled
Follow the steps in the article Configure Extended Protection in Exchange Server.
Hi Ali,
would the EP being enabled during install of CU14 affect authorization through a load-balancer (e.g. Kemp)?
I upgraded Exchange Servers with a Kemp load balancer in place, and there are no issues. Of course, you should double-check everything, as every organization is set up differently.
Hi Ali,
Thank you for feedback.
Best Regards,
Atti
Hello Ali,
thank you for your courses, they are very useful.
I have a question about CU by Hybrid-Environments.
Do we need take any additional actions if we want to implement CUs on a Hybrid-Environment.
We do not have any Mailboxes on our local Exchange Server.
Thank you in advance for your answer.
Emre
Hi Emre,
No additional actions are required. Install the CU, and that’s it.