Today we are re-releasing the November 2024 SUs for Exchange Server. The original release of these SUs (released on 11/12/2024) introduced an issue with Exchange Server transport rules stopping after a certain amount of time in some environments. The re-released SUs resolve this issue.
To help you understand how to move forward, in this post we use the following naming convention to distinguish between the original November 2024 SU and the re-release:
- Nov 2024 SUv1: original November 2024 SU (released on 11/12/2024 with article KB5044062)
- Nov 2024 SUv2: re-released November 2024 SU (released on 11/27/2024 with article KB5049233)
The following table describes the actions you need to take based on your environment:
|
If Nov 2024 SUv1… |
Then… |
|
was installed manually and you do not use any transport or DLP rules OR was installed manually and you had a problem with rules stopping but used some sort of workaround to keep the rules running |
it is recommended to install the Nov 2024 SUv2 to gain more granular control over the X-MS-Exchange-P2FromRegexMatch header. Please see the FAQ below. |
|
was installed using Microsoft / Windows update and you do not use any transport or DLP rules, |
download and install the Nov 2024 SUv2 (it will not be released on Microsoft / Windows update for automatic installation). |
|
was installed (manually or automatically) and then uninstalled to fix the issue with transport rules, |
install the re-released Nov 2024 SUv2. |
|
was never installed, |
install the re-released Nov 2024 SUv2. |
Download links are updated in the November 2024 SU announcement blog post.
For any additional actions you might need to take after installing the Nov 2024 SUv2, please see the original release blog post. You should always run Exchange Health Checker to see if any additional steps might be needed.
An issue reported during installation in January 2025
Over the last week, we have heard a number of customers with the following problem; please review this KB article if you have an error installing a November SU:
File version error when you try to install Exchange Server November 2024 SU
FAQs
We installed the original Nov 2024 SUv1 manually and had no problems. Do we need to install the Nov 2024 SUv2?
Yes. We recommend installing the Nov 2024 SUv2. Please see below for more details.
We installed the Nov 2024 SUv1 through Microsoft / Windows Update and had no problems. Will our server install the Nov 2024 SUv2 automatically?
No. Please see the Are Nov 2024 SUv2 packages going to be released on Windows / Microsoft update? question below.
What are the differences between the Nov 2024 SUv1 and Nov 2024 SUv2 packages?
The Nov 2024 SUv2 package resolves the transport rules issue introduced in the Nov 2024 SUv1 package. It also adds more granular control for “Non-RFC compliant P2 FROM header detection.” More details can be found here.
Are Nov 2024 SUv2 packages going to be released on Windows / Microsoft update?
Because of the known issues after the installation (please see this KB article) we have decided not to release the updates on Windows / Microsoft update. While we have not seen many customers have this issue, the fact that the solution to the issue requires manual intervention means that we want our customers to deliberately install Nov 2024 SU packages.
Due to how we install updates, we need the update in the .msp format and not the .exe format. How can we get the .msp if the update is not published to Windows Update Catalog?
Extract the .msp by doing the following: download the .exe package you need to a workstation that does not have Exchange installed and double-click on it. The update will fail to install and display an error message, but a command line window will display where the package was extracted (usually a temporary folder). Copy the .msp file from the temporary folder before dismissing the error message (dismissing the error removes the files from the temporary folder).
The original Nov 2024 SU blog post, applicable CVEs, and our recommended actions post-installation still apply.
The Exchange Server Team
