Shulou(Shulou.com)06/01 Report--

From an IT Pro perspective, Project 2016 has the following new features:

Resource booking

Resource booking is a new feature in Project Server 2016 that helps project and resource managers agree on the specific workload and working hours of specific resources associated with the project. Resource bookings are developed from legacy functional resource plans in Project Web App, and as an optional step in the upgrade process, all existing resource plan data can be converted into resource subscriptions.

Resource bookings provide the following features:

Project managers can use the new resource plan view in Project Professional 2016 to make resource requests.

Resource managers can view all resource requests through the new Resource requests page and can use the capacity planning heat map to learn about the availability of resources.

IT professionals need to know how to migrate Project Server 2013 resource plans to resource bookings in Project Server 2016. To do this, run SharePoint PowerShell cmdlet in the upgrade process.

One-time installation-Project Server and SharePoint Server

One of the biggest changes in Project Server 2016 is the installation process. The new Project Server 2016 runs as a service application in SharePoint Server 2016 Enterprise. Because the SharePoint Server 2016 Enterprise MSI file also contains the installation files for Project Server 2016, you no longer need to install separately like the previous version of Project Server. An activation key is required to activate Project Server 2016.

Basic installation languages and language packs

Because Project Server 2013 and SharePoint Server 2013 are installed separately, it is sometimes necessary to consider the basic installation language and language packs to provide multilingual support for users. For example, you can install both Project Server 2013 (US English) and SharePoint Server 2013 (US English), and then add the Project Server 2013 (French) language pack in scenarios where you need to provide users with US English and French Project Web App interfaces. New Project Server 2016 and SharePoint Server 2016 can now be installed through an one-time installation, and the system automatically matches their base languages. For example, when installing SharePoint Server 2016 (US English), the basic installation language for Project Server 2016 and SharePoint Server 2016 will be US English.

Upgrade to Project Server 2016

When planning to upgrade to Project Server 2016, you need to be aware of the following:

You can only upgrade through Project Server 2013-to upgrade from an older version of Project Server, you must upgrade the database to Project Server 2013 before upgrading to Project Server 2016. There is no direct path to upgrade from Project Server 2010 to Project Server 2016.

Project Web App site Collection upgrade-you also need to upgrade the SharePoint 2013 content database that contains PWA site collections during the upgrade process.

In-place upgrades are not supported-you must first create Project Server 2016, and then attach and upgrade the Project Server 2013 database to the new farm. In-place upgrade is not supported.

Upgrade through SharePoint PowerShell-similar to the Project Server 2013 upgrade experience, upgrade to Project Server 2016 by using SharePoint PowerShell cmdlet.

Migrate Project Server 2013 resource plans-as an optional step in the upgrade process, you can migrate Project Server 2013 resource plans to resource bookings in Project Server 2016. Resource planning is not supported in Project Server 2016.

One database for multiple instances

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

Saving Project data in a database can simplify database operations, such as backup and restore, migration, etc.

Custom field limit

To help achieve the best performance of Project Server 2016 reports, there are limits on the number of single-valued custom fields (or fields of each type) that are stored in the report schema:

Project Custom Field

Schedule Custom Field

Custom field combinations of tasks and resources

450 text field

450 text field

450 text field

450 lookup tables

450 lookup tables

450 lookup tables

450 custom fields of all other types (cost, date, duration, number, tag)

450 custom fields of all other types (cost, date, duration, number, tag)

450 custom fields of all other types (cost, date, duration, number, tag)

Project Web App change

Administrators should be aware of several major changes in Project Web App that affect users:

New calendar options

In Project Server 2016, note that there are some changes in the way Project Web App calendars are used. The details include:

New featur

Multiple calendars-you can have multiple calendars. You can add additional calendars through the project center or the schedule page.

Adjust the calendar date range-you can now adjust the start and end dates of the calendar.

Simplified the way the project was created

In Project Server 2016, you can easily create a new project through the "get started with Project Web App" window displayed on the Project Web App home page. Selecting create or Import Project launches the create New Project wizard, which guides the user through the necessary steps.

For more information, see: https://technet.microsoft.com/en-us/library/ff631142(v=office.16)

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.