Monday, October 23, 2017

SharePoint 2016: Build Numbers

Finding your Build Number

To find the build version of the SharePoint farm using Windows PowerShell:

1. Open the SharePoint Management Shell

2. Type the following command:

(Get-SPFarm).BuildVersion

Build Number Table:

Please see the table below:
Schema VersionBuild NumberSchema ChangeLPsReleased MonthCompon ent KBDownload LinkIssue Fixed
16.0.4327.100016.0.4351.1000N/A NoRTMSP 16RTM 
16.0.4327.100016.0. 4366. 1000No NoApril 2016 CU SP 16KB 2920721April 2016 CULink
16.0.4378.100016.0.4378.1000Yes NoMay 2016 CUSP & Proj 16KB 3115088   May 2016 CULink
16.0.4378.100016.0.4378.1000Yes YesMay 2016 CUSP & Proj 16KB 2920690 May 2016 Cu  +LPsee above link
16.0.4393.100016.0.4393.1000YesNoJune 2016 CUSP & Proj 16 KB 3115181June 2016 CU  Link 
16.0.4393.1000 16.0.4393.1000 Yes  YesJune 2016 CU SP & Proj 16 KB 3115184June 2016 CU+LP Link
16.0.4405.100016.0.4405.1000Yes NoJuly 2016 CuSP & Proj 16Kb 3115299   July 2016 CU
16.0.4405.100016.0.4405.1000Yes Yes July 2016 Cu SP & Proj 16 Kb 3115304 July 2016 CU +LP   
16.0.4417.100016.0.4417.1000YesNoAug 2016 CUSP & Proj 16KB 3115437   Aug 2016 CU  Link
16.0.4417.100016.0.4417.1000YesYesAug 2016 CUSp & Proj 16KB 3115441Aug 2016 CU & Lp Link
16.0.4432.1003YesYesSep 2016 CUSP & Proj 16Kb 3118295 Sep 2016 CU +LP
16.0.4432.1003 YesNoSep 2016 CUSP & Proj 16 Kb 3118289Sep 2016 CU
16.0.4444.100416.0.4444.1000 Yes NoOct 2016 CUSP & Proj 16Kb 3118372 Oct 2016 CU 
16.0.4444.100016.0.4444.1000 YesYesOct 2016 CUSP & Proj 16 Kb 3118376 Oct 2016 CU +LP 
16.0.4456.100216.0.4456.1000  YesNo Nov 2016 CUSP & Proj 16Kb 3127940 Nov 2016 CU
16.0.4456.100216.0.4456.1000  YesYesNov 2016 CU SP & Proj 16Kb 3127942 Nov 2016 CU +LP  
16.0.4471.100016.0.4471.1000YesNo Dec 2016 CUSP & Proj 16Kb 3128014 Dec 2016 CU
16.0.4471.1000 16.0.4471.1000YesYesDec 2016 CUSp & Proj 16 Kb 3128017 Dec 2016 CU + LP 
16.0.4483.100116.0.4483.1001YesNo Jan 2017 CUSP & Proj 16Kb 3141486 Jan 2017 CU 
16.0.4483.100116.0.4483.1001YesYesJan 2017 CUSP & Proj 16Kb 3141487 Jan 2017 CU + LP 
 16.0.4498.100216.0.4498.1002 YesNo Feb 2017 CUSP & Proj 16Kb 3141515 Feb 2017 CU 
 16.0.4498.100216.0.4498.1002 YesYes Feb 2017 CUSP & Proj 16Kb 3141517 Feb 2017 CU + LP 
 16.0.4510.100116.0.4510.1001 YesNoMarch 2017 CUSP & Proj 16Kb 3178672  March 2017 CU  
16.0.4510.100116.0.4510.1001YesYesMarch 2017 CUSP & Proj 16Kb 3178675  March 2017 CU + LP  
16.0.4522.100016.0.4522.1000 YesNo April 2017 CUSP & Proj 16Kb 3178718  April 2017 CU  
16.0.4522.100016.0.4522.1000 YesYesApril 2017 CUSP & Proj 16Kb 3178721 April 2017 CU + LP  
16.0.4534.100016.0.4534.1000YesNoMay 2017 CUSP & Proj 16Kb 3191880  May 2017 CU  
16.0.4534.100016.0.4534.1000YesYesMay 2017 CUSP & Proj 16Kb 3191884  May 2017 CU + LP  
16.0.4549.100116.0.4549.1001 Yes No June CU 2017SP & Proj 16KB 3203432June 2017 CU 
16.0.4549.100016.0.4549.1000  YesYes June CU 2017SP & Proj 16 Kb 3203433June 2017 CU +LP   
​16.0.4561.100016.0.4561.1000Yes No July CU 2017SP & Proj 16Kb 3213544July 2017 CU 
16.0.4561.100016.0.4561.1000YesYesJuly CU 2017SP & Proj 16Kb 3213543July 2017 CU & LP 

Please read below for further explanation of each column:
  • Schema Version: This version number you will see from central admin (home page or going to Central admin > System Settings > Manager Server in Farm) or you can get the same from PowerShell as well: (Get-SPFarm).BuildVersion
  • Build Number: Now onwards, MSFT is not changing the schema version with every CU as they change the practice so this number represents the patch level you are. You can get by going Central Admin > Upgrade and Migration > Check Product and patch Installation Status.
  • Schema Change: This column will tell if Schema was changed or not for a specific CU
  • LPs: This column will tell if they included the Language Pack fix or not.
  • Release: This Column will tell the release month of the CU
  • Component: What SharePoint or Project component this CU is for. Most probably it will be SharePoint 2016.
  • KB: Link to MSFT KB Articles
  • Download Link: Download link for the CU
  • Issue Fixed: This will list all the issues fixed in this CU.

Thursday, May 11, 2017

Factors affecting performance and capacity in Project Server 2013

Entity Description/Notes Small Medium Large
Projects   20 100 5000
Project Sites   20 100 5000
% Projects in Managed Mode   0% 10% 80%
Tasks   1250 25000 1250000
Average Tasks Per Project   62.5 250 250
Task Transaction History The number of times status tends to be submitted and approved for any given task 10 10 100
Assignments   1625 32500 1625000
Average Assignments Per Task   1.3 1.3 1.3
Average Tasks per My Site User   50 250 5000
Approvals Pending updates per manager 5 50 600
Resources   50 1000 10000
Average Resources Per Project   2.5 10 20
Average Assignments Per Resource   32.5 32.5 162.5
Users   50 1000 10000
Calendars   3 26 100
Issues   20 400 20000
Risks   20 400 20000
Deliverables   20 800 40000
Enterprise Project Types     5 50
Workflows     2 30
Average Projects Per Workflow     50 167
Phases     5 50
Phases Per Enterprise Project Type     20 20
Stages     15 150
Stages Per Workflow     20 40
PDPs     10 100
Custom Fields Per PDP     10 10
Number of Departments       100
Average Projects Per Department       50
Average Resources Per Department       100
Timesheets Per Year The more you utilize timesheets, the more resource demands will be placed on SQL Server. 2600 52000 780000
Status Reports Per Year     26000 260000

Users cannot see the checked out files in the folder/ library

I Came across a Issue today wherein the user opened a ticket for the below issue Issue : Users cannot see the checked out files in the fo...