This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 26%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
The customer never did CU Update for SharePoint 2016. The version is 16.0.4327.1000 (release candidate). Can we install the latest CU directly ? or do we need to install feature pack 1 or 2 before installing the latest October 2020 Patch (16.0.5071.1001)
I'm not sure how you identified that the customer is running RC. Did the customer state so? Or did you just look at the build version reported in the Central Admin and returned from powershell?
RC and RTM return the same build version in these two scenarios. In most cases when people report that customers are running RC they look at the wrong places to identify if the customer is using RTM or RC.
From RTM the customer can directly go to the latest CU.
If the customer really installed an RC version the customer would have to uninstall and reinstall SharePoint with the RTM version.
Please have a look here about common mistakes regarding the build version of SharePoint.
https://blog.stefan-gossner.com/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
@stefan , thanks for the information.
I think i noted down configuration database version which is 16.0.4327.1000 (SharePoint 2016 Release Candidate)
SharePoint 2016 RTM version is 16.0.4351.1000 right ?
I will run (Get-SPFarm).BuildVersion command and confirm the build version.
If the customer is installed the RC version, is there any option to copy the existing data ? Because it is a production environment.
Hi Saijthgh,
the configuration database schema version is the same for RTM and RC
(Get-SPFarm).BuildVersion is the same for RTM and RC
you cannot use this info to differentiate RC and RTM.
Please check in "control panel" / "programs and features". Here you can see the actual version in the "Version" column.
Alternatively check in the central admin in the "Manage patch status" page. It will also show you the correct version information.
Cheers,
Stefan
The version shows as 16.0.4351.1000 (SharePoint 2016 RTM). There are 2 Web and 1 App SharePoint Servers in the farm and 1 stand alone database server.
Is it necessary to update the windows updates for all SharePoint Servers and DB Server(Windows Server 2012 R2) before the cumulative update ?
Can we directly update to January 2021 Patch (Language Independent Files) from SharePoint 2016 RTM or do we need to install Feature Pack 2 before that ?Also it has project server as well. Please find above the screenshots.
You can directly install the January 2021 Patch. But ensure to install as well the language independent and the language dependent patch!
Installing only the language independent patches can result in all type of problems as javascript files (included in language dependent patch) no longer match the binaries and because text strings required by the language independent binaries might be missing in the old language dependent files on your file system.
Thanks a lot for the information.
Is there any sequence for language independent and the language dependent patch installation ? Which one should we install first ?
Does the January 2021 Patch include Project Server 2016 as well ?
Sequence does not really matter - users usually install the language independent one first. Just don't forget to run the configuration wizard after both patches are installed.
Project server fixes are included.
Successfully installed the January 2021 patches in all servers. However, getting the following message for My Site Database. Database is up to date. But some sites are not completely upgraded.
My Site is customized a lot.
Also ran the below command
stsadm.exe -o localupgradestatus73383-upgradestatus.txt
[5] content database(s) encountered.
[0] content database(s) still need upgrade or cannot be upgraded.
[265] site collection(s) are contained in the content databases.
[0] site collection(s) still need upgrade.
[29] other objects encountered, [0] of them still need upgrade or cannot be upgraded.
The issue is automatically got resolved. No Idea how ?
yes, you can directly install the latest PU. This public update delivers Feature Pack 2 for SharePoint Server 2016.
https://www.microsoft.com/en-us/download/details.aspx?id=102255
Thanks & Regards,
Hi, @SGH ,
Just like sharatha said, for SharePoint 2016, you can directly deploy the latest update. The feature packs will be included.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Upgrading from the RC to RTM or any post-patch is not supported. You need to build a new farm and perform a content migration (database attach upgrade is not supported in this scenario).