Install and Configure Project Server 2016

One of the biggest changes in Project Server 2016 is the installation process. So before you get started to Install and configure Project Server 2016 , you should be aware of:

  • A separate installation is no longer required as it was in previous versions of Project Server.
  • The SharePoint Server 2016 MSI file will contain the installation files for Project Server 2016 as well.
  • Project Server 2016 runs as a service application in SharePoint Server 2016.
  • Project Server 2016 is only available on SharePoint Server 2016 Enterprise.

Note: Although Project Server 2016 is included as part of the SharePoint Server 2016 Enterprise installation, but it is still require a separate license.

Below I’ll elaborate

How to Install and Configure Project Server 2016 under SharePoint 2016?

Steps:

  1. Create SharePoint and Project Server Service Account.
  2. Install & configure SharePoint 2016.
  3. Register Managed Account.
  4. Configure Project Server 2016 Service.
  5. Deploy Project Web App.
Create SharePoint and Project Server Service Account.

First, you should create the following service accounts in Active Directory.

  • SPAdmin is the installation account that used to install and run SharePoint Configuration wizard.
    • it should be added to local administrator group on each server on which Setup is run.
    • Member of the Server Admin SQL Server security role.
  • SPFarm is the farm account that used to configure the farm.
    • it must have a server role as DBcretor and security admin in SQL Server.
    • db_owner fixed database role for all databases in the server farm
  • PSWebAppPool is a domain user that used to run the application pool for the web application that will host the PWA site collection.
  • PSSrvAppPool is a domain user that used to run the associated application pool with Project server service application.
Install & configure SharePoint 2016.

Minimum requirements for the database server in the farm is  The 64-bit edition of Microsoft SQL Server 2014 Service Pack 1 (SP1).

Minimum requirements for Operating System is Windows Server 2012 R2 Standard or Datacenter or Windows Server 2016 Standard or Datacenter

  • Run the Microsoft SharePoint Products Preparation Tool.
  • Run the SharePoint installation file.
  • Provide the SharePoint Key, and follow the steps as shown below.
    • Enterprise trial product key: NQGJR-63HC8-XCRQH-MYVCH-3J3QR

install-sharepoint-and-project-server-2016-_1

install-sharepoint-and-project-server-2016-_2

install-sharepoint-and-project-server-2016-_3

install-sharepoint-and-project-server-2016-_4

install-sharepoint-and-project-server-2016-_5

install-sharepoint-and-project-server-2016-_6

install-sharepoint-and-project-server-2016-_7

install-sharepoint-and-project-server-2016-_8

install-sharepoint-and-project-server-2016-_9

install-sharepoint-and-project-server-2016-_10

install-sharepoint-and-project-server-2016-_11

install-sharepoint-and-project-server-2016-_12

install-sharepoint-and-project-server-2016-_13

install-sharepoint-and-project-server-2016-_14

install-sharepoint-and-project-server-2016-_15

install-sharepoint-and-project-server-2016-_16

Once the installation is finished, the Central Administration will be opened, Click on cancel to configure the farm manually.farm-wizard

Register Managed Account.
  1. On the Central Administration home page, in the left navigation, click Security.
  2. On the Security page, in the General Security section, click Configure managed accounts.managed-account
  3. On the Managed Accounts page, click Register Managed Account.register-managed-account
  4. Type the user name and password of the service account and leave the Automatic Password Change settings as default.
  5. Click OK.register-managed-account-_1
  6. Repeat the above steps for all service accounts.

All the above steps are related to SharePoint 2016 installation and configuration, in the next section, I will show How to configure Project Server 2016?

Enable Project Server 2016 License.
  • Open the SharePoint 2016 Management Shell as Administrator.
  • Type the below cmdlet to enable Project Server 2016:
Enable-ProjectServerLicense -Key

Project Server trial license key: Y2WC2-K7NFX-KWCVC-T4Q8P-4RG9W

enable-projectserverlicense

Creating a Project Server service application.
  1. On the Central Administration home page, in the Application Management section, click Manage service applications.
  2. On the Manage Service Applications page, on the ribbon, click New, and then click Project Server Service Application.create-a-project-server-service-application
  3. Provide the name, and select the service account that will run this service as shown below.(In this case, it’s PSSrvAppPool).

create-a-project-server-service-application-_1

In Project Server 2013, to be able to create the Project Server Application Service, you needed to start the Project Server Application Service manually as a prerequisite.

In Project Server 2016, the Project Server Application Service will be started automatically once the project server service application is created, you could note that in the Central Administration > System Setting > Services On Server.services-on-server-sharepoint-2016

Create a web Application for PWA.
  • On the SharePoint Central Administration > in the Application Management > Web Application > Manage Web application.
  • From the above ribbon > Select New > Provide the required information and select PSWebAppPool as application pool account.

