Project Server 2007 and 2010: Roundup of the week

If you are interested in 2010 then the Product Group blog has a brand new article from Bonny on user controlled scheduling. This covers the ability to turn of the scheduling engine for selected tasks (task type changed from automatically scheduled to manually scheduled) and also introduces the new Task Inspector – which is Task Drivers++. 

Other recent 2010 posts include a feature I love from Roberto on Sync to SharePoint – a very cool new feature that allows collaboration via SharePoint 2010 directly from Project Professional 2010.  This does not need Project Server and works with all versions of SharePoint 2010, including SharePoint Foundation 2010 – the new name for Windows SharePoint Services (WSS).

A reminder of some training opportunities for Project Server 2010 – see Christophe’s posting on the Ignite World tour – both technical and sales tracks will be available, and Christophe also posted a reminder of the software requirements stack for 2010.  Get ready for 2010 – x64 required for your SQL Server as well as all servers in the farm.  x64 also available (but optional) for the client.

Another great addition to the TechNet content this week cam from Michael Jordan, Lead Architect from Microsoft Consulting Services entitled: Microsoft Office Project Server 2007 – Performance and Capacity Planning Best Practices And to plagiarize Christophe: This is a great asset for all customers and partners to ensure they are following deployment best practices to guarantee optimal performance, it is based on best practices learned from hundreds of Project Server 20007 customers engagements as well as scalability labs. 


The purpose of this guide is to extend the Microsoft Office Project Server 2007 Performance Testing Lab ( whitepaper by providing Best Practices and Recommendations. Further recommendations are made in this guide based on field experience and deployment successes in real world scenarios against the main areas of the system. The emphasis is on Project Server 2007 in a production environment using physical servers. Reference is made to virtualization in the relevant sections. However, for a more comprehensive overview please read the Project Server 2007 Hyper-V guide (

The guidelines and recommendations in this guide present the “what” and “why”. Certain areas are prescriptive providing steps on “how” to accomplish the recommendation. However, the assumption is the audience of this guide is able to understand the reasons behind the guidance and take the necessary actions within their organization to implement optimization that applies to their scenario.

The guidelines and recommendations in this guide cover technical, functional and process related guidance. It’s important to note these are mutually inclusive of each other and present cross-impacts through the system when a design is not balanced across all 3 areas. It’s expected that administrators of a Project Server 2007 deployment will collect regular operational and functional data, and over time trend the system for performance and scalar depth. Optimization in all areas is required on a regular basis to maintain an efficient system and identify remediation steps through operational policies.


The intended audience includes IT administrators, database administrators, data architects, system engineers, project managers and business analysts who may be involved in implementing Project Server 2007. This document is designed for a reader who has general knowledge of all the required application and platform components that support Project Server 2007.

Additional Project Server 2007 resources for IT Professionals can be found on TechNet:

If this interests you then Jan’s posting regarding the EPMU training is also a must-read.


Comments (0)

Skip to main content