Project Server 2010: Things to note, and avoid, as you start the 2010 journey…

Unless you have been living in a cave you will have heard that next month sees the virtual launch of Office 2010.  Details of the virtual launch and other availability stuff at but I thought I’d take a few minutes to prepare the scene.  I know you will all read the wealth of documentation we have up on the TechNet Project Server 2010 TechCenter but sometimes our customers can get imaginative and read more into what we don’t say that what we do.  “I know TechNet says that apples are apples, but it doesn’t say that apples are not bananas!”

So to cover off the things that have caught some of our internal folks and early adopters out;

  • You need to have SharePoint Server 2010 licensed as ENTERPRISE to be able to load and run Project Server 2010
    • It will NOT run or load on SharePoint Foundation, SharePoint server 2007, WSS 3.0, SharePoint Portal Server 2003, SharePoint Team Services, Office Web Folders (yes, I have been around SharePoint that long…) or any earlier variant of FPSE or VTI stuff.
    • You cannot use SharePoint 2010 (any version) to support Project Server 2007 or earlier
  • You need x64, for ALL servers
  • You need x64 for your SQL Server.  Theoretically I think you could support the Analysis Services features on a different x86 SQL Server, but why would you…
    • You cannot use the Analysis Services instance created for PowerPivot to support Project Server 2010 OLAP database functionality – the OLAP mode it requires is not compatible with the mode required for Project. You could use a different instance on the same server –but be aware that PowerPivot has some high resource requirements and might be best on its own server.
  • As you have SharePoint Server on your farm as a requirement, please take into account the extra resource requirements before turning on all the extra new services
  • If you have a 2007 farm with MOSS and Project Server and you plan to upgrade in place (assuming you meet all the requirements – x64 etc.) then you have to upgrade to both SharePoint Server and Project Server 2010.  You cannot just upgrade SharePoint.  Also note that October 2009 CU is required as the starting point for this in place upgrade
  • Project Professional 2010 can only connect to Project Server 2010.  Project Professional 2007 can connect to 2010 servers in Backwards Compatibility mode
  • If you are running SharePoint PowerShell commands you need to be running as an administrator

Apples are not bananas.  Full details of the requirements can be found at and there is also a great webcast detailing upgrade and migration at

Please note the SQL Server requirements particularly:

  • SQL Server 2008 SP1, CU2 or CU5 or above (not CU3 or CU4)
  • SQL Server 2005 SP3, CU3

So start getting your servers or HyperV images prepared and above all – enjoy!  Project Server 2010 is an awesome product, and that is a word I do not use lightly!

Technorati Tags:
Comments (4)

  1. David Hans says:

    Hi Brian,

    just to clarify one specific point in this article, related to SQL2008 R2 – are you saying that if you are running your 2010 farm against a single SQL server/cluster, you have to have 2 instances of Analysis Services if you plan to use both Project Server 2010 OLAP Cubes AND PowerPivot ?  (due to different modes etc.)

  2. Great point David – and yes, but not quite.  the PowerPivot AS instance I am referring to is the one that gets installed to the SharePoint Server (so not a good place to have your Project data – and I’d even say Project Server and PowerPivot for SharePoint should be muutally excusive…

    I stole the following from in the PowerPivot for SharePoint

    · Analysis Services Service   Loads the VertiPaq engine to manage the data within PowerPivot workbooks retrieved from SharePoint content databases. The PowerPivot system service extracts the database from the Excel workbook, selects an appropriate SharePoint application server, which runs the Analysis Services service as well as an instance of the PowerPivot system service, and then attaches the database to the Analysis Services instance without requiring Excel 2010 on the server.

    Note: On a SharePoint server, an Analysis Services instance can only load VertiPaq databases for in-memory BI processing. Analysis Services in VertiPaq mode does not support traditional OLAP processing modes. Although it is possible to install additional Analysis Services instances on the same server to support traditional OLAP processing, Microsoft does not recommend this configuration because of the differences in workload patterns and resource consumption.

  3. Debbie Harris says:

    We are in the planning stages of migration and I was wondering about the linkage to Exchange because we will not be upgrading our Exchange environment until the end of 2010.  I would like to put up a Project Server 2010 environment before that so I can have plenty of time to build out the information and templates needed for the new proposal functionality to create and select projects.  Can the connection to Exchange be added after an initial deployment, or is that something that has to be part of the installation?


  4. Hi Debbie,

    Great question.  The link to Exchange can easily be activated later.  The code will be deployed when you install Project Server 2010 but does not get turned on automatically.  There is a setting in Server Settings to switch the link on (once you have made the permission settings in Exchange – see TechNet article) and then another setting for each resource whose tasks you wish to sync. The article at

    Best regards,


Skip to main content