logo-sharepoint-4 logo-sharepoint-2logo-sharepoint-3

Jones Professional Services is a Microsoft Certified Partner delivering SharePoint / Project Server 2016, Enterprise Project Management solutions and now the release of SharePoint Server 2016.

SharePoint 2016 Requirements

Hardware/Software requirements for SharePoint Server 2016

Server Operating System:

Windows Server 2012 R2

Database Server:

SQL Server 2014

SQL Server 2014 Analysis Services must also be installed if you are using the Cube Building Service in Project Server 2016.

Supported browsers:

Microsoft Edge

Microsoft Internet Explorer 11

Microsoft Internet Explorer 10

Google Chrome (latest released version)

Mozilla Firefox (latest released version plus immediate previous version)

Apple Safari (latest released version)

Project client compatibility

You can connect to Project Server 2016 with not only the Project Professional 2016 client and Project Pro in Office 365, but also with Project Professional 2013.

Just be mindful that the 2013 version will not allow for 2016 features in Project Server 2016.

Compatible with

Project Professional 2016

Project Pro in Office 365

Project Professional 2013

Upgrading to Project Server 2016 

When planning to upgrade to Project Server 2016 take note of the following:

  • Upgrade only through Project Server 2013 - If you are upgrading from earlier versions of Project Server, you must upgrade your databases to Project Server 2013 first in order to upgrade to Project Server 2016. There is no direct upgrade path from Project Server 2010 to Project Server 2016.
  • Project Web App site collection upgrade - The SharePoint 2013 content database that contains your PWA site collection needs to be upgraded as well during the upgrade process.
  • No in-place upgrade – You must first create a Project Server 2016, and then attach and upgrade your Project Server 2013 databases to the new farm. In-place upgrade is not supported.
  • Upgrade through SharePoint PowerShell - Similar to the Project Server 2013 upgrade experience, upgrading to Project Server 2016 Release Candidate will be through the use of SharePoint PowerShell cmdlets.
  • Migrate your Project Server 2013 Resource Plans - You can migrate your Project Server 2013 Resource Plans to use as Resource Engagements in Project Server 2016 Release Candidate as an optional part of the upgrade process. Resource Plans are not supported in Project Server 2016.

A single database for multiple instances

In Project Server 2013, a separate Project database is created for each Project Web App instance. In Project Server 2016 , a single database (the SharePoint content database) will be used for all instances of PWA. Even though all data is saved to the single database, data from each individual instance is still isolated from other instances.

Having your Project data contained within a single database makes for easier database operations, such as backup and restore, migration, etc.

Custom field limits

To help provide the best performance in Project Server 2016 reporting, there are limits to how many single-value custom fields, or each type, that get stored in the reporting schema:

Project custom fields

Timesheet custom fields

Task and Resource custom fields, combined

450 text fields

450 text fields

450 text fields

450 lookup tables

450 lookup tables

450 lookup tables

450 of all other custom field types (cost, date, duration, number, flag)

450 of all other custom field types (cost, date, duration, number, flag)

450 of all other custom field types (cost, date, duration, number, flag)


02/28/2016 - 1:43pm