Microsoft Project Server and SharePoint Server 2007 and 2010 October 2012 CU Announcement
I am pleased the announce the release of (some of) the 2012 October Cumulative Update for Project 2010, Project Server 2007, Project Server 2010, SharePoint Server 2007 and SharePoint Server 2010. There are no fixes affecting Project 2007 client this cycle. Some of the packages listed below will be delayed, as noted. Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed. Remember that this release for the 2010 products, like the August 2012 Cumulative Update, has a hard requirement on Service Pack 1 – see notes below.
*** Update 11/7/2012 - the 2007 Server packages are now available ***
*** Update 11/14/2012 - see https://blogs.msdn.com/b/brismith/archive/2012/11/14/project-server-2007-issue-installing-the-october-2012-cumulative-update.aspx for details on some issues found with the 2007 CU ***
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.
The article below provides information on how to deploy the Project Server Cumulative Update.
You can read about the fixes included in the Project and Project Server August CUs from the following articles:
Server Rollup Package(Recommended): Delayed for a couple more weeks *** Update 11/15/2012 - now available ***
Description of the Project Server 2010 cumulative update package (Project server-package):
https://support.microsoft.com/kb/2687565
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): October 30, 2012
https://support.microsoft.com/kb/2687615
Project Client Package:
Description of the Project 2010 hotfix package (Project-x-none.msp): October 30, 2012
https://support.microsoft.com/kb/2687612
More information on deploying the Cumulative Update:
The article below provides information on how to deploy the Project Server Cumulative Update.
Updates for Project Server 2010
https://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.
As mentioned above, and at https://blogs.msdn.com/b/brismith/archive/2012/07/18/project-server-2010-from-august-2012-cumulative-update-onwards-you-will-also-need-to-load-sp1.aspx – the August Cumulative Update requires your client and server to already be at the Service Pack 1 (SP1) level – if you get a message saying the patch does not apply to your system then this may be the reason.
SP1 for the Project Server 2010 can be found at https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=26636
SP1 for the Project Professional 2010 client can be found at https://www.microsoft.com/en-us/download/details.aspx?id=26635 for the 32-bit and https://www.microsoft.com/en-us/download/details.aspx?id=26627 for the 64-bit.
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.
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.
Project Server 2007 (*** See note above for details of a problem found with the Project Server 2007 CU***)
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 August CU from the following articles:
Server Rollup Packages:
Description of the Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package): October 30, 2012
https://support.microsoft.com/kb/2687535
Description of the SharePoint Server 2007 cumulative update server hotfix package (MOSS server-package): October 30, 2012 Delayed for a couple more weeks
https://support.microsoft.com/kb/2687533
Individual Product Packages:
Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp, Pjsrvwfe-x-none.msp): October 30, 2012 Delayed for a couple more weeks
https://support.microsoft.com/kb/2687536
There are no fixes for Project 2007 in this cycle.
More information on deploying the Cumulative Update:
The article below provides information on how to deploy the Project Server Cumulative Update.
Deploy cumulative updates (Project Server 2007)
https://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 August 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
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.
Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2
https://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
https://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: (For reference – there were no fixes released for Project 2007 client in this cycle)
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)
https://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.
1. Download the hotfix from either 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 SP1 client.
Feel free to open a support incident at https://support.microsoft.com if you run into any issues with the installation and we will be happy to help!
Comments
Anonymous
January 01, 2003
I hear you Mike - it is always difficult knowing if it is worth announcing - particularly when so much is delayed - but for some customers who are expecting the release on the last Tuesday of the month hearing it is delayed is more useful than hearing nothing. Also as I am able to share the URLs then if it does get released at say, 9pm on a Friday night, it could help someone over a weekend rather than waiting for me to be available to get the post done. The extra challenge with this CU is that the December one will be shipping earlier in the month - I can certainly see some customers may well choose to wait and install that one as they are so close together. Also I know of many customer who want the roll-up package to install - but for testing a specific fix then the individual package still has its use. Best regards, Brian.Anonymous
January 01, 2003
Hi Mike, this doesn't ring any bells. I'd suggest opening a support incident - or pinging me offline if you already have one open at Brian.Smith@Microsoft.com. and I can follow up on this. Best regards, Brian.Anonymous
November 06, 2012
Why announce now when several downloads are not available? Why not wait until everything you announce IS available?Anonymous
November 08, 2012
Hello, Brian. Are you looking for a fix at the "error"(including the red bar above) when saving certain tasks in the Timesheet? Two of our clients and ourselves are facing this issue. No information under ULS logs are provided, i could assure you i've inspected everything there. It simply doesn't allow to save the timesheet even after its deletion or task re-assignment. Any news? Regards, Mike