Delegation is a great new feature in Project Server 2010 that allows one user to allow others to act on their behalf. Very useful when a Project Manager is going to be out of town and doesn’t want to have to re-set the status manager for all her owned tasks just so someone else can action updates – instead she just sets a delegate and they can work as if they were the Project Manager. Works across all features – so can be used for timesheets, or even administrative functions. I’m sure there will be plenty of posts going in to the details but wanted to describe how this works for both new instances of Project Server 2010 as well as upgraded 2007 instances
This is pretty powerful and for new Project Server 2010 instances the default behavior is that Administrators can manage resource delegates – so they can set up delegates for any user on the system. So if they navigate to the Manage Delegates option (under the new Personal Settings on the left navigation – or site map) and click New they will see all the users who can be a delegate if they click the Browse button next to Set Delegate, and they will see ALL users if they click Browse next to the Working on Behalf Of.
However, we have taken the design decision that this is quite a dramatic new feature for existing 2007 users, so the default if you have upgraded a PWA instance from 2007 is that Administrators CANNOT manage resource delegations. So in this case when clicking Browse next to Working on Behalf Of they would see no one.
So the next question is – how do I change this? It is one of the tricky category permissions that sometimes catch our customers out – as it is set for the category of My Organization within the Administrators group. So if you either want to turn this off in your native 2010 instance, or turn it on in your upgraded 2007 instance, go to Manage Groups and select Administrators, then within the Add or Edit Group page scroll down until you see the Categories.
Now for the tricky bit – click on My Organization and you will then see the set of permissions for My Organization! I have collapsed the Project permissions to fit the interesting bit in – the Manage Resource Delegates option.
In 2007 upgraded instances this will look like this and be unchecked – and will need to be checked if you want administrators to be able to set delegates for everyone – in 2010 native instances it will already be checked – so uncheck if you want to turn this off for administrators. You can of course do this the other way around, and go to Manage Categories and then select Administrators – but the key take-away here is that you need to select the category (or group) to see the applicable permissions – something that isn’t always intuitive.
More 2010 postings to come –many, like this one based on early feedback and experience from our TAP customers and Ignite attendees (thanks Jesse!).
Key announcement today on the Microsoft Office 2010 Engineering blog: Get Office for Today or Tomorrow
In addition to the Office 2010 Technology Guarantee, were excited to confirm that Office 2010, SharePoint 2010, Visio 2010, Project 2010 and Project Server 2010 are on schedule and will release to manufacturing (RTM) next month. For businesses, we will launch the 2010 set of products, including Office 2010, SharePoint 2010, Visio 2010, and Project 2010 worldwide on May 12. To find out more about the Worldwide Business Launch, visit http://sharepoint.microsoft.com/businessproductivity/proof/pages/2010-launch-events.aspx. For consumers, Office 2010 will be available online and on retail shelves this June
In addition to the Office 2010 Technology Guarantee, were excited to confirm that Office 2010, SharePoint 2010, Visio 2010, Project 2010 and Project Server 2010 are on schedule and will release to manufacturing (RTM) next month.
For businesses, we will launch the 2010 set of products, including Office 2010, SharePoint 2010, Visio 2010, and Project 2010 worldwide on May 12. To find out more about the Worldwide Business Launch, visit http://sharepoint.microsoft.com/businessproductivity/proof/pages/2010-launch-events.aspx.
For consumers, Office 2010 will be available online and on retail shelves this June
Release is just around so start planning and attend the May 12 virtual launch event!
Great post from the SharePoint team today on Accessibility and SharePoint 2010, great paragraph on the Project grid accessibility capabilities that will ship with Project Serve 2010. A guess what, it’s also highly extensible (and ActiveX free!).
Project Server 2010 includes the new Project Permission feature so that by-default, Project Managers can directly control who has access to the projects that they own. For more information about the Project Permissions feature, see the Project Server 2010 – Project Permissions blog posting.
The ability to directly add or remove permissions to a project is controlled by the Manage Basic Project Security category permission. Given that this is a category permission, it means that it is possible to grant this permission for one project yet deny it for another project or more commonly, to grant it for a group of projects yet deny it for a different group of projects.
By default, the following groups have the Manage Basic Project Security permission enabled on the noted category:
How do you enable or disable this permission? The following steps show you how you could, for example, deny Portfolio Managers from creating project permissions. A similar approach is taken to enable or remove the permission for a group or user.
As noted, you can use a similar process to add the Manage Basic Project Security permission to other users or groups. But do note that that though you can control this permission directly on a category on a user account, for easier manageability it is recommended that you control this at the security group level.
Great News! The latest Cumulative Update (CU) has been released. This include a number of fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. Don’t miss the note below on some Project Server 2007 fixes released that just missed the CU.
The article below provides information on how to deploy the Project Server Cumulative Update.
Deploy cumulative updates (Project Server 2007)
We strongly recommend that you install WSS and Office Servers 2007 Service Pack 2. The KB articles below provide information on how to download and install SP2 if you have not already done so.
Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2
Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2
Description of Office Project 2007 Service Pack 2 (SP2) and of Office Project Language Pack 2007 Service Pack 2 (SP2)
The server patches require that WSS and Office Servers 2007 SP1 be installed. For clarity, SP1 is required and SP2 is strongly recommended. Here are the links to the SP1 Server Patches for your convenience:
Description of the 2007 Microsoft Office servers Service Pack 1 and the 2007 Microsoft Office servers Language Pack Service Pack 1
How to deploy the 2007 Microsoft Office servers Service Pack 1 and Office Server Language Pack 2007 Service Pack 1
The Server CU is released in two different versions. The first version is in Individual Packages specific to a particular product like WSS and Project Server. These are smaller downloads but they do not include language packs or patches for other products so patches for those products would have to be downloaded and installed separately.
The second version is the Server Rollup Packages. This is a set of two rollup packages which contains all the fixes for WSS, Project Server and MOSS. These packages should be used when MOSS is part of the deployment and/or you have language packs installed. The Server Rollup Packages are much larger (~200MB each) but they will greatly simplify MOSS patch deployment.
You can read about the fixes included in the February CU from the following articles:
Note: There has been a follow-up CU build that was released just after the February CU. This CU contains three fixes that are not included in the February CU. Please check http://support.microsoft.com/kb/980854 to see if these are fixes you need. This CU also contains all of the fixes in the February CU so you will not need to install the February CU if you install this fix unless you are a Microsoft Office SharePoint Server (MOSS) user. Customers running MOSS will want to install the server rollup fixes and then the post-February CU. This CU will not be downloadable from the KB so you will need to open a Support Case in order to obtain it. Customers with existing cases open for the February CU do not need to open another case.
Note: There may be a few day delay before all of the articles are published. You can download the CU files through the links at the end of this email should the articles not be available when you click the link. This will give you a head start on testing the patches in preparation for deploying them into production.
Server Rollup Packages:
Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): February 23, 2010
Description of the Office SharePoint Server 2007 Cumulative Update Server Hotfix Package (MOSS server-package): February 23, 2010 (This includes Project Server 2007 CU)
Individual Product Packages:
Description of the Windows SharePoint Services 3.0 Cumulative Update Server hotfix package (Sts-x-none.msp): February 23, 2010
Description of the Office Project Server 2007 hotfix package (Pjsrvapp-x-none.msp, Pjsrvwfe-x-none.msp): February 23, 2010
Description of the Office Project 2007 hotfix package (Project-x-none.msp): February 23, 2010
In order to install this hotfix, you will need to have Microsoft Project 2007 SP1 installed on the client. The article at the URL below contains information on how install download and install SP1 should you not have it installed already.
Note: We strongly recommend that you install Project 2007 SP2 from the information earlier in the article.
Description of Project 2007 Service Pack 1 and of Project Language Pack 2007 Service Pack 1
Microsoft Office 2010 - including Project Standard 2010, Project Professional 2010 and Visio 2010 use the same volume activation technology as Windows 7 and Windows Vista. If you have already set up a Key Management Service (KMS) host to activate Windows, you can use the same host to activate Office 2010 after a few steps.
You can use the following methods to activate Office 2010 by using Office Activation Technologies, which are the same methods that are used for Windows Vista and later versions of Windows:
For detailed information, see Overview of volume activation for Office 2010 in the technical library.
For information about when you would use each activation method, see the four scenarios described in detail in Volume activation quick start guide for Office 2010 in the technical library.
New to Microsoft SharePoint Foundation and Microsoft SharePoint Services is claims based authentication. This means Project Server 2010 also gains this authentication addition and improvement as well.
Briefly, claims based systems provide for federated authentication services such as Active Directory Federation Services (ADSF), single sign-on mechanisms and so forth. In a claims-based authentication system a security token exists and is made up of a set of identity assertions about an authenticated user. Assertions are attributes that are associated with a user’s identity. Assertions can include a user name, a role, an employee ID, and a variety of other attributes that can be used to determine authorization. A Security Token Service (STS) responds to authentication requests and creates the token based on account information in various attribute stores. The token is then used to authenticate actions. In essence, claims-based authentication provides flexibility beyond the traditional Windows NTLM/Kerberos authentication method.
For information about what claims authentication is as well as the STS, see the following articles:
Once you understand what claims based authentication is, you may still wonder how it may be useful to or even necessary in a Project Server 2010 installation. For many Project Server 2010 installations, they will be configured to use Windows-legacy authentication which is essentially the same thing as what you have by default in Project Server 2007. That is, Windows Integrated Authentication challenges that use Negotiate (NTLM/Kerberos). In fact, if today your Project Server 2007 server uses Windows Authentication (the default), then there’s nothing you will need to do differently in 2010 – it’ll just work for you once the upgrade is completed. But, here are a number of cases you’ll need to consider that’ll necessitate the use of claims based authentication.
Whether you are migrating from Project Server 2003 to Project Server 2010, Project 2007 to Project Server 2010, or are new to 2010, use the following road map to help you understand your claims requirements.
Project 2003 Authentication Usage
Impact of 2007 Upgrade
Impact of 2010 Upgrade
Using a mix of Project Server and Windows Authentication
Project Server Accounts will be converted to Forms Authentication Accounts.
Claims authentication setup will be required to support this security configuration.
Exclusively using Project Server accounts for authentication
Exclusively using Windows accounts for authentication
Windows Authentication Classic Mode
No claims authentication setup is required if you wish to continue in this mode.
New Authentication modes for Project Server 2010
This is essentially the same as Forms Authentication.
A slight variation to Mixed-Mode.
Below are explanations for each of the authentication modes and more information to help you understand which to use.
Here are the common authentication modes that will require claims.
Project Server accounts are prevalent in Project Server 2003; Project Server performs all authentication requests, maintains the passwords and so forth. If you plan on using these forms accounts in 2010 instead of converting them to Windows accounts, you will need claims. In Project Server 2003, Project Server accounts prompt you for credentials similar to this:
In many respects, Project Server accounts are very similar to Project Server 2007 forms based accounts and can be converted to such.
An example of 2007 forms base user accounts is the AspNetSqlMembership provider or an LDAP provider. If you plan on using the same in 2010, then claims is required. In Project Server 2010, a forms based authentication prompt looks similar to:
Mixed mode authentication allows you to have two different URLs pointing to the same Project site in order to offer a different authentication mechanism for a given set of users. For example, you may have http://servername/pwa available to your users who are behind your corporate firewall and who are logged on using their Windows credentials. You may also have something like http://northwindtraders.com as an external URL available to users outside of the company domain so that they can log on using a forms-based account. Both URLs, however point to the same Project Server site.
All of these authentication methods use Security Assertion Markup Language (SAML) or claims sign-in. SAML-claims looks and works nearly identically to forms authentication except a third-party off-box solution provides a unified logon. For more information about SAML, see articles such as: http://www.pingidentity.com/landing-pages/saml-lp.cfm http://en.wikipedia.org/wiki/SAML http://xml.coverpages.org/saml.html
A typical SAML sign-in form might look something like the following:
Your organization needs the ability to offer more than one authentication method to users but using the same URL. This is known as multi-authentication. This scenario is similar to mixed mode authentication except there’s only one physical URL in one authentication zone and when a user hits the URL, they are taken to a page where they must choose which authentication method they’ll be using similar to that shown below:
Related to multi-authentication or mixed mode authentication, if you use Windows authentication and you use Forms authentication, then you’ll need to use Windows-Claims with your Forms-Claims setup.
These are the primary scenarios when you’ll need to use claims authentication and for each of these you’ll need to do special setup to enable claims authentication. Below are some articles to help you get this setup:
This article shows you how to enable claims to work with the ASP.NET membership/role provider. This article also discusses anonymous access; take note that anonymous access will not work with Project Server.
This article discusses how to configure a SAML based sign-in. Mixed mode and Multi-Authentication are simply combinations of these two basic types.
For more information about planning for the different authentication methods, see the following:
Question: Are there specific procedures for setting up claims to work with Project Server 2010?
Answer: While setup documents specific to Project Server will be released shortly, there’s nothing claims specific to Project Server 2010.
Question: If I use Forms Authentication today in 2007, can I just install 2010 and will everything work automatically?
Answer: No. There’s some work you’ll need to do. On an upgrade, the easiest approach is to install and then after that is completed, you can set up the web app to use claims (including the steps to enable the asp.net membership provider) and then rerun the SharePoint configuration wizard. Rerunning the wizard will then convert the user accounts to the claims format.
Question: If I plan on using Forms authentication using the ASP.NET SQL membership provider, do claims make it easier to manage the users?
Answer: Claims is not user management but instead deals with the authentication of users. Thus, the same processes you use in 2007 to manage users in your ASP.NET membership provider will need to be used in 2010.
Question: Will all of the features like the Report Center work if I choose to use claims?
Answer: Yes. Once setup is completed, all features will work whether it’s the Report Center or features like project workspaces.
Question: In Project Professional 2007, the Login dialog box has an option to allow me to enter my credentials. How can I do this using Project Professional 2010?
Answer: If you’re logging in using any one of the varieties of forms authentication, you’ll get prompted for login information similar to what you see in the browser. If you are using Windows authentication, there is not a direct option to enter credentials but instead it is controlled via Internet Explorer’s User Authentication options. Within Internet Explorer’s Options, for the security zone in which your PWA site exists, change the login options to prompt similar to the picture below:
Note: This changes the logon option for the entire zone and is not exclusive to Project Professional.
Here’s a news item for our Microsoft partners. Microsoft is introducing a new Microsoft Partner Network Community, designed to facilitate real-time networking opportunities between people selling or building Microsoft solutions, Microsoft partners and Microsoft.
The community offers a number of ways for you to engage with your peers and Microsoft, either globally or directly within your region.
I’d like to direct you to a few partner network community resources that may be of interest to you and help you start the conversation with other partners and Microsoft.
This is the final installment of a four part series on common workflow administration tasks associated with Project Server 2010.
Installation and setup of Project Server 2010 is covered in the overall setup guide, and these articles will make the assumption that the user has already read and completed the setup of Project Server 2010.
These articles also will not cover the topic of creating Project Server 2010 workflows. Please refer to our SDK articles to find out more information on how to create our workflows.
Restarting a workflow may become necessary for any number of reasons. By restarting a workflow, you will cause the workflow engine to execute the workflow from the very beginning. No project related data will be lost or reset. This action simply tells the workflow to “Go to Stage 1” and execute everything again. Similarly, changing a project to another Enterprise Project Type that has a workflow, will cause the project to execute the new workflow from the very beginning.
The skip to stage functionality is something that will only work if the workflow is correctly designed to allow for stage skipping. All project server workflows will always stop whenever natural stop points are reached. These include
As such, to get the skip to stage functionality working fully, you will need to incorporate “if” branches that will bypass “stop points” like approval points and portfolio selection points when developing the workflows.
This is the third of a four part series on common workflow administration tasks associated with Project Server 2010.
This is the second of a four part series on common workflow administration tasks associated with Project Server 2010.
Project Server Workflows need to run under the context of a user. However, they do not run under context of the user that started the project, instead, the workflows are run under the “Workflow Proxy Account”. This means that the user account which you specify as the workflow proxy account must have the proper rights to execute all of the commands a project server workflow will need to do.
It is recommended that you setup a service user to serve as this function. The steps below show how to define and setup a workflow proxy account.
This is the first of a four part series on common workflow administration tasks associated with Project Server 2010.
Once a workflow has been created within Visual Studio and activated on the server farm (covered in SDK articles) the administrator will need to correctly associate the workflow with an EPT.
Overview of Microsoft Project Server 2010 for IT Professionals
Tuesday, December 15, 2009 8:00 AM Pacific Time (US & Canada)
In this webcast, we provide an overview of Microsoft Project Server 2010 features, requirements, and deployment considerations that IT professionals need to know about the product. Topics we discuss include: system requirements, deployment scenarios, installation procedures, upgrade options, and administration and operations enhancements that help IT professionals.
Christophe Fiessinger, Senior Technical Product Manager, Microsoft Corporation
Project 2010 Overview
Wednesday, December 16, 2009 11:00 AM Pacific Time (US & Canada)
Keshav Puttaswamy, Group Program Manager, Microsoft, will discuss and demonstrate core capabilities and features of the upcoming release – Microsoft Project 2010. The webcast will cover the key bets of unifying project & portfolio management, improving execution with effective collaboration, enhancing user experience & appeal, and simplifying deployment & interoperability.
Keshav Puttaswamy, Group Program Manager, Microsoft Corporation
Project Server Security in SQL Server Reporting Services
Wednesday, December 16, 2009 1:00 PM Pacific Time (US & Canada)
In this webcast, we discuss a method of taking advantage of Microsoft Office Project Server security in Microsoft SQL Server Reporting Services reports. We also cover a scenario where a customer has requested a SQL Server Reporting Services report that displays sensitive financial data. The customer only wants executors of the report to see information on projects to which they have access. Join us to learn more.
Stephen C. Sanderlin, System and Software Architect, MSProjectExperts
Project 2010 and Project Server 2010 Programmability
Thursday, December 17, 2009 8:30 AM Pacific Time (US & Canada)
In this webcast, we provide an overview of the programmability enhancements that are in the upcoming versions of Microsoft Office Project 2010 and Microsoft Office Project Server 2010. We highlight Windows Communication Foundation, Ribbon programmability, and the new programmability features such as Workflow. We also discuss writing backwards compatibility for Microsoft Office Project 2007 applications
Chris Boyd, Program Manager II, Microsoft Corporation
All will be recorded and available afterward as podcasts in case you miss them.
We will be supporting migration from Microsoft Project Server 2003 SP3 to Microsoft Project Server 2010 via a Virtual Migration Environment (more details to come.). If you have not already updated your 2003 server to SP3, now might be a good time to plan the application of that service pack.
The Project Server 2010 Business Intelligence feature utilizes the support of Excel Services, Secure Store Service, PerformancePoint Services and SQL Server. A thorough understanding of how these features fit together is necessary to get the most from the feature. This post will provide that overview and provide troubleshooting questions for common issues.
Our Business Intelligence features leverage Excel Services as the base functionality since most people use Excel to visualize data and it’s a tool that many people already know how to use.
There are four core components to this solution.
Excel client. The Excel Client is used to author and publish new reports. This solution will work with Excel 2007 SP2 or later.
Office Data Connections. Office Data Connections(ODC) are used to store the connection information, the SQL Query and the Secure Store Target Application ID. External ODCs are used to allow you to manage data connection and query information externally to the reports that consume the data. These two components together are the deliverables from the report author.
When you provision a new Project Web Application site or when you create a new OLAP database, ODCs and attached templates will be automatically generated in the Business Intelligence Center.
Excel Services. Excel Services provides rendering and interactivity support on the web. This service enables the user to share reports easily with others. It also enables a user to filter the data in a report dynamically to meet a particular need.
Secure Store. Secure Store is a SharePoint service used to store credentials in a Target Application Profile. These profiles help avoid double hop authentication situations and provide control around who has access to what data for a given Target Application Profile. In SharePoint Server 2007, this service was known as Single Sign-On service or SSO.
The diagram above illustrates the interactions between the four components. The arrows denote what information is passed between the components and in what direction.
Lastly, PerformancePoint is called out above as it is used to create the Business Intelligence Center as it is their service that provides this infrastructure. It isn’t used for the core reporting features. However, you can easily develop PerformancePoint reports over Project Server data.
The setup steps for the Business Intelligence features can be found here. http://technet.microsoft.com/en-us/library/ee662106(office.14).aspx
Please note, if you are using Active Directory(AD), you can set up a AD Group for Report Authors such that you only have to create one SQL Login for the group. The membership of the group is then maintained outside of SQL Server.
Also, you must set up a SQL Login with db_datareader rights for the credentials used in the Secure Store Target Application ID. If you have created the AD group for the authors above and it matches the security needed to service reports, you can simply add the Target Application ID credentials to the Report Author’s AD group instead of creating a new SQL Login.
This can be due to a number of reasons. Here is a list of items to verify. The steps to do each of these items are listed in the setup link above.
We’ve added some performance configuration suggestions for SQL in this release, based on feedback from early test customers and from the results of our own performance testing. These settings are intended to help the overall performance of the system.
The following properties should be set on your Project Server databases.
Auto close is typically set to False by default when Project Server 2010 creates the databases for a farm setup. If set to True, this property tells SQL Server to automatically close the database when the last user has ended their connection and all other processes have completed. This makes sense in single user scenarios when you are using the desktop version of SQL Server with limited resources. However, on a multiple user system, this creates unnecessary overhead.
This property can be set accidentally, if you prototyped an environment using a Standalone install and then moved the databases to a production farm.
Slow queries are annoying to everyone. One of the most common factors we’ve found that cause this slowness to occur is the database statistics being out of date. The two settings above are recommended so that your statistics are kept up to date AND that query processing doesn’t wait for the statistics refresh to complete. Previously, if you set AUTO_UPDATE_Statistics to True, if SQL found stale statistics, it would halt a query and make it wait until the statistics were updated. Depending on the size of the database and the query, this can lead to a substantial wait time, leading the user to think the system is hung.
In SQL Server 2005, the AUTO_UPDATE_STATISTICS_ASYNCHRONOUSLY property was added. This enabled SQL to automatically refresh the statistics in the background while allowing queries to continue execution. This leads to a better overall user experience since the operation may be a bit slower initially but it still completes. Note, Project Server 2010 does not set this property by default. Also, note, if you are migrating Project Server 2007 databases, you should update these properties post Upgrade. For more information, go to this link: http://msdn.microsoft.com/en-us/library/ms190397.aspx
If you upgrading databases from SQL Server 2000 to SQL Server 2005/2008, the sampling algorithm changed in the 2005 release. It is recommended that you run sp_updatestats with the RESAMPLE option to update the statistics, using the new algorithm.
Custom field performance will see the most benefit from this setting. As the number of custom field values grow, the query performance will decline as the number of records to query grows.
Note, I said custom field values, not number of custom fields. For example, if you have a task level custom field with a large lookup table and assignment roll down enabled, this one field will create a lot of potential data to query. The new departments feature of Project Server 2010 may also lead to more custom fields and custom field values on the server.
Enabling the CLR on the SQL Server allows us to execute queries in a more efficient manner by reducing stress on the application server, reducing SQL roundtrips and performing queries closer to the data. The resulting Custom Field performance gains are significant. For more information on how to enable the CLR, go to this link. http://technet.microsoft.com/en-us/library/ee662108(office.14).aspx#section3
I recommend starting with the SharePoint Guidance for SQL Server Database Administrators. The document is targeted to SharePoint Server 2007 but the concepts are valid for SharePoint Server 2010 as well. This document can be found here: http://technet.microsoft.com/en-us/library/ee721075.aspx
Another article on Project Server 2007 Performance and Capacity Planning best practices white paper would also be another great read. This document can be found at http://technet.microsoft.com/en-us/library/dd823304.aspx
The initial documentation for planning a SharePoint Server 2010 Server farm may also be of interest to you. The documentation can be found here: http://technet.microsoft.com/en-us/library/cc789337(office.14).aspx
Lastly, there are three videos from the Project Conference which may be of interest to you. Each cover aspects of SQL Server and Performance best practices.
The Microsoft Project Server 2010 Public Beta will expire on October 31, 2010. Some people have asked and I wanted to make this date clear to all.
Please note: Project Server 2010 Public Beta is not supported for Production use.
Also note: upgrade from Microsoft Project Server 2010 Public Beta to Microsoft Project Server 2010 Released Version is explicitly blocked and not supported. This restriction applies to both In-Place or DB Attach upgrade methods.
In the previous post, it was stated that Windows Server 2008 R2 support was coming. I’m happy to announce it is here, if you apply the following hotfix. http://support.microsoft.com/kb/976462 Once you apply it, you don’t have to reboot the server. However, we would suggest doing an IISReset to ensure everything is reloaded with the patched bits.
My name is Treb Gatte and I’m the Program Manager responsible for Setup and Upgrade for Microsoft Project Server 2010.
In this post, we will review the major requirement changes for Project Server 2010 and give you the locations of the documentation. In subsequent posts, we will review the “shopping list” of required patches and software levels and then delve into the setup process itself.
While much of Project Server 2010 will look familiar to Project Server 2007 users, there are some key items that have changed in the infrastructure.
Project Server 2010 now requires Microsoft SharePoint Server 2010 as a setup prerequisite. SharePoint Server 2010 is the latest version of what was Microsoft Office SharePoint Server (MOSS) 2007. This is a higher SKU than in the previous release where only Windows SharePoint Services 3.0 was required. The key takeaway is that this change may impact your infrastructure and licensing needs.
Project Server 2010 leverages SharePoint Server 2010 to provide workflow capabilities to our new Portfolio features, charting support for Resource and Portfolio charting and Excel Services and the Business Intelligence Center to greatly enhance our Business Intelligence capabilities.
Project Server 2010 will only be offered in 64 bit versions this release. The 64 bit requirement is the same for all tiers (web front end, application server and SQL Server). This change was done to take advantage of better performing hardware. The key takeaway is that this change may impact your infrastructure needs.
Most customers we’ve talked to seem to already use 64 bit SQL Servers. The impact appears to be to the Web Front End /Application Server tiers.
Project Server 2010 requires Internet Explorer 7 or higher only. This means if you attempt to use Firefox and Safari to browse to PWA, it will not load as these browsers are explicitly blocked. The key takeaway is that this may have an impact on how you implement the solution.
If your company is planning to implement Windows 7 on the desktop and you have internal applications that require Internet Explorer 6, you may consider the XP mode feature of Windows 7 for IE 6 support while keeping IE 7/8 on the native desktop for other applications, such as Project Server.
The final release of Project Server 2010 can be hosted on Windows Server 2008 SP2 or later or Windows Server 2008 R2. Please note, the Public Beta can be hosted on Windows Server 2008 SP2 initially. Windows Server 2008 R2 support will be added to the Public Beta in the near future. We’ll post a note when that support is available.
Project Server 2010 will require SQL Server 2005 SP3 CU3 or SQL Server 2008 SP1 CU2 to be installed. As a result, we will no longer support SQL Server 2000. We are currently testing SQL Server 2008 R2 November CTP. Therefore, it isn’t officially supported for Public Beta yet. A note will be posted when this support is available.
Absolutely, positively no ActiveX controls anywhere. This will reduce the long term impact of cumulative updates and service paces and well as make initial installation much easier.
Windows PowerShell support has been added to Project Server 2010. This capability makes managing and setting up SharePoint Server and Project Server much easier. If you’ve never used Windows PowerShell, this primer would be a great place to start. http://technet.microsoft.com/en-us/library/ee176949.aspx
Project Server 2010 now integrates directly with Exchange Server 2007 SP2 or later rather than use the Outlook Add-In. If your users want to update task status via Outlook, you no longer have to contend with the Outlook Add-In ActiveX control. All configuration is done on the Project Server and the Exchange Server.
If you are using OLAP, Project Server now requires SQL Server 2008 Analysis Management Objects instead of DSO. The setup details and link to the download can be found here: http://technet.microsoft.com/en-us/library/ee662106(office.14).aspx#section2
The number of post installation configuration steps are greater than in past releases and are needed in both SharePoint and Project Server. Project Server 2010 is now dependent on the following services for Business Intelligence features. As such, there are post configuration steps to enable the functionality for each Project Web Application instance.
For charting in the Portfolio and Resource features, there is a dependency on the State Service. However, this service is automatically configured by our provisioning process since it is a farm wide service.
In Project Server, you will now have to configure Time Reporting Periods as the newly redesigned My Tasks and My Timesheet interfaces depend on having those periods configured. If you previously configured Timesheet Periods in Project Server 2007, these values will populate this table automatically on upgrade.
There are also some recommended SQL Server settings that will improve your performance, which we will cover in a separate post.
To make it easier for you to correctly setup the product, the setup and upgrade documentation is located here.
Sometimes, seeing the process performed can be a great way to see beyond the documentation. Therefore, we’ve created videos of the entire setup process for you to review.
Deploy Project Server – Single Application Server Farm
Deploy Project Server – Multi Application Server Farm
Create Project Web Access Site:
Add an Application Server to a Project Server Farm:
This blog focuses on the needs of the Project Administrator/Implementer. The posts will answer the questions of how do I and why would I implement various aspects of Project Server. While there will be a lot of content for Project Server 2010, we will also have Project Server 2007 related content as well.
Why another blog? Most of our readers use RSS feeds to get their content. Therefore, segregating the content makes it easier for each audience to get related posts for their areas of interest.
The Project blog at http://blogs.msdn.com/project will continue to have great content targeted at readers who want to know more about new features and how to use them.
The Project Programmability blog at http://blogs.msdn.com/project programmability will continue to focus on developer content for Project Server.