Planning and architecture for Project Server 2010

Published: May 12, 2010

IT professionals can use the content in this planning and architecture guide to develop conceptual, logical, and physical designs for configuring Microsoft Project Server 2010 features, servers, and topologies. This section also provides recommendations for system designs based on customer scenarios and includes information to help IT Pros design a highly reliable, consistently available, and scalable system.

In this section:

• Plan hardware architecture in Project Server 2010

  This article describes the tested performance and capacity limits of Microsoft Project Server 2010, provides information about the test environment, and test results, and offers guidelines for acceptable performance.

• Plan for deployment (Project Server 2010)

  This article provides links to articles about deployment planning. Before installing Microsoft Project Server 2010, be sure you have reviewed this information.

• Plan for authentication in Project Server 2010

  This article describes planning for security in a Microsoft Project Server 2010 Enterprise Project Management (EPM) Solution. This material is useful for Project Management Organizations (PMOs) and system administrators who are responsible for planning the deployment of a Project Server 2010 EPM Solution.

• Project Server and SharePoint Server security

  Microsoft Project Server 2010 is completely dependent on Microsoft SharePoint Server 2010 to support its user interface and farm topology. Security at the authentication level is tightly integrated between Project Server 2010 and SharePoint Server 2010, whereas user and group authorization is handled separately by Project Server 2010.

• Plan for performance and capacity (Project Server 2010)

  This set of articles covers capacity planning for Microsoft Project Server 2010.

• Plan groups, categories, and RBS in Project Server 2010

  Microsoft Project Server 2010 security is based on users, groups, and categories. This article addresses planning for groups and categories in a Project Server deployment.

• Project Server 2010 upgrade overview

  This article provides an overview of how to upgrade to Microsoft Project Server 2010 from a previous version of Project Server.

• Plan for upgrade to Project Server 2010

  This section contains articles that help you plan and prepare for upgrading from to Microsoft Project Server 2010.

• Hardware and software requirements (Project Server 2010)

  Microsoft Project Server 2010 provides for a number of installation scenarios. Currently, these installations include single server with built-in database installations and single server or multiple server farm installations.

• Project Server 2010 architecture

  This article describes the multi-tiered system in Microsoft Project Server 2010.

• Plan browser support (Project Server 2010)

  This article describes supported Web browsers for connecting to Microsoft Project Server 2010 and other considerations that have to be made in planning for them.

• Plan for Project Server 2010 Web Parts

  This article describes the 18 Web Parts that are installed with Project Server 2010 that provide Project Server 2010 functionality.

• TechNet Webcast: Project Server 2010: Performance, part 1: setup, test, execution, and results

  This Microsoft TechNet Webcast is one of two parts that discuss Microsoft Project Server 2010 performance characteristics and farm architecture planning. This Webcast shows how the testing lab was set up, how the tests were executed, and which test tools were used.

• TechNet Webcast: Project Server 2010: Performance, part 2: architecture, sizing, and capacity

  This Microsoft TechNet Webcast is one of two parts that discuss Microsoft Project Server 2010 performance characteristics and farm architecture planning. This Webcast shows the test results, architecture, data flow, and sizing guidelines and best practices for a Project Server 2010 implementation.

• Technical diagrams (Project Server 2010)

  This article contains models (posters) that detail a specific technical area, such as upgrade paths for Project Server 2010 or the various methods available for migrating from Microsoft Office Project Portfolio Server 2007 to Project Server 2010.