5

Yes you are right, the build number for April 2017 CU is 15.0.4919.1003 But I advise you to don't trust the build number in Manage Servers in Farm, it often gives you a wrong indication about installed fixes. Stefan Goßner discussed the reason in details at SharePoint patching demystified I quoted some One reason might be that you looked at the KB ...


3

Here is very good explanation about the issue you mentioned. when looking at the SharePoint foundation KB article there are rare cases that the patch level listed in the central administration is lower than the version number in the KB article. The reason for this is that different fixes are added to the CU at different times. Some fixes modify ...


3

Did you look at the build-number in CA -> System Settings -> Manage Servers in this farm -> Configuration Database Version. Unfortunately the Config-DB build number does not always match the build of a (cumulative) update. The best ressource to check success of your installation is CA -> Upgrade and Migration -> View product and patch installation status. ...


3

In some exceptional cases, the CU does not update the configuration database version in Central Administration like Oct CU 2013. And in this case, you can get the configuration database version from SQL Server by opening Content Database > the versions table. Check the version number with versionID 00000000-0000-0000-0000-000000000000. Or by checking ...


2

build number is not supposed to be change after every cu. because every cu is not upgrading the schema of configuration database. check from central admin> upgrade and migration > patch status,on this page if the kb for August cu is listed that's mean it is installed. you can also check from add remove program from the server and then under sharepoint check ...


2

Stefan Goßner has a great blog post on this - SharePoint does not have a build version. Full Stop. I think it is worth noting that you can gauge what patch level you're at, but each component in SharePoint has it's own build number, which can influence the farm build number. For your image, the KB number is the knowledge base article for the specific patch....


2

found an article here. "What may seem obvious is actually more difficult to determine than you’d expect. Finding your version will depend on what operating system SharePoint is installed on and what build you are running, plus they all store the version information in separate places." I checked my SharePoint 2013 for Administrators Offical Book. There ...


1

"The only component directly accessing the configuration database is the SharePoint foundation component" But as you know their is no SharePoint foundation patch released in the October 2018 for SharePoint Server 2010. So in this case configuration database version will not change and remain same. Read the below article, which explain int he detail. Common ...


1

Both build numbers 15.0.4569.1000 & 15.0.4571.1502 refers to your farm has been patched to Service Pack 1. you can check the corresponding release for the build numbers at SP Build Number Regarding The first number 15.0.4569.1000 is Service Pack 1 (replaced) that released on 2014 February 25. Regarding The second number 15.0.4571.1502 is Service Pack 1 ...


1

Download SharePoint Server CU from Microsoft together with the .cab files. Copy them on all Servers in your farm and execute the .exe. After the Installation is finished on all Servers, start the “SharePoint Products Configuration Wizard” on every Servers. (Do this step one Server after the other!) You should now see the the build number in SharePoint. ...


Only top voted, non community-wiki answers of a minimum length are eligible