Review system requirements for upgrade (Project Server 2010)


Applies to: Project Server 2010

Topic Last Modified: 2011-11-14

Before you can upgrade your environment from Microsoft Office Project Server 2007 to Microsoft Project Server 2010, your servers must meet the following minimum requirements:

  • The hardware and software must meet or exceed the minimum system requirements to run the new version.

    This includes the requirement for 64-bit hardware and 64-bit versions of the operating system and Microsoft SQL Server. Before you start the upgrade process, make sure that the system meets or exceeds the minimum requirements in Hardware and software requirements (Project Server 2010). Before upgrading, determine how much production capacity that you must have in your upgraded environment and determine the hardware that you must have for an upgrade based on that information.

  • Office Project Server 2007 must be updated to Service Pack 2 and the October 2009 cumulative update.

    Your environment must be updated to at least Service Pack 2 of Office Project Server 2007 to run the upgrade process, either for an in-place or a database-attach upgrade. We recommend that you install the October 2009 Cumulative Update also. For more information about how to install service packs and updates, see Deploy Project Server 2007 updates (


    If you are also using Microsoft Office SharePoint Server 2007, you are also required to update it with Service Pack 2 and October 2009 Cumulative update.

  • Internet Explorer 7, 8, or 9 must be used for Microsoft Project Web App access to Project Server 2010.

    In order to access Project Server 2010 through Project Web App, users must have Internet Explorer 7, 8, or 9. If you attempt to use browsers such as Firefox and Safari to browse to Project Web App, the page will not load because these browsers are explicitly blocked. It is important to note this, especially if you are using other applications that are designed specifically to work with other browsers or versions of Internet Explorer.

    If your company plans to implement Windows 7 on the desktop and you have internal applications that require Internet Explorer 6, you may want to consider the XP mode feature of Windows 7 for Internet Explorer 6 support. You can then keep Internet Explorer 7 or 8 on the native desktop for Project Web App access to Project Server 2010.

    Another option is for users to access Project Server 2010 through a Terminal Server connection on which the host computer uses Internet Explorer 7, 8, or 9.


    The Project Server 2010 Service Pack 1 update provides support for additional Web browsers to access Project Web App pages that are most frequently used by team members. The following are additional supported Web browsers:

    • Firefox 3.6.8+ on Macintosh OS X v10.6, Windows 7 (32-bit/64-bit), Windows Vista SP2, Windows XP SP3, Windows Server 2003 and UNIX/Linux

    • Google Chrome 6.0 on Windows 7

    • Apple Safari 5 on Mac OS X v10.6

    The following are team member pages that are supported with these additional browsers:
    • Project Web App (PWA) main default page (default.aspx)

    • All pages in the "My Work" section in the Quick Launch. This includes the following:

      • Tasks

      • Timesheets

      • Issues and Risks

    For more information about the Project Server 2010 Service Pack 1 update, see Deploy Service Pack 1 for Project Server 2010.


    If you are using Internet Explorer 9 for PWA, you may encounter a small issue with editing grids on certain pages. On these specific pages, when the complete contents of an editable cell are deleted, data cannot be added to the cell until the page is refreshed. To resolve this issue, apply Project Server 2010 Service Pack 1 and make sure that you have the latest updates for Internet Explorer 9. For more information, see Plan browser support (Project Server 2010).

  • Prepare to upgrade or update your Project Professional client users for the upgrade to Project Server 2010.

    Project Server 2010 supports client connectivity from Microsoft Project Professional 2010. It also supports client connectivity from Microsoft Office Project Professional 2007 with Service Pack 2 (SP2), but only when backward compatibility mode (BCM) is enabled on Project Server 2010. If you have not upgraded your Office Project Professional 2007 users to Project Professional 2010, plan to give them the SP2 update so that they will be able to connect to Project Server 2010 after the upgrade from Office Project Server 2007. By default, BCM is enabled after upgrade, and it allows you to conveniently plan to upgrade your Office Project Professional 2007 SP2 clients to Project Professional 2010 over time. Note that when backward compatibility mode is enabled, some new Project Professional 2010 features are unavailable to these users. For more information about BCM, see the "backward compatibility mode" section of Project Server 2010 upgrade overview.


    Project Server 2010 does not support client connectivity through Microsoft Office Project Professional 2003, even when BCM is enabled.

About these requirements

It is important that your hardware meet at least the minimum requirements that are listed in Hardware and software requirements (Project Server 2010); otherwise, you might encounter issues during the upgrade process. For example, if your database server has insufficient memory or processor power, it may be unable to keep up with the number of transactions that occur during the upgrade process, and the upgrade may fail.

We recommend that you use a trial upgrade in a test environment to determine exactly what hardware capacity you must have for an acceptable upgrade experience. If you experience capacity problems with your hardware during the trial upgrade, you can increase the capacity and repeat the upgrade until you are satisfied that you have found the optimal level of upgrade performance.


It is important to track the following three resource components for a server that is running SQL Server: CPU, memory, and I/O subsystem. When one or more of these components seems to have reached capacity, analyze the appropriate strategy based on the current and projected work load, and determine whether to add more resources or to scale out to a new server that is running SQL Server. In general, we recommend that you consider scaling out, in addition to adding more resources.