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.
http://technet.microsoft.com/en-us/library/cc197280(office.14).aspx
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:
Configure Reporting:
Add an Application Server to a Project Server Farm:
Project Server 2007 allows you to creating literally hundreds of custom fields. This is great, but a huge downside is that all of these fields are not typically needed by every user and therefore, they may add clutter and confusion. In 2007, it is also not possible to create different custom field rules for one project vs. another user. For instance, you cannot make a field required for one project yet optional for another.
With Project Server 2010, departmental custom fields help to relieve the problems of too much information and too many choices. As an example, departments help you to manage the UI clutter, and help you to define, at a resource, at a task, or at a project level, which fields are required or not required. Let’s walk through this new feature and show you how you can use departments to manage your enterprise custom fields.
To begin with, we need a brief conversation about scope. In Project Server 2007, all custom fields are globally scoped which means the fields are available to all users. In Project Server 2010, fields can be globally scoped, but they can also be departmentally scoped as well. Consider this list of custom fields:
Field
Scope
Department
Required?
ProjectCustomText1
Global
-
No
ProjectCustomText2
Yes
ProjectCustomText3
Marketing
ProjectCustomText4
ProjectCustomText5
Development
ProjectCustomText6
If a project belongs to the Development department, then when viewing areas of the product that enabled departmental fields, you will see:
Let’s say we have a user named Bob. Departments filter the list of custom fields Bob sees by-default. This does not mean, however, that he won’t be able to view custom fields assigned to the marketing department. When Bob saves a project, which fields will he be required to enter values for? Remember, in Project 2007, Bob would need to input data for all required fields. In Project 2010 since a project, for example, can be associated with a department, Bob may be required to enter a value for the ProjectCustomText5 field AND will always be required to enter a value in the ProjectCustomText2 field since has global scope.
A quick summary of scope shows that departmental fields enable two primary functions:
It needs to be stressed the departmental fields are not tied into security. That is, you cannot use them with security categories and groups to enable or disable fields and their functions. Instead, their primary purpose is to filter out fields you don’t need to deal with. There are places in Project Web App (PWA) where you may not be able to see filtered fields and so it may seem like security has been applied, but you’ll find that in places like Project Professional, you can re-filter to show all fields.
Remember this: it’s about Structure and NOT Security.
Now, let’s look at what it takes to setup and use departmental fields.
By default, Project Server 2010 has a new lookup table named Department. Similar to the 2007 State and RBS lookup tables, this is a permanent lookup table (you can’t delete it) that is blank by-default.
Like any other lookup table, you can define the code mask and create a lookup table that’s flat or hierarchical. In addition to the Departments lookup table, by default there’s also the “Project Departments” and “Resource Departments” fields, predefined with the Department lookup table selected (you can’t change this).
These two new fields control a number of aspects within Project Professional and PWA. As with other custom fields associated with lookup tables, you can choose whether or not multiple values can be selected. But, just as with other such fields, once you’ve chosen to allow multiple values, you cannot revert back to single selection. So be careful in your selection!
You can create other custom enterprise fields and also choose to associate them with departments as shown below.
To help administrators easily determine which fields have been associated with a department, as you can see in the next picture the new Department field has been added to the Enterprise Custom Fields and Lookup Tables page.
In addition to setting up custom fields and associating them with departments, you can also associate users with departments. Let’s suppose user Bob needs to be a part of the Development and Testing departments. While editing his user account, you set the departments as seen the next picture.
Remember, setting the user’s department(s) helps to control how custom fields are filtered to them and helps to control which whether some items are seen or not seen in PWA.
Now that you’ve had a brief overview of creating departments, and associating departments with fields and with users, how do you use them in normal every day usage and what should you expect? There are a number of Places in Project Professional and PWA where departmental custom fields can be used to your advantage so let’s take a brief look at these.
To understand how departmental custom fields are used in Project Professional, let’s look back to the first example given earlier where there are the two globally scoped project level fields plus two each for the marketing and development departments. Our user Bob is working in Project Professional and is saving a project. By default, Bob will see only the globally scoped enterprise project fields similar to the below picture:
Bob sees the two global fields because this project has not been associated with a department. Therefore, when Bob attempts to save the project (and without entering text into the ProjectCustomText2 field), he sees the following message:
Bob then enters a value into the ProjectCustomText2 field and is able to save the project. Bob then goes to the Project Information dialog box and associates the project with the Development department. Now he sees not only the global custom fields, but also two additional fields associated with the Development department.
Take notice that the required fields always appear at the top of the list.
Here you see the addition of both the ProjectCustomText5 and the ProjectCustomText6 fields. Bob forgets to fill in the required ProjectCustomText5 field and is reminded of this when saving similarly to when he neglected to enter required text into the ProjectCustomText2 field.
Finally, Bob fills in the required field and is able to successfully save his project. The same concepts can be applied to task level custom fields as well. For instance, you can assign a department to a task-level custom field and if the project belongs to the department and a field is required, you’ll need to fill in a value for all tasks in the project before you can save it.
There are a few places in PWA where departments affect your experience and an example is when creating new projects based on an enterprise project types (EPT). The administrator who creates the EPTs can specify that they belong to a department. Therefore, when creating new projects from within the Project Center view, the list of EPTs you see is filtered based on your department. Likewise, when editing the properties of a project, you will see similar behaviors. In the following picture, suppose you you are a project manager and you are a member of the marketing department.
Here, you see the “EPT for Marketing Projects” EPT because you are a member of the marketing department. If there are EPTs that have no department association, then they appear in the list as well. However, EPTs associated with other departments do not appear and unlike in Project Professional where you can set the department filter within the Save dialog box, there’s no provision to do so in the Project Center.
Project Server 2010 allows you to create multiple OLAP databases for reporting purposes. When configuring a cube, you can specify both the project and source departments so that the cube is “filtered” on these criteria. Here is a look at the OLAP Database Build Settings page:
Within the cube configuration, you can add the Project department field as a dimension to the Project and Tasks cubes and you can add the Resource department field as a dimension to the Resource cube. Like any other custom field, if the Project or Resource departments fields are defined for multiple values, then they can be used for filtering, but the field itself does not make it into the cube.
Departmental custom fields are used heavily in Project Server 2010’s portfolio analysis features. When creating your driver library, you can associate a business driver with a single or multiple departments as shown in the following picture:
In this example, Driver2 has been associated with both the Development and Testing departments.
Similarly, after your business driver library has been established and you want to create the driver prioritizations, when establishing the properties for the prioritization set, you can associate it with a department.
A department on the driver prioritization filters which business drivers are available. In the previous picture, you can see that Driver2 is available because this driver belongs to both the Development and Testing departments. Obviously, having just one business driver will not produce a good portfolio analysis, but the example suffices.
This brief overview of departmental custom fields has been given to help you understand the following:
Great News! The latest Cumulative Update (CU) for Office and Office Servers 2007 has been released (news of the 2010 releases coming shortly!). 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.
*** Update *** Also do not forget the upcoming Webcast where Adrian Jenkins will provide an overview of this release and also address related questions:
Information About Microsoft Project and Project Server Cumulative June Update - Tuesday, July 13, 2010 8:00 AM Pacific Time (US & Canada)
For full details of this series please see http://blogs.msdn.com/b/chrisfie/archive/2010/06/16/microsoft-project-and-project-server-2007-and-2010-cumulative-update-webcast-series.aspx
*** /Update ***
The article below provides information on how to deploy the Project Server Cumulative Update.
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.
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:
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 June CU from the following articles:
Note: There may be a few day delay before all of the articles are published.
Server Rollup Packages:
Individual Product Packages:
Client Installation:
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.
Once we know that SP1 is installed, you will install the hotfix by performing the following steps:
NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.
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.
Following the first 2010 CU desktop released a few weeks ago, the server KB and hotfix download are now live!
Don’t forget to watch this recorded webcast: Information About Microsoft Project and Project Server Cumulative June Update and with this PowerPoint deck to learn the updates included in this first 2010 CU.
http://blogs.technet.com/b/projectadministration/archive/2010/06/30/june-2010-cumulative-update-cu-for-project-server-2007-office-sharepoint-server-2007-wss-and-project-2007-now-available.aspx
Service Pack 3 (SP3) for Project and Project Server 2007 are now released and can be found at:
For full details and more specific link see the Office Sustained Engineering blog at http://blogs.technet.com/b/office_sustained_engineering/archive/2011/10/25/office-2007-and-sharepoint-2007-service-pack-3-availability.aspx
*** Update – just heard there are a couple of issues being investigated with the 2007 Office packages – this affects the MOSS Server package 2596540 (which is the roll up that also includes the Project Server 2007 fix below), and a Project 2007 fix that was specifically aimed at implementations of Project 2007 and Office 2010 where Visual Reports would not work. Also corrected the description below from 2010 to 2007 – sorry… Both of the updates below are unaffected. *** All affected updates have been re-released 11/1/2011
The October 2011 Cumulative Update for Project and Project Server 2007 can be found at:
A few answers to questions I’m am sure are on the tips of your tongues (as we have all been asking them internally)
Thanks to Rob and Adrian for the information – and Adrian and I (mostly Adrian) will include SP3 in our regular Cumulative Update webcast – 11/8/2011.
Here’s the URL for the 11/8/2011 8:00:00 AM - Information about Microsoft Project and Project Server October 2011 Software Update
https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032493962&Culture=en-US
There is a slight delay in the release of the 2010 Cumulative Updates for October 2011 – more information as soon as I have it.
Great News! The December Cumulative Updates (CU) for Project and Project Server 2010 and 2007 have been released. Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.
Also remember to join us in January for a TechNet webcast to go over both the December 2011 Cumulative Updates for Project Server 2010 and Project Server 2007. The information for this event is below:
TechNet Webcast: Information about Microsoft Project and Project Server December 2011 Software Update (Level 200) https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032493964&culture=en-us
TechNet Webcast: Information about Microsoft Project and Project Server December 2011 Software Update (Level 200)
https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032493964&culture=en-us
Project and Project Server 2010
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.
You can read about the fixes included in the Project and Project Server December CUs from the following articles:
Server Rollup Package(Recommended):
Description of the Project Server 2010 cumulative update package (Project server-package): December 13, 2011 http://support.microsoft.com/kb/2597015
Description of the Project Server 2010 cumulative update package (Project server-package): December 13, 2011
http://support.microsoft.com/kb/2597015
Individual Project Server Package:
Only required if you do not install the Server Rollup. Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): December 13, 2011 http://support.microsoft.com/kb/2596997
Only required if you do not install the Server Rollup.
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): December 13, 2011
http://support.microsoft.com/kb/2596997
Project Client Package:
Description of the Project 2010 hotfix package (x86 Project-x-none.msp, x64 Project-x-none.msp): December 13, 2011 http://support.microsoft.com/kb/2597006
Description of the Project 2010 hotfix package (x86 Project-x-none.msp, x64 Project-x-none.msp): December 13, 2011
http://support.microsoft.com/kb/2597006
More information on deploying the Cumulative Update:
Updates for Project Server 2010 http://technet.microsoft.com/en-us/projectserver/gg176680.aspx As Project Server 2010 is now based on SharePoint Server 2010 we strongly recommend that you install the Project Server 2010 Server Rollup Package as there are a large number of individual server packages for SharePoint Server. The Project Server 2010 Server Rollup Package contains all the patches released in this Cumulative Update for SharePoint Foundation Server 2010, SharePoint Server 2010 and Project Server 2010. For those accustomed to Project Server 2007 Cumulative Updates, you should note that the MOSS Server Rollup Package does not contain the Project Server patches. As in Project Server 2007, the Server Rollup Packages are much larger but they will greatly simplify your Project Server patch deployment. Client Installation: Installation of the client patch is straightforward and is the same as it was in Project 2007. The instructions for installing the client patch are below. NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout. Download the hotfix from the link in the KB Article. Extract the patch package by running the .exe file that you downloaded. Run the extracted .exe file to apply the patch to your Project Professional/Standard client.
Updates for Project Server 2010
http://technet.microsoft.com/en-us/projectserver/gg176680.aspx
As Project Server 2010 is now based on SharePoint Server 2010 we strongly recommend that you install the Project Server 2010 Server Rollup Package as there are a large number of individual server packages for SharePoint Server. The Project Server 2010 Server Rollup Package contains all the patches released in this Cumulative Update for SharePoint Foundation Server 2010, SharePoint Server 2010 and Project Server 2010.
For those accustomed to Project Server 2007 Cumulative Updates, you should note that the MOSS Server Rollup Package does not contain the Project Server patches. As in Project Server 2007, the Server Rollup Packages are much larger but they will greatly simplify your Project Server patch deployment.
Installation of the client patch is straightforward and is the same as it was in Project 2007. The instructions for installing the client patch are below.
Project and Project Server 2007
*** Update - all packages now available (12/16/2011) ***
There was an issue found with the Project Server 2007 December Cumulative Update and it had to be rebuilt. The issue has been fixed and we expect the patch to be released the week of December 19th.
You can read about the fixes included in the December CU from the following articles:
Available Now! Description of the Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package): December 13, 2011 http://support.microsoft.com/kb/2596987
Available Now!
Description of the Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package): December 13, 2011 http://support.microsoft.com/kb/2596987
ETA: Week of December 19th. Now available (12/16/2011) Description of the Office SharePoint Server 2007 cumulative update package (MOSS server-package): December 13, 2011 http://support.microsoft.com/kb/2596986
ETA: Week of December 19th. Now available (12/16/2011)
Description of the Office SharePoint Server 2007 cumulative update package (MOSS server-package): December 13, 2011
http://support.microsoft.com/kb/2596986
Available Now! Description of the Windows SharePoint Services 3.0 hotfix package (Sts-x-none.msp): December 13, 2011 http://support.microsoft.com/kb/2596983 ETA: Week of December 19th. Now available (12/16/2011) . Description of the Office Project Server 2007 hotfix package (pjsrvapp-x-none.msp, pjsrvwfe-x-none.msp): December 13, 2011 http://support.microsoft.com/kb/2596989 Available Now! Description of the Project 2007 hotfix package (Project-x-none.msp): December 13, 2011 http://support.microsoft.com/kb/2596984
Description of the Windows SharePoint Services 3.0 hotfix package (Sts-x-none.msp): December 13, 2011 http://support.microsoft.com/kb/2596983
ETA: Week of December 19th. Now available (12/16/2011) .
Description of the Office Project Server 2007 hotfix package (pjsrvapp-x-none.msp, pjsrvwfe-x-none.msp): December 13, 2011
http://support.microsoft.com/kb/2596989
Description of the Project 2007 hotfix package (Project-x-none.msp): December 13, 2011
http://support.microsoft.com/kb/2596984
Deploy cumulative updates (Project Server 2007) http://technet.microsoft.com/en-us/library/dd239177.aspx Server Pack 3 for Project and Project Server 2007 has been released. While not required for the December CU, we strongly recommend that you install it as it contains a number of patches to improve performance and reliability. The following blog goes into more detail about SP3. Office 2007 and SharePoint 2007 Service Pack 3 Availability http://blogs.technet.com/b/office_sustained_engineering/archive/2011/10/25/office-2007-and-sharepoint-2007-service-pack-3-availability.aspx SP3 may be option, however, Service Pack 2 for both WSS and Office Servers 2007 are required for this Cumulative Update. 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 http://support.microsoft.com/kb/953338 Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2 http://support.microsoft.com/kb/953334 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 but they will greatly simplify MOSS patch deployment. Client Installation: In order to install this hotfix, you will need to have Microsoft Project 2007 SP2 installed on the client. Description of Office Project 2007 Service Pack 2 (SP2) and of Office Project Language Pack 2007 Service Pack 2 (SP2) http://support.microsoft.com/kb/953326 Once we know that SP2 is installed, you will install the hotfix by performing the following steps: NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout. Download the hotfix from either the KB Article or by using the information at the end of this email. Extract the patch package by running the .exe file that you downloaded. Run the extracted .exe file to apply the patch to your Project Professional/Standard SP1 client.
Deploy cumulative updates (Project Server 2007)
http://technet.microsoft.com/en-us/library/dd239177.aspx
Server Pack 3 for Project and Project Server 2007 has been released. While not required for the December CU, we strongly recommend that you install it as it contains a number of patches to improve performance and reliability. The following blog goes into more detail about SP3.
Office 2007 and SharePoint 2007 Service Pack 3 Availability
http://blogs.technet.com/b/office_sustained_engineering/archive/2011/10/25/office-2007-and-sharepoint-2007-service-pack-3-availability.aspx
SP3 may be option, however, Service Pack 2 for both WSS and Office Servers 2007 are required for this Cumulative Update. 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
http://support.microsoft.com/kb/953338
Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2
http://support.microsoft.com/kb/953334
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 but they will greatly simplify MOSS patch deployment.
In order to install this hotfix, you will need to have Microsoft Project 2007 SP2 installed on the client.
Description of Office Project 2007 Service Pack 2 (SP2) and of Office Project Language Pack 2007 Service Pack 2 (SP2)
http://support.microsoft.com/kb/953326
Once we know that SP2 is installed, you will install the hotfix by performing the following steps:
Feel free to open a support incident at http://support.microsoft.com if you run into any issues with the installation and we will be happy to help!
Great News! The latest Cumulative Updates (CU) for Project and Project Server 2010 and 2007 have been released. Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.
Feel free to join us in March for a TechNet webcast to go over these patches in greater detail. The information for this event is below:
TechNet Webcast: Information about Microsoft Project and Project Server February 2012 Software Update (Level 200)
https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032493966&Culture=en-US
There was an issue found with one of the other Office Server products which needed to be addressed before release. The issue has been fixed and the Server Rollup Packages are being rebuilt. We expect the patch to be released the week of March 5th.
Please note that the issue was not with the Project Server Individual Package so the Project Server CU (KB2597138) can be used for testing and/or rapid deployment for organizations who cannot wait for the Server Rollup Patch to be released.
You can read about the fixes included in the Project and Project Server February CUs from the following articles:
ETA: Week of March 5th
Description of the SharePoint Server 2010 and Project Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package, Project server-package): March 2012
http://support.microsoft.com/kb/2597152
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): February 28, 2012
http://support.microsoft.com/kb/2597138
Description of the Project 2010 hotfix package (project-x-none.msp): February 28, 2012
http://support.microsoft.com/kb/2597942
1. Download the hotfix from the link in the KB Article.
2. Extract the patch package by running the .exe file that you downloaded.
3. Run the extracted .exe file to apply the patch to your Project Professional/Standard client.
You can read about the fixes included in the February CU from the following articles:
Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): February 28, 2012
http://support.microsoft.com/kb/2597959
Description of the Office SharePoint Server 2007 Cumulative Update server hotfix package (MOSS server-package): February 28, 2012
http://support.microsoft.com/kb/2597958
Description of the SharePoint Server 2007 hotfix package (sts-x-none.msp): February 28, 2012
http://support.microsoft.com/kb/2597951
Description of the Project Server 2007 hotfix package (pjsrvapp-x-none.msp, pjsrvwfe-x-none.msp): February 28, 2012
http://support.microsoft.com/kb/2597960
Description of the Office Project 2007 hotfix package (project-x-none.msp):February 28, 2012
http://support.microsoft.com/kb/2597955
Server Pack 3 for Project and Project Server 2007 has been released. While not required for the February CU, we strongly recommend that you install it as it contains a number of patches to improve performance and reliability. The following blog goes into more detail about SP3.
SP3 may be optional, however, Service Pack 2 for both WSS and Office Servers 2007 are required for this Cumulative Update. The KB articles below provide information on how to download and install SP2 if you have not already done so.
1. Download the hotfix from either the KB Article.
3. Run the extracted .exe file to apply the patch to your Project Professional/Standard SP1 client.
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.
Description of the 2007 Microsoft Office servers Service Pack 1 and the 2007 Microsoft Office servers Language Pack Service Pack 1
http://support.microsoft.com/kb/936984/en-us
How to deploy the 2007 Microsoft Office servers Service Pack 1 and Office Server Language Pack 2007 Service Pack 1
http://support.microsoft.com/kb/945013/en-us
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.
Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): February 23, 2010
http://support.microsoft.com/kb/978396
Description of the Office SharePoint Server 2007 Cumulative Update Server Hotfix Package (MOSS server-package): February 23, 2010 (This includes Project Server 2007 CU)
http://support.microsoft.com/kb/978395
Description of the Windows SharePoint Services 3.0 Cumulative Update Server hotfix package (Sts-x-none.msp): February 23, 2010
http://support.microsoft.com/kb/978389
Description of the Office Project Server 2007 hotfix package (Pjsrvapp-x-none.msp, Pjsrvwfe-x-none.msp): February 23, 2010
http://support.microsoft.com/kb/978397
Description of the Office Project 2007 hotfix package (Project-x-none.msp): February 23, 2010
http://support.microsoft.com/kb/980209
Description of Project 2007 Service Pack 1 and of Project Language Pack 2007 Service Pack 1
http://support.microsoft.com/kb/937154/en-us
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
Mixed-Mode
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.
Project Server
Exclusively using Project Server accounts for authentication
Forms Authentication
Windows
Exclusively using Windows accounts for authentication
Windows 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
Description
SAML
This is essentially the same as Forms Authentication.
Multi-Auth
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:
http://blogs.msdn.com/spidentity/archive/2010/01/04/claims-based-authentication-cheat-sheet-part-1.aspx
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.
http://blogs.msdn.com/spidentity/archive/2010/01/23/claims-based-authentication-cheat-sheet-part-2.aspx
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:
http://technet.microsoft.com/en-us/library/cc288475(office.14).aspx
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.
*** Update *** Please see http://blogs.msdn.com/b/brismith/archive/2010/09/17/project-server-2010-applied-august-cu-and-having-problems-with-jsgrid.aspx if you are having issues with JSGrid after loading JUST the Project Server 2010 CU - KB 2276341
Yesterday saw the release of the August Cumulative Update (CU) for both Office 2007 and Office 2010 product families, including Microsoft Office Project Server 2007, Microsoft Office Project 2007, Microsoft Project Server 2010 and Microsoft Project 2010.
These include a number of fixes, so Microsoft strongly recommends that you evaluate in a test environment based on your production environment before putting this fix live in production.
Also do not forget the upcoming Webcast where Adrian Jenkins and Brian Smith will provide an overview of this release and also address related questions:
TechNet Webcast- Information About Microsoft Project and Project Server Cumulative August Update - Tuesday, September 14, 2010 8:00 AM Pacific Time (US & Canada)
The article below provides information on how to deploy the Project Server Cumulative Update. There is an article in the works for 2010, but basically the steps are the same.
The second version is the Server Rollup Packages. This is a set of rollup packages which contains (for 2007) 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.
For 2010 there are new combinations due to the fact that SharePoint Server 2010 is now a required feature. I will update this post once the articles are live with a better description of the rollups, but basically the Project Server rollup contains the SharePoint Server patches – but the Server Rollup no longer contains the Project Server patches
You can read about the fixes included in the August CU from the following articles:
Note: There may be a few days delay before all of the articles are published.
2007
Individual Product Packages: Description of the SharePoint Server 2007 hotfix package (sts-x-none.msp): August 31, 2010 http://support.microsoft.com/kb/2276469 Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp; Pjsrvwfe-x-none.msp): August 31, 2010 http://support.microsoft.com/kb/2276475 Description of the Office Project 2007 hotfix package (project-x-none.msp): August 31, 2010 http://support.microsoft.com/kb/2289175
2010
Individual Product Packages: Description of the SharePoint Foundation 2010 hotfix package (Sts-x-none.msp): August 31, 2010 http://support.microsoft.com/kb/2266423 Description of the SharePoint Server 2010 hotfix package (spswfe-x-none.msp, pplwfe-x-none.msp, osrchwfe-x-none.msp): August 31, 2010 - http://support.microsoft.com/kb/2276339 *** Update - If you load the Project Server 2010 hotfix 2276341 you will also need to load at least 2266423 listed above. http://blogs.msdn.com/b/brismith/archive/2010/09/17/project-server-2010-applied-august-cu-and-having-problems-with-jsgrid.aspx Description of the Project Server 2010 hotfix package (Wosrv-x-none.msp, Pjsrvwfe-x-none.msp, Osrv-x-none.msp): August 31, 2010 http://support.microsoft.com/kb/2276341 No August update for Microsoft Project 2007 Server Rollup Packages: *** Descriptions updated *** Description of the SharePoint Foundation 2010 Cumulative Update Server Hotfix Package (SharePoint Foundation server-package): August 31, 2010 - http://support.microsoft.com/kb/2352346 Description of the SharePoint Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package): August 31, 2010 - http://support.microsoft.com/kb/2352342 (Does not include Project Server patch) Description of the SharePoint Server 2010 and Project Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package, Project server-package): August 31, 2010 - http://support.microsoft.com/kb/2352345
*** Update - If you load the Project Server 2010 hotfix 2276341 you will also need to load at least 2266423 listed above. http://blogs.msdn.com/b/brismith/archive/2010/09/17/project-server-2010-applied-august-cu-and-having-problems-with-jsgrid.aspx
Server Rollup Packages: *** Descriptions updated ***
In order to install the 2007 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.
Feel free to join us in May for a TechNet webcast to go over these patches in greater detail. The information for this event is below:
TechNet Webcast: Information about Microsoft Project and Project Server April 2012 Software Update (Level 200) https://msevents.microsoft.com/CUI/EventDetail.aspx?culture=en-US&EventID=1032493968
You can read about the fixes included in the Project and Project Server April CUs from the following articles:
Description of the Project Server 2010 cumulative update package (Project server-package): April 24, 2012
http://support.microsoft.com/kb/2598152
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): April 24, 2012
http://support.microsoft.com/kb/2598272
Description of the Project 2010 hotfix package (Project-x-none.msp): April 24, 2012
http://support.microsoft.com/kb/2598274
You can read about the fixes included in the April CU from the following articles:
Description of the Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package): April 24, 2012
http://support.microsoft.com/kb/2598130
Description of the SharePoint Server 2007 Cumulative Update Server Hotfix Package (MOSS server-package): April 24, 2012
http://support.microsoft.com/kb/2598129
Description of the Windows SharePoint Services 3.0 hotfix package (Sts-x-none.msp): April 24, 2012
http://support.microsoft.com/kb/2598263
Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp, Pjsrvwfe-x-none.msp): April 24, 2012
http://support.microsoft.com/kb/2598131
Description of the Project 2007 hotfix package (Project-x-none.msp): April 24, 2012
http://support.microsoft.com/kb/2598264
Server Pack 3 for Project and Project Server 2007 has been released. While not required for the April CU, we strongly recommend that you install it as it contains a number of patches to improve performance and reliability. The following blog goes into more detail about SP3.
*** Update *** 11/18/2010 - The issues have now been resolved and the links to the revised updates are now available. The KB number is unchanged, but the Revision Number on the article is 2.0 and the version of the patch is 14.0.5128.5003. Sorry for any inconvenience caused. This only applies to KB 2394322 (link below) and 2394320 (which isn't in the links below)
***Update*** Please see the latest information on potential issues with the October CU at http://blogs.technet.com/b/projectadministration/archive/2010/11/08/critical-information-about-the-sharepoint-server-2010-october-cumulative-update.aspx
*** Update *** Reminder, the TechNet Webcast giving more details of this cumulative update:
Tuesday, November 09, 2010 8:00 AM Pacific Time (US & Canada), TechNet Webcast: Information About Microsoft Project and Project Server Cumulative October Update – with Adrian Jenkins and Brian Smith.
Great News! The latest Cumulative Updates (CU) for Project and Project Server 2010 and 2007 have been released. You can download them directly from the links in the KB articles.
As Project Server 2010 is now based on the MOSS we strongly recommend that you install the Server Rollup Packages as there are a large number of individual server packages for MOSS. There is a set of two rollup packages which contains all the fixes for SharePoint Foundation Server, MOSS and Project Server. Both Server Rollup Packages should be installed to ensure that the underlying technology that Project Server depends on is up to date.
For those accustomed to Project Server 2007 Cumulative Updates, you should note that the MOSS Server Rollup Package does not contain the Project Server patches. You will need to make sure that you install the MOSS + Project Server Rollup Package (the link is provided below). As in Project Server 2007, the Server Rollup Packages are much larger (~150MB each) but they will greatly simplify your Project Server patch deployment.
You can read about the fixes included in the October CU from the following articles:
Service Pack 2 for both WSS and Office Servers 2007 are required for this Cumulative Update. The KB articles below provide information on how to download and install SP2 if you have not already done so.
Note: The SP2 Requirement is new as of the August 2010 Project and Project Server 2007 Cumulative Updates.
The Server 2007 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 (~100MB each) but they will greatly simplify MOSS patch deployment.
Great News! The latest Cumulative Updates (CU) for Project and Project Server 2010 and 2007 have been released. There was a problem found in both the 2010 Server Rollup Packages which required a fix and for the patches to be rebuilt. The current guidance is that we should see it released during the week of 3/7/2010.(Oops - too eager with the cut and paste from February!) Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.
Additionally, you are welcome to join us on TechNet for a webcast where we will be discussing this issues in detail and answering questions regarding the February Cumulative Update. The information on this webcast can be found at the URL below.
TechNet Webcast: Information About Microsoft Project and Project Server May 2011 Software Update (Level 200)
https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032455143
Description of the SharePoint Server 2010 and Project Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package, Project server-package): April 26, 2011
http://support.microsoft.com/kb/2512801
Description of the Project Server 2010 hotfix package (pjsrvwfe-x-none.msp): April 26, 2011
http://support.microsoft.com/kb/2516483
Description of the Office Project 2010 hotfix package (project-x-none.msp): April 26, 2011
http://support.microsoft.com/kb/2516479
For those accustomed to Project Server 2007 Cumulative Updates, you should note that the MOSS Server Rollup Package does not contain the Project Server patches. You will need to make sure that you install the MOSS + Project Server Rollup Package (the link is provided below). As in Project Server 2007, the Server Rollup Packages are much larger but they will greatly simplify your Project Server patch deployment.
Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): April 26, 2011
http://support.microsoft.com/kb/2512783
Description of the Office SharePoint Server 2007 Cumulative Update server hotfix package (MOSS server-package): April 26, 2011
http://support.microsoft.com/kb/2512782
Description of the SharePoint Server 2007 hotfix package (sts-x-none.msp): April 26, 2011
http://support.microsoft.com/kb/2512780
Description of the Project Server 2007 hotfix package (pjsrvapp-x-none.msp, pjsrvwfe-x-none.msp):April 26, 2011
http://support.microsoft.com/kb/2512784
Description of the Office Project 2007 hotfix package (project-x-none.msp):April 26, 2011
http://support.microsoft.com/kb/2534046
Following the publication of the source code for the recently released Project 2010 content pack, we also published the source code of the project to automate the deployment procedure of the content pack on MSDN Code Gallery: http://code.msdn.microsoft.com/Project2010DemoPack.
One of the nugget it contains is the PowerShell script to automate the configurate of Secure Store Service (which is required for Excel Services 2010), and yes you can also follow the step by step procedure documented on TechNet: Configure reporting for Project Server 2010
Code is also here: http://gallery.technet.microsoft.com/ScriptCenter/en-us/a88f7b6e-9c9e-475f-afd1-c68c4ef3cc4a
$targetApplicationName = "ProjectServerApplication" $userName = "contoso\administrator" $password = "pass@word1" $url = "http://project.contoso.com/pwa" $grp1 = (New-Object System.Security.Principal.NTAccount("contoso", "domain users")).Translate([System.Security.Principal.SecurityIdentifier]).Value $memberclaims = New-SPClaimsPrincipal -Identity $grp1 -IdentityType WindowsSecurityGroupSid $pw = new-spsecurestoreapplicationfield -name "Password" -type WindowsPassword -masked:$false $un = new-spsecurestoreapplicationfield -name "User Name" -type WindowsUserName -masked:$false $fields = $un, $pw $proxy = Get-SPServiceApplicationProxy -identity "af18e4e8-3221-432f-b6cb-9e76a64d248c" $defaultServiceContext = Get-SPServiceContext $url $credentialTypes = "UserName","Password" $c1 = convertto-securestring $userName -asplaintext -force $c2 = convertto-securestring $password -asplaintext -force $credentialValues = $c1,$c2 $pkmacctclaims = New-SPClaimsPrincipal -Identity $userName -IdentityType WindowsSamAccountName $app = new-spsecurestoretargetapplication -name $targetApplicationName -friendlyname $targetApplicationName -contactemail "administrator@contoso.com" -applicationtype Group -timeoutinminutes 3 -setcredentialsuri "http://ipserver2" new-spsecurestoreapplication -ServiceContext $defaultServiceContext -TargetApplication $app -Administrator $pkmacctclaims -CredentialsOwnerGroup $memberClaims -Fields $fields $ssoapp = Get-SPSecureStoreApplication -ServiceContext $defaultServiceContext -Name $targetApplicationName [System.Threading.Thread]::Sleep(10000) Update-SPSecureStoreGroupCredentialMapping -Identity $ssoapp -Values $credentialValues Update-SPSecureStoreApplicationServerKey -Passphrase pass@word1 -ServiceApplicationProxy $proxy
Great News! The latest Cumulative Update (CU) has been released: April 2010. 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.
The article below provides information on how to deploy the Project Server Cumulative Update: Deploy cumulative updates (Project Server 2007) http://technet.microsoft.com/en-us/library/dd239177.aspx
Also check this blog post for more information: February 2010 Cumulative Update (CU) for Project Server 2007, Office SharePoint Server 2007, WSS and Project 2007 now available!
Following a two month cycle, next Cumulative Update is due at the end of June 2010.
Thanks to the TechNet writer’s team Project Server 2010 Administrator's Guide NOW AVAILABLE! A great asset for all project administrators.
Table Of Content:
Hello to announce the release of the Microsoft Project Server 2010 Server Settings Backup/Restore tool (also referred to as Playbook): http://technet.microsoft.com/en-us/library/gg128952.aspx
The Microsoft Project Server 2010 Server Settings Backup/Restore tool is part of the Project Server 2010 Project Resource Kit (PRK). It enables Project Server 2010 administrators to back up server settings from a selected Project Server 2010 instance to an XML or binary .playbook file. The tool can then restore the server settings to another Project Server 2010 instance. The data from the exported XML (or binary) file is what is imported to the target Project Server 2010 instance. This tool can be especially useful when you move server settings from a test to a production environment, but could also be used to generate a simple “playbook” of custom fields and views (for example, for different industries). You can access the Project Server 2010 Server Settings Backup/Restore tool by downloading the Project 2010 PRK from the Microsoft Download Center.
The Microsoft Project Server 2010 Server Settings Backup/Restore tool is part of the Project Server 2010 Project Resource Kit (PRK). It enables Project Server 2010 administrators to back up server settings from a selected Project Server 2010 instance to an XML or binary .playbook file. The tool can then restore the server settings to another Project Server 2010 instance. The data from the exported XML (or binary) file is what is imported to the target Project Server 2010 instance. This tool can be especially useful when you move server settings from a test to a production environment, but could also be used to generate a simple “playbook” of custom fields and views (for example, for different industries).
You can access the Project Server 2010 Server Settings Backup/Restore tool by downloading the Project 2010 PRK from the Microsoft Download Center.
*** Update - Thanks Tony for pointing out the link is for an old June CU - I'll update once I have fresh information... ***
Feel free to join us in July for a TechNet webcast to go over these patches in greater detail. The information for this event is below:
TechNet Webcast: Information About Microsoft Project and Project Server Cumulative June Update (Level 200)
https://msevents.microsoft.com/CUI/EventDetail.aspx?culture=en-US&EventID=1032454430&CountryCode=US
*** Update - all patches now available - sorry for the delay ***
There was an issue found with one of the other Office Server products which needed to be addressed before release. The issue has been fixed and the Server Rollup Packages are being rebuilt. We expect the patch to be released the first week of July.
Please note that the issue was not with the Project Server Individual Package so the Project Server CU (KB2598375) can be used for testing and/or rapid deployment for organizations who cannot wait for the Server Rollup Patch to be released.
You can read about the fixes included in the Project and Project Server June CUs from the following articles:
ETA: First week of July *** Update - Now available! ***
Description of the Project Server 2010 cumulative update package (Project server-package): June 26, 2012
http://support.microsoft.com/kb/2598355
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): June 26, 2012
http://support.microsoft.com/kb/2598375
*** Update***
Additional package - see http://blogs.msdn.com/b/brismith/archive/2012/07/20/project-server-2010-duplicated-outlook-tasks-after-exchange-sync-june-cu.aspx for full details.
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp, Pjsrvmui-x-none.msp): June 26, 2012
http://support.microsoft.com/kb/2598376
(Includes all of 2598375 + and Exchange Sync fix and a Category Editing fix. These needed globalization changes hence the separate fix))
*** End Update ***
Description of the Project 2010 hotfix package (Project-x-none.msp): June 26, 2012
http://support.microsoft.com/kb/2598351
Description of the Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package): June 26, 2012
http://support.microsoft.com/kb/2687257
Description of the SharePoint Server 2007 Cumulative Update Server Hotfix Package (MOSS server-package): June 26, 2012
http://support.microsoft.com/kb/2687256
Description of the Windows SharePoint Services 3.0 hotfix package (Sts-x-none.msp): June 26, 2012
http://support.microsoft.com/kb/2598389
Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp, Pjsrvwfe-x-none.msp): June 26, 2012
http://support.microsoft.com/kb/2687258
Description of the Project 2007 hotfix package (Project-x-none.msp): June 26, 2012
http://support.microsoft.com/kb/2687253
Server Pack 3 for Project and Project Server 2007 has been released. While not required for the June CU, we strongly recommend that you install it as it contains a number of patches to improve performance and reliability. The following blog goes into more detail about SP3.
*** Update November 2011 *** With the recent release of Project Server Service Pack 1 and recent IE9 updates, Project 2010 is now fully compatible with IE9
Internet Explorer (IE) 9 was launched on Monday, March 14th. We have been working very closely with the Internet Explorer (IE) team to ensure that our customers can take advantage of all the great new features that the new IE release offers. After testing the different versions of Microsoft Project Server with IE 9, here is an update on IE 9 support status:
There is a small known issue with editing some of the grids in Project Server 2007 and Project Server 2010. When the entire contents of an editable cell are deleted, that cell becomes un-editable until the page is refreshed. Therefore, when modifying the content of a cell, you must ensure that all the content of the cell is not completely removed. To completely replace the contents of the cell, select the whole text and replace that with the new string. This issue affects the grid on the following pages:
Microsoft Office Project Server 2007
Microsoft Project Server 2010
There are also known issues with changing a project owner in the project information page, and adding or removing project fields in project detail pages. We are working across IE and Microsoft Project teams to fix all these issues soon. We will update when the fixes are available.
The August 2011 Cumulative Updates for Microsoft Project and Project Server 2010 have now been released. *** Update 9/7/2011 - rollup package now posted **** We did find a late issue with the SharePoint Foundation CU during our testing which we have identified and will need to re-build. This does however mean that the server rollup patches will be delayed too – as they contain the SharePoint Foundation bits. The current estimate is that these rollup packages will be available late next week. The server rollup patch is the preferred patch because it contains the fixes for all of the server technologies used by Project Server 2010 The individual server patch is available should you need an August fix for Project Server before next week. It should also allow you to start testing the Project specific fixes right away.
This delay does not affect the August 2011 Cumulative Update for Project and Project Server 2007.
As always, we want to encourage you to test any CUs with a recent copy of your production database before deploying into production so that we can catch any problems, and fix them, in test before they start impacting a live environment.
We should also remind you that we recommend applying Service Pack 1 - http://technet.microsoft.com/en-us/library/hh272536.aspx. This article makes many references to the June CU – the August CU is cumulative so does contain all that was shipped in the June CU so if you haven’t installed the June CU then you can just install the August CU (and SP1). More details of SP1 can be found at http://blogs.msdn.com/b/project/archive/2011/06/28/announcing-the-release-of-service-pack-1-sp1-for-microsoft-project-and-project-server-2010.aspx and the downloads listed at http://support.microsoft.com/kb/2510766. Q&A from the SP1 TechNet webcast can be found at http://blogs.msdn.com/b/brismith/archive/2011/07/11/project-server-2010-sp1-and-june-cu-questions-and-answers.aspx.
So without any further ado, here is the information:
(ETA 9/9/2011)
Description of the SharePoint Server 2010 and Project Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package, Project server-package): August 30, 2011
http://support.microsoft.com/kb/2553049
Description of the Project Server 2010 hotfix package (pjsrvwfe-x-none.msp): August 30, 2011
http://support.microsoft.com/kb/2553047
Description of the Project 2010 hotfix package (project-x-none.msp): August 30, 2011
http://support.microsoft.com/kb/2584056
Description of the Windows SharePoint Services 3.0 cumulative update package (WSS server-package): August 30, 2011
http://support.microsoft.com/kb/2553022
Description of the Office SharePoint Server 2007 cumulative update package (MOSS server-package): August 30, 2011
http://support.microsoft.com/kb/2553020
Description of the Office SharePoint Server 2007 hotfix package (sts-x-none.msp): August 30, 2011
http://support.microsoft.com/kb/2553019
Description of the Office Project Server 2007 hotfix package (pjsrvapp-x-none.msp, pjsrvwfe-x-none.msp): August 30, 2011
http://support.microsoft.com/kb/2553024
Description of the Office Project 2007 hotfix package (project-x-none.msp):August 30, 2011
http://support.microsoft.com/kb/2553105
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.
http://technet.microsoft.com/en-us/office/ee691939.aspx
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.
Database, database, database, yes there are plenty of them and guess what you need to maintain them for optimal performance! A MUST read for all farm admin, and I hope you all carefully implement maintenance plans: Database Maintenance for Microsoft SharePoint 2010 Products
This white paper provides information and guidelines for maintaining the databases that host Microsoft® SharePoint® 2010 data and configurations. It describes and provides examples of the database maintenance tasks that we recommend when using SharePoint 2010.
Yes we are currently on updating our Project Server 2010 database guidance as well, in the meantime this is a great starting point: Database maintenance plans for Project Server 2007
Must read prior to any production rollout: Estimate Performance and Capacity Requirements for Microsoft Project Server 2010.
This performance and capacity planning document provides guidance on the footprint that usage of Microsoft Project Server 2010 has on topologies running Microsoft SharePoint Server 2010.
More information around performance and capacity planning for Project Server 2010 can be found on TechNet: http://technet.microsoft.com/projectserver
Additionally check out all the Microsoft Project 2010 Ignite videos released today, plenty of IT Pro content you all need to know: Microsoft Project 2010 Ignite Online Recordings Are Live!
Great News! The latest Cumulative Updates (CU) for Project and Project Server 2010 and 2007 have been released. There was a problem found in both the 2010 Server Rollup Packages which required a fix and for the patches to be rebuilt. The current guidance is that we should see it released during the week of 3/7/2010. Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.
TechNet Webcast: Information About Microsoft Project and Project Server Cumulative February Update (Level 200)
https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032455141
As Project Server 2010 is now based on the MOSS we strongly recommend that you install the Project Server 2010 Server Rollup Package as there are a large number of individual server packages for MOSS. The Project Server 2010 Server Rollup Package contains all the patches released in this Cumulative Update for SharePoint Foundation Server 2010, SharePoint Server 2010 and Project Server 2010.
There was a problem found in the one of the Office Server packages which means that it has to be fixed and rebuilt. You can download the individual Project Server 2010 Cumulative Update and install it so that you can start testing or have the patched deployed now. You could then install the Office Server 2010 Server Rollup Package over the individual Project Server package to update all of the SharePoint and other Office Servers files.
Server Rollup Package:
ETA - The week of March 7th, 2011
Description of the SharePoint Server 2010 and Project Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package, Project server-package): February 22, 2011
http://support.microsoft.com/kb/2475879
Description of the Project Server 2010 hotfix package (pjsrvwfe-x-none.msp): February 22, 2011
http://support.microsoft.com/kb/2479792
Description of the Office Project 2010 hotfix package (project-x-none.msp): February 22, 2011
http://support.microsoft.com/kb/2496946
Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): February 22, 2011
http://support.microsoft.com/kb/2475886
Description of the Office SharePoint Server 2007 Cumulative Update server hotfix package (MOSS server-package): February 22, 2011
http://support.microsoft.com/kb/2475885
Description of the Windows SharePoint Services 3.0 hotfix package (sts-x-none.msp): February 22, 2011
http://support.microsoft.com/kb/2483218
Description of the Project Server 2007 hotfix package (pjsrvapp-x-none.msp, pjsrvwfe-x-none.msp): February 22, 2011
http://support.microsoft.com/kb/2475887
Description of the Office Project 2007 hotfix package (project-x-none.msp):February 22, 2011
http://support.microsoft.com/kb/2483215
1. Download the hotfix from either the KB Article or by using the information at the end of this email.