September 2023 CU for SharePoint Server 2019 is available for download

September 2023 CU for SharePoint Server 2019 is available for download:

The KB article for September 2023 CU will be available at the following Location in a couple of hours:

• KB 5002472 – September 2023 Update for SharePoint Server 2019 (language independent)
  This is also a security update!
• KB 5002471 – September 2023 Update for SharePoint Server 2019 (language dependent)

The downloads for September 2023 CU are available through the following links:

• Download September 2023 Update for SharePoint Server 2019 (language independent)
  This is also a security update!
• Download September 2023 Update for SharePoint Server 2019 (language dependent)

SharePoint 2019 September 2023 CU Build Number:

Language independent fix: 16.0.10402.20016
Language independent fix: 16.0.10402.20016

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

March 2023 CU for SharePoint Server 2016:

The product group released the March 2023 Cumulative Update for SharePoint Server 2016 product family.

This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.

The KB articles for March 2023 CU should be available at the following locations in a couple of hours:

• KB 5002368 – March 2023 Update for SharePoint Server 2016 (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 5002325 from February 2023 CU.

The downloads for March 2023 CU are available through the following links:

• Download March 2023 Update for SharePoint Server 2016 (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 5002325 from February 2023 CU.

SharePoint 2016 March 2023 CU Build Numbers:

Language independent fix: 16.0.5387.1000

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

March 2023 CU for SharePoint Server 2019

March 2023 CU for SharePoint Server 2019 :

The product group released the March 2023 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 March 2023 CU will be available at the following Location in a couple of hours:

• KB 5002358 – March 2023 Update for SharePoint Server 2019 (language independent)
  This is also a security update!
• KB 5002357 – March 2023 Update for SharePoint Server 2019 (language dependent)

The downloads for March 2023 CU are available through the following links:

• Download March 2023 Update for SharePoint Server 2019 (language independent)
  This is also a security update!
• Download March 2023 Update for SharePoint Server 2019 (language dependent)

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 March 2023 CU Build Number:

Language independent fix: 16.0.10396.20000
Language dependent fix: 16.0.10396.20000

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Cumulative update for SharePoint Enterprise Server 2013

February 14, 2023, cumulative update for SharePoint Enterprise Server 2013 (KB5002346)

Note: This is build 15.0.5529.1000 of the cumulative update package.

We recommend that you test those hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new release contains all the hotfixes and security updates that were included with the previous Microsoft SharePoint Enterprise Server 2013 update package releases.

Important notes about the cumulative update package

• The Microsoft Office 2013 hotfixes are now multilingual. This cumulative update package contains updates for all languages.

• This cumulative update package includes all the server component packages. Additionally, this cumulative update package updates only those components that are installed on the system.

Improvements and fixes in this cumulative update

This cumulative update package fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• Description of the security update for SharePoint Enterprise Server 2013: February 14, 2023 (KB5002312)

• Description of the security update for SharePoint Foundation 2013: February 14, 2023 (KB5002347)

How to download and install the update:

This update is available only for manual download and installation from the Microsoft Download Center.

• Download cumulative update 5002346 for SharePoint Enterprise Server 2013

Note: Three files are available in this update: one .exe file and two .cab files. In order for the installation to work correctly, you must download all three files.

Virus-scan claim

Microsoft scanned this file for viruses by using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

Cumulative update package information:

Hotfixes that are included in this cumulative update package

This cumulative update package contains all the .msp files that we released as hotfixes or as public updates that target SharePoint Server 2013. This update package also targets SharePoint Foundation 2013. Therefore, you don't have to install those packages separately.

Prerequisites:

To apply this cumulative update, you must have Microsoft SharePoint Server 2013 Service Pack 1 (SP1) installed.

Restart requirement:

You may have to restart the computer after you apply this cumulative update.

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

How to set sharepoint site to read only

How to set sharepoint site to read only?

 set sharepoint site to read only is required while doing the Migration from On-premise to online.

The steps are same for all: 2010, 2013 and 2016.  

We can achieve this in  3 options as shown below.

Through Central Administration:

1. Go to Central Admin > Application Management > Configure quotas and locks.
2. Select the site collection which should be read-only and select the “Read-Only” radio button. Click OK.
3. Now, browse the site collection and we can see a message on the top saying, “This site is read-only at the farm administrator’s request”.
4. when the site is set to read-only,user can only view the document or download a copy of it.
   

Through Database:

1. Select the content database and go to its Properties.
2. Click on Options menu from the left-hand side of the window and under the "State" section, set “Database Read-Only” to “True”, as shown in the image below.
3. Now, the content database is in read-only mode.

Through PowerShell:

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.