A user contacted me via email the other day with a simple question - "Where can I get all the KB articles for Project Server 2010 and Project 2010 client fixes from June 2011 to February 2012?" The user said that, ideally, a spreadsheet including all fixes in those CUs would be the most useful.
CUs for Project Server are cumulative, so the latest CU includes all the fixes from all the CUs prior. For example, take the April 2012 CU announcement on the Project Admin Blog. If you go to the link for the April 2012 Project Server 2010 CU, there is a section titled "Issues that this hotfix package fixes". Each CU will have this section and that section will detail what has been corrected with each CU. There is no spreadsheet I am aware of that lists all CUs fixes since a certain service pack, so you have to read each CU's KB article to determine what's fixed. Then, you can plan out your testing to hit those issues if you have been affected by them or want to increase your confidence level that the CU actually fixes what it says it fixes.
Because the CU releases are all announced on the Project Admin Blog, you can search that blog for "CU Announcement".
Doing so resulted in links to
August 2011 http://blogs.technet.com/b/projectadministration/archive/2011/09/01/microsoft-project-server-and-sharepoint-2007-and-2010-august-cu-2011-announcement.aspx
October 2011 http://blogs.technet.com/b/projectadministration/archive/2011/11/02/microsoft-project-server-and-sharepoint-2007-and-2010-october-cu-2011-announcement.aspx
December 2011 http://blogs.technet.com/b/projectadministration/archive/2011/12/14/microsoft-project-server-and-sharepoint-server-2007-and-2010-december-2011-cu-announcement.aspx
February 2012 http://blogs.technet.com/b/projectadministration/archive/2012/02/29/microsoft-project-server-and-sharepoint-server-2007-and-2010-february-2012-cu-announcement.aspx
April 2012 http://blogs.technet.com/b/projectadministration/archive/2012/04/27/microsoft-project-server-and-sharepoint-server-2007-and-2010-april-2012-cu-announcement.aspx
If you are interested in post upgrade validation testing for Project Server 2010, use the links below to test functionality in your test environment (you do have a test environment, right?) after an upgrade on a Project Server with a copy of production data on it.
You can perform initial testing using the “Initial use setup”. Consider using an automated testing tool if human resources are hard to come by to reduce the validation testing window. After you complete the above checks, proceed to the following series of tests. Document the results.
Full Functionality Validation Testing Links are here:
Ok. If it's a CU why does the KB says "This hotfix does not replace a previously released hotfix" - yet it has?
Thanks Brooks, Do you have any idea on April 2012 CU which was called off. When will it be ready to download?
The April 2012 CU is ready to download now. I checked the Project Server Admin blog and there was an article posted by Brian Smith about a month ago. The link for the Project Server 2010 cumulative update package included the following section:
A recent, isolated issue was discovered in the SharePoint 2010 Products April 2012 Cumulative Update that could result in an HTTP 500 error when users delete objects to include documents, lists, and Webs and a new object is created using the same path where the original object remains in the Recycle Bin. The following packages were affected:
KB2598151 - SharePoint Server Package
KB2598152 - Project Server Package
KB2598321 - SharePoint Foundation Package
KB2598304 – Wss-x-none.msp
This issue has been resolved in the revised packages. The revised packages include support for resolving issues related to the originally published updates.
You asked "If it's a CU why does the KB says "This hotfix does not replace a previously released hotfix" - yet it has?"
The "Description of the Project Server 2010 cumulative update package (Project server-package): April 24, 2012" link at support.microsoft.com/.../2598152 is clear that there was an update to the hotfix package to correct a problem. Farther down the same article, in the Resolution section, the article does state that the hotfix does not replace a previously released hotfix, which is incorrect. I will request the hotfix article be corrected.
Brook. Thanks but the same can be said for all/other Office 2010 applications [desktop and server].