I am pleased to announce the release of the February 2013 Cumulative Update (CU) for Project, Project Server and SharePoint for 2007, 2010 and the very first one for 2013. Also you may notice this is earlier in the month, and since December 2012 we are planning to ship the Office Cumulative updates on the 2nd Tuesday (“Patch Tuesday”) of the even months. 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. In most of the KB articles the term hotfix is used in place of Cumulative Update. They tend to be interchangeable terms – a Cumulative Update is just a hotfix built to a schedule.
There is a slight delay on the SharePoint/Project Server package – more details as soon as I have them.
***Update 3/18 - please see http://blogs.technet.com/b/projectsupport/archive/2013/03/18/project-server-2013-march-public-updates.aspx for the Project Server 2013 update ***
Project 2013 Client Package:
Description of the Project 2013 hotfix package (Project-x-none.msp): February 12, 2013
We are working on the specific CU installation options for 2013, but the process hasn’t changed from 2010 – so if you are familiar with 2010 patching or read the 2010 instructions below you should be good to go.
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 February CUs from the following articles:
Server Rollup Package(Recommended):
Description of the Project Server 2010 cumulative update package (Project server-package): February 12, 2013
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): February 12, 2013
The version number is 14.0.6134.5000 *** Update 2/15 *** and you can also expect to see the databases updated to this version number. but there are no database updates - so the DB should upgrade to 14.0.6131.5000 if it wasn't already at that level - sorry for any confusion.
Project 2010 Client Package:
Description of the Project 2010 hotfix package (Project-x-none.msp): February 12, 2013 (The title may say “Project Server 2010”, and there are some other references to '”server” – just getting this corrected, but this is definitely the client CU.
The version number is 14.0.6134.5000, in case you want to limit the connection of certain patched release to Project Server 2010.
More information on deploying the Cumulative Update:
Updates for Project Server 2010
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 http://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 http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=26636
SP1 for the Project Professional 2010 client can be found at http://www.microsoft.com/en-us/download/details.aspx?id=26635 for the 32-bit and http://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.
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
No fixes this month for Project Server 2007 – but listing the WSS and SharePoint patches for reference. 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 February CU from the following articles:
Server Rollup Packages: Listing the WSS and SharePoint roll-up packages, but as there are no fixes for Project Server these do not include them.
Description of the Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package): February 12, 2013
Description of the SharePoint Server 2007 cumulative update server hotfix package (MOSS server-package): February 12, 2013
Individual Product Packages:
Project 2007 Client Package:
Description of the Project 2007 hotfix package (Project-x-none.msp): February 12, 2013
Deploy cumulative updates (Project Server 2007)
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
Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2
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)
Once we know that SP2 is installed, you will install the hotfix by performing the following steps:
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.
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!
Hi, Thanks so much for this post. See if you can help: I have Project Professional 2010 with no CU nor Service Pack. What do I need to install so I can have all the latest updates? And how do I keep it always current?
Sorry if there is any post already mentioning it, as I'm new arround here.
Thanks in advance!
Hi Anderson Oliveira,
You can load Project Professional SP1 (listed above) and the February CU from the posting above and you will be up to date. To keep up to date load the Cumulative updates which comes out every 2 months - and SP2 which will be out shortly, and any security fixes that we might send out via the public update mechanism.
Am I correct in assuming that if we apply this CU for Project 2010 Project, it will apply all prior hotfixes released since SP1? If not, is there a comprehensive list of hotfixes by date that should be applied and in what order?
I ask because I'm further assuming that there are some hotfixes that roll-up previous hotfixes, and that it's not the case that we simply have to go down the line chronologically from that point.
This hotfix process is so damn aggravating without a central list!!
As per Brian's response above, if you load SP1 and the February CU, you will be up to date.
For previous versions, you can also refer to the link below. It goes until June 2011, but it is the best list I could find in internet
There is this other one, but it is in spanish. At least it goes until June 2012
Hope this helps.
I finaly was able to install the CU and SP1 at my company. The version it shows is like this:
Microsoft Project 2010 (14.0.6134.5000) SP1 MSO (14.0.6108.5000).
Although I could find the first code, I couldnt fine the second one. Would you confirm if the version I have for SP1 is correct?
Hi Anderson, MSO is the shared code that Project uses from the core Office family - so sometimes you will see the second number increment when another Office Cumulative Update (CU) or Public Update (PU - normally the monthly security patches) is applied. The site at support.microsoft.com/.../2121559 gives the versions for Service Packs - and by searching on MSO and the version you posted this looks like August 2011 hotfix for the general Office components.
My name is Mohamed from Expit, I wanted to share with everyone background info about a product we released sometime back. It’s a connector for Microsoft project that allows users to integrate MS Project professional 2010 with Microsoft System Center Services Manager 2012 (SCSM). The product is freely available at www.expit.com/ProjectConnector.aspx
It basically allows users to convert workflow templates in SCSM into task sequences in project. The connector also syncs project tasks as tickets into SCSM. Please check it out and let us know what you would with for in the next release, we are in the process of building a new edition to cater for the greater community wish list of features.
Thanks for the clarification on this as the update process is a bit confusing. It would be a big help if you continued to post an announcement with each new CU - just a shameless plug. :)
I do still have one question. Should both the Office and the Project build numbers be in parity? For example, would the most up to date build be Microsoft Office Project 2010 14.0.6134.5000 SP1 MSO 14.0.6134.5000?