create-a-web-application

  • Once you have created the web application > Click Create Site Collection to create the top level website.

Note: Project Server 2016 does not require a specific template. You can choose one appropriate for your organization.

Create a PWA Content Database.
  • On the SharePoint Central Administration > in the Application Management > DataBases > Manage Content Databases.
  • Click on Add A content Database.
  • Create a new Content Database for PWA “WSS_Content_PWA”

Note: In Project Server 2016, A single database (SharePoint Content Database) holds the project data and the content to facilitate the database operations, such as backup and restore, migration, etc. read more at Project Server 2016: New and deprecated features compared to Project Server 2013.

Lock Down PWA Content Database to prevent any new site collections being added except  PWA site.

The final result should look like the following:

content-database-lockdown

Note: before going to the next step “Provisioning the PWA Instance” if you don’t want to use the “Sites” Wildcard Inclusion URL “http://epm/sites/PWA” to be like this “http://epm/PWA” as was in Project Server 2013, you would be better off creating a Managed Path called “PWA” of type Explicit Inclusion as the following:

  • Open SharePoint Central Administration and go to Application Management -> Web Applications -> Manage Web Applications.
  • Click on the Managed Paths Icon on the Web Application Ribbon and then create new path called PWA of Type “Explicit Inclusion”
  • Once this is done, you can provision your PWA App on the “http://epm/PWA” instead of using the “http://epm/sites/PWA” URL.

By the way, creating the PWA site Collection on http://epm/sites/PWA is OK for most implementations, but if you don’t want to use the out of the box “Sites” Wildcard Inclusion option, you should create Explicit Inclusion as I mentioned above. (Special Thanks for viarcini@microsoft.com)

Create and provision PWA Instance.

In Project Server 2013, you can create and provision PWA instance by managing Project Server Service application as shown below.

pwa-2013

Contrary to what was happening in the Project Server 2013: In Project Server 2016 you can’t provision PWA instance via Central Administration.

provison-project-server-2016-pwa-instance

In this case, The PWA instance should be provisioned via PowerShell cmdlets as mentioned below:

  • Open the SharePoint 2016 Management Shell as Administrator.
  • Type the following to create PWA instance in Project Server 2016:
New-SPSite -ContentDatabase PWA_Content -URL http://epm/sites/PWA -Template pwa#0
  • Then Enable ‘pwasite’ feature.
Enable-SPFeature pwasite -URL http://contoso-appsrv1/sites/PWA

enable-spfeature-pwasite

You can now access the new Project Web App site.

pwa-in-project-server-2016

Like Project Server 2013, the Project Server 2016by default has the SharePoint Permission mode, To switch from SharePoint Mode to Project Server Mode, follow the mentioned steps at SharePoint Permission Mode Vs Project Server Permission Mode in Project Server 

Download

Project Server 2016 Configurator Script

See also

Enjoy 🙂

Advertisements

17 thoughts on “Install and Configure Project Server 2016

  1. Hi Guys. How do I set up project server roles in 2016. I am stumped. In 2010 the roles were accessible from the admin area. I.e. Project Manager role was selected and all the PM rights per their role were stamped down onto the new resource in the Resource Module.
    Same for Team Lead, Team Member and Executive. In 2016 I do not see this. Any ideas?

    Like

  2. Hi, awesome Post thanks.
    Unfortunately I always get an error at the final step “Enable-SPFeature”
    Error Message Post provision setup failed. CreateBuiltInLookupTableAndCustomFields failed
    Any idea where I have done a wrong configuration?
    Regards, Markus

    Like

  3. I really liked your post. To the point and well illustrated.
    One comment though. I think you are missing an optional step right before provisioning the site, and right after creating the PWA Content Database.
    You are creating the PWA site Collection on http://epm/sites/PWA, and this is OK for most implementations, but if you don’t want to use the “Sites” wildcard Inclusion URL, you would be better off creating a Managed Path called PWA of type Explicit Inclusion.
    To do this, just open SharePoint Central Administration and go to Application Management -> Web Applications -> Manage Web Applications.
    Make sure you have the Web Application you created on the step “Create a web Application for PWA”
    Click on the Managed Paths Icon on the Web Application Ribbon and then create new path called PWA of Type “Explicit Inclusion”
    Once this is done, you can provision your PWA App on the “http://epm/PWA” instead of using the “http://epm/sites/PWA” URL.
    Again, this is not necessary, but if you don’t want to use the out of the box “Sites” Wildcard Inclusion option, you should do this.

    Thanks again for a great article. Keep up the good work!

    Liked by 1 person

    1. @Virgil Arciniegas Thank you very much for your valuable comment that made me happy and proud :).
      By the way, I’ve updated my article with your important note. Thanks again for your precious feedback.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s