Project Server 2010 Installation Guide: Microsoft Corporation
Project Server 2010 Installation Guide: Microsoft Corporation
Project Server 2010 Installation Guide: Microsoft Corporation
KB979917 - QFE for Sharepoint issues - Perf Counter fix & User Impersonation
(http://go.microsoft.com/fwlink/?LinkId=192577)
For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
Deploying Microsoft Project Server 2010 requires that you have certain Active Directory users
and groups available. The deployment instructions assume that the necessary groups already
exist. If you have not yet created the necessary users and groups, do so now before deploying
Project Server.
For detailed information about the users and groups required for Project Server deployment,
please refer to the following document:
http://technet.microsoft.com/en-us/library/cc197607.aspx
1.3 Configure SQL Server and Analysis Services (Project Server 2010)
For Microsoft Project Server 2010 to work correctly, the associated instance of SQL Server must
be configured to enable remote connections using TCP/IP. This is the default configuration for
SQL Server, but we recommend confirming that the configuration is correct before you install
Project Server 2010.
1. Click Start, click All Programs, click Microsoft SQL Server 2008 R2, click Configuration
Tools, and then click SQL Server Configuration Manager.
2. In the left pane, expand SQL Server Network Configuration, and then select the
instance of SQL Server where you will be installing Project Server 2010 databases.
In order for Project Server 2010 setup and configuration to function, you must create a SQL
Server login for the Farm Administrator domain account and give it the required server roles.
2. Connect to the database engine of the instance of SQL Server that you will be using with
Project Server 2010.
5. On the New page, in the Login name text box, type the domain account that you
created for the Farm Administrator.
7. In the Server roles list, select the dbcreator, public, securityadmin, and sysadmin check
boxes.
8. Click OK.
The common language runtime will improve the performance of your Project Server 2010
deployment. To enable the common language runtime, execute the following query:
go
reconfigure
go
Enabling the common language runtime provides a significant improvement in performance for
custom field operations.
1.3.4 Configure Analysis Services
There are two configuration steps that you must follow for the instance of Analysis Services that
you will be using with Project Server 2010:
Add the Farm Administrator account to the OLAP users local group.
1.3.4.1 To add the Farm Administrator account to the OLAP users local group
2. Click Start, point to All Programs, point to Administrative Tools, and then click
Computer Management.
3. On the Computer Management page, in the left pane under System Tools, expand Local
Users and Groups. Click the Groups folder.
6. On the Select Users, Computers, or Groups page, type the name of the Farm
Administrator account.
7. Click OK. The Farm Administrator account will appear in the Members list.
8. Click OK.
1. Open SQL Server Management Studio. In the Connect to Server window, connect to the
instance of SQL Server 2005 Analysis Services that you are using with Project Server
2010.
2. In Microsoft SQL Server Management Studio, in Object Explorer, right-click your SQL
Server 2005 Analysis Services instance name, and then click Properties.
3. On the Analysis Services Properties page, in the Select a page pane, click Security.
4. Click Add.
5. On the Select Users, Computers, or Groups page, type the name of the Farm
Administrator account.
6. Click OK. The Farm Administrator account appears in the Members list.
7. Click OK.
Use the following procedure to install software prerequisites for SharePoint Server 2010.
2. On the SharePoint Server 2010 Start page, click Install software prerequisites.
Note:
3. On the Welcome to the Microsoft SharePoint Products Preparation Tool page, click Next.
4. On the License Terms for software product page, review the terms, select the I accept
the terms of the License Agreement(s) check box, and then click Next.
A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token
authentication without transport security or message encryption in WCF.
Note:
If there is no Internet Access, we need to download the above components from Internet
manually. In our case, the following components need to be downloaded:
A. Make sure the following roles are added for Windows Server 2008 R2:
They can be added manually in Server Manager, and we can just follow the wizard to
add them.
Windows Server 2008 R2 FIX: A hotfix that provides a method to support the token
authentication without transport security or message encryption in WCF is available for
the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=166231)
The following procedure installs binaries, configures security permissions, and edits registry
settings for SharePoint Server 2010.
1. On the SharePoint Server 2010 Start page, click Install SharePoint Server.
2. On the Enter Your Product Key page, enter your product key, and then click Continue.
3. On the Read the Microsoft Software License Terms page, review the terms, select the I
accept the terms of this agreement check box, and then click Continue.
4. On the Choose the installation you want page, click Server farm.
6. Optional: To install SharePoint Server 2010 at a custom location, click the File Location
tab, and then either type the location or click Browse to find the location.
8. When Setup finishes, a dialog box prompts you to complete the configuration of your
server. Ensure that the Run the SharePoint Products and Technologies Configuration
Wizard now check box is selected.
9. Click Close.
12. On the Connect to a server farm page, select the Create a new server farm option, and
then click Next.
a. In the Database server box, type the name of the database server where you
want to host the SharePoint Server 2010 databases.
b. Type the user name and password of the database access account.
c. Click Next.
14. On the Specify Farm Security Settings page, type and confirm a pass phrase for the farm,
and then click Next.
15. On the Configure SharePoint Central Administration Web Application page, select a port
number for the SharePoint Central Administration Web site, and then click Next.
16. On the Completing the SharePoint Products Configuration Wizard page, click Next.
Once SharePoint Server 2010 configuration has been completed, SharePoint Central
Administration will open. There is no SharePoint Server 2010 configuration that is required
before installing Project Server 2010. Therefore, you can close Central Administration.
1. On the Project Server 2010 DVD, run default.hta. The Setup menu opens.
3. On the Enter your Product Key page, type your product key, and then click Continue.
4. On the End User License Agreement page, review the terms of the agreement. To accept
the agreement, select the I accept the terms of this agreement check box.
5. Click Continue.
7. When the installation is complete, select the Run the SharePoint Products and
Technologies Configuration Wizard now check box.
8. Click Close.
11. On the Completing the SharePoint Products Configuration Wizard page, click Next.
Once Project Server 2010 is installed, the following configuration steps are required before
creating a Microsoft Project Web App site and using Project Server 2010:
The procedures to complete these tasks are described in this article. Each of these procedures is
completed by using the SharePoint Central Administration Web site.
Before you can use a domain account within SharePoint Server 2010, you must register it as a
managed account. We can register one to run the various Service Applications in Project Server
2010.
c. Click OK.
The first step is to start the Project Application Service and the PerformancePoint Service in the
farm.
1. On the SharePoint Central Administration home page, in the System Settings section,
click Manage services on server.
1. On the Central Administration home page, in the System Settings section, click Manage
services on server.
Once you have started the Project Application Service and PerformancePoint Service, you must
create a service application for each service.
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.
b. In the Application Pool section, select the Create new application pool option,
and in the Application pool name box, type ProjectAppPool.
c. Select the Configurable option, and select the account from the drop-down list.
d. Click OK.
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
PerformancePoint Service Application.
b. Select the Add this service application’s proxy to the farm’s default proxy list
check box.
c. In the Application Pool area, select the Create new application pool option, and
in the Application pool name box, type PerformancePointAppPool.
d. Select the Configurable option, and select the account from the drop-down list.
e. Click Create.
4. When the service application has been successfully created, click OK.
A Web application is required to host the Project Web App web site and the associated project
sites. Perform the following procedure to create a Web application.
The next step is to create a top-level Web site and give users read permission to that site.
3. In the Primary Site Collection Administrator section, type the account which is Farm
Admin.
4. Click OK.
In order to use the reporting and business intelligence features of Project Server 2010,
you must install the SQL Server 2008 Analysis Management Objects on the Litware-Proj
virtual machine. Click the following link to download the Analysis Management Objects,
and then install the package:
Important:
We highly recommend that you use a separate SharePoint Server 2010 content database for
each PWA site and its associated project workspaces. To correctly isolate the PWA site in its
own content database, you must deploy PWA at a time when other administrators are not
creating new sites on the Web application where you are deploying PWA.
By putting PWA and its associated project workspaces in a separate content database, you
greatly simplify site migration and backup and restore procedures.
1. Create a content database to host the PWA site and its associated project workspaces.
4. Lock down the PWA content database to prevent additional site collections being added.
SharePoint Server 2010 uses a round-robin algorithm to determine the distribution of site
collections across content databases. In order to deploy the PWA site to a specific content
database, you have to lock down any existing content databases in the farm. The process does
not affect user access; it only affects the distribution of new site collections.
To lock down your content databases, follow these steps for each content database associated
with the Web application where you plan to deploy your PWA site.
Important:
Ensure that no other administrators are adding site collections to the Web application where
you plan to deploy PWA while you are performing the procedures in this section.
2. In the Current Number of Site Collections column, note the number of site collections
for the database that you plan to lock down.
3. In the Database Name column, click the link for the content database that you want to
lock down.
a. In the Maximum number of sites that can be created in this database box, type
the existing number of site collection for this database (as noted in the Current
Number of Site Collections column, earlier in this procedure).
Note:
Take note of the current value for this parameter; you will have to change it
back to this value after the PWA site has been created.
b. In the Number of sites before a Warning event is generated box, type a lower
number than the value that is used for Maximum number of sites that can be
created in this database.
Note:
Take note of the current value for this parameter; you will have to change it
back to this value after the PWA site has been created.
5. Click OK.
3. In the Web Application section, choose the Web application where you plan to deploy
the PWA site.
4. In the Database Name and Authentication section, type the database server name
where you plan to deploy your PWA databases, and type a name for the database.
5. Click OK.
Once the content database has been created and configured, the next step is to create the PWA
site itself.
2. On the Manage Service Applications page, click the Project Server Service Application.
3. On the Manage Project Web App Sites page, click Create Project Web App Site.
4. Complete the Create Project Web App Site page as designated in the following table:
Option Description
Project Web App The path from the root site for this PWA site.
path
Select a language The user interface language for this PWA site.
Use Project Web App Use this option if you want to host PWA on a root URL
path as host header (for example, https://www.contoso.com).
Administrator The user account that will be added to the Project Server
Account Administrators security group in this instance of PWA.
You must use this account the first time that you access
PWA.
Primary database The instance of SQL Server where you want to host the
server Project Server databases. If your database administrator
has already created Project Web App databases, specify
the names of those databases in the appropriate text
boxes. If the databases were not previously created,
they will be created automatically.
Published database The name of the Project Server Published database for
name this instance of PWA.
Draft database name The name of the Project Server Draft database for this
instance of PWA.
Archive database The name of the Project Server Archive database for this
name instance of PWA.
Reporting database The instance of SQL Server where you want to deploy
server the Reporting database (if different from the primary
database server).
Use primary database Select the check box to deploy the Reporting database to
server the primary database server specified earlier. Clear the
check box to deploy the Reporting database to a
different database server, and specify the instance of
SQL Server that you want to use in the Reporting
database server box.
Reporting database The name of the Project Server Reporting database for
name this instance of PWA.
Quota for SharePoint The maximum site storage, in megabytes, for the PWA
content in this site site.
Quota Warning for The site storage level, in megabytes, at which a warning
SharePoint content in e-mail message will be sent to the site administrator.
this site
5. Click OK.
Project Server starts the PWA site creation process. This may take some time. When the site
creation process is complete, the status shown on the PWA site list is Provisioned.
Once the PWA site has been provisioned, verify that it was created in the content database that
you created. Use the Get-SPSite Windows PowerShell command, passing the new content
database as a parameter:
4. From the Windows PowerShell command prompt (that is, PS C:\>), type the following
command and then press ENTER:
The command should return the URL for your PWA site and no other URLs.
Note:
If additional URLs beyond that of the PWA site are listed in the content
database, delete the PWA site and restart the procedure with a new
content database.
Once the PWA site is in the desired content database, you must lock down the database to
prevent SharePoint Server 2010 from adding additional site collections to the database. This is
performed by configuring the maximum number of sites for the content database to one.
Note:
Configuring this setting does not prevent new project workspace sites from being created.
4.5 To lock down the content database for Project Server 2010 site
2. In the Database Name column, click the link for the content database that you created.
b. In the Maximum number of sites that can be created in this database box, type
1.
4. Click OK.
Once you have locked down your PWA content database, you can return any other content
databases to their original values for Maximum number of sites that can be created in this
database and Number of sites before a Warning event is generated.
5 Reference
For more information about Project Server 2010 installation:
http://technet.microsoft.com/en-us/library/cc197479.aspx
http://technet.microsoft.com/en-us/library/ee662106.aspx