The product group released the November 2024 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix.
The KB article for November 2024 CU will be available at the following Location in a couple of hours:
- KB 5002650 – November 2024 Update for SharePoint Server 2019 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002597 from August 2024 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
The downloads for November 2024 CU are available through the following links:
- Download November 2024 Update for SharePoint Server 2019 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002597 from August 2024 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2019 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
SharePoint 2019 November 2024 CU Build Number:
Language independent fix: 16.0.10416.20000
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2019
- Blog: SharePoint Patching Best Practices
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified (applies also to SharePoint Server 2019)
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
Hi,
We have a big problem with our farm the timer job “worklow” is gone, if we update our farm to last version is there a chance that this workflow will be created back in the process ? We currently have april 2024 CU.
Thank you for your help
Permalink
Hi Larry,
I would try the following:
$farm = Get-SPFarm
$farm.TimerService.EnsureDefaultJobs()
Then run the command below for specific web application:
$w = Get-SPWebApplication http://sp
$w.EnsureDefaultJobs()
Cheers,
Stefan
Permalink
Hi Stefan,
I already tried with no luck,
the following command return nothing
Get-SPTimerJob | ? { $_.Name -eq “job-workflow” }
Permalink
Hi Stefan,
I try this without success, is there a way to create it back with code by referencing the dll ?
Thanks for your help
Permalink
Hi Larry,
it might be possible but this requires some research to be done.
Please open a support case with Microsoft if you need assistance with this.
Cheers,
Stefan
Permalink
Hi Stefan – I ran all the CU’s on my servers, ran upgrade db status powershell, and then psconfigui.exe. The PSConfig ran successfully. I checked the status of the servers in “Manage Servers” in Central Admin and despite my running a successful CU install and PSConfig, I still get “Upgrade Required” as the status. Please let me know what we can do and if you are aware of the issue.
Permalink
Hi Raghav,
please run test-spcontentdatabase against the databases on the server where you see the problem.
It looks as if some upgrade operations did not succeed.
test-spcontentdatabase should help to identify the culprit.
Cheers,
Stefan
Permalink
Hi Stefan,
Do you know if there is a trending issue after NOV24 CU?
This location X:\Program Files\Microsoft Office Servers\16.0\Data\Office Server\Applications\Search\Nodes\B12BEF\IndexComponent2\storage\data\GUID\Journal is getting full with files “backupsection_583154_583158.@meta”.
What are those? Can be deleted?
Permalink
Hi Stefan,
Do you know if there are any issues with the HTTPs redirect after deploying the November 2024 for SharePoint 2019?
Prior to the patch when a user would type our internal intranet sites url without the https on their mobile devices Edge browser, it would automatically redirect to the https address. That is not happening now, the user has to make sure they include the https when going to the site.
Permalink
Hi Joyce,
a HTTPs redirect from HTTP? Thats not part of the feature set of SharePoint Server 2019.
Maybe you configured it in IIS (e.g. using steps provided here: https://blogit.create.pt/miguelisidoro/2021/08/11/how-to-configure-https-with-http-redirect-in-sharepoint-2019-using-host-named-site-collections/) or you installed a 3rd party solution to perform this?
Cheers,
Stefan