Microsoft Project Server 2010 and 2013 November 2014 CU Announcement


I am very pleased to announce the release of the November 2014 Cumulative Update (CU) for Project, Project Server and SharePoint for 2013, and Project and Project Server and SharePoint 2010.  Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed. At the time of posting not all of the KB articles are live.

This release for the 2010 products, has a hard requirement on Service Pack 2 – see notes below, (Support for Microsoft Office 2010 Service Pack 1 ended on 10/14/14).  Don’t forget language packs SP2 if you have any language packs loaded!  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.  I should also point out that the individual Project Server packages are only ‘individual’ in the sense that they do not include the SharePoint patches – they are still cumulative and the November CU will contain all previous CU releases (at least back to the applicable baseline. 

Another important point to add here is that there was an issue early last year running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April 2013 or later– so a good practice would be to load SP1, then the November 2014 CU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

Project and Project Server 2013

An overview of all the Office 2013 releases for November 2014 can be found here – Url TBD - Office 2013 cumulative update for November 2014

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 November CUs from the following articles:

Project Server 2013 Server Rollup Package

November 11, 2014 Cumulative Update for Project Server 2013 package

http://support.microsoft.com/kb/2889949

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes):

Hotfix KB 2899547 for Project Server 2013 November 11, 2014

http://support.microsoft.com/kb/2899547

The dbo.Versions table should show 15.0.4667.1000 after applying the November2014 CU.  The version number 15.0.4667.1000 can be used to control the connecting client to the November 2014 level, but only if you are loading the November CU to the server and client.  This version control no longer blocks server side scheduling engine, but as this fix is server side you cannot use a higher value until you have this server patch.

SP1 for Project Server 2013 can be hound here - http://support.microsoft.com/kb/2880553

Project 2013 Client Package:

Hotfix KB2899569 for Project 2013 November 11, 2014 (Project-x-none.msp)

http://support.microsoft.com/kb/2899569 

The client version number will be 15.0.4667.1000 and as this matches the server scheduling engine version this can be used if you want to restrict the client version that can connect to the server – assuming of course that you have upgraded the server to the November CU too.  If not then follow the suggested version number for the server patch level you are running.  See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details.  As mentioned above – the version number entered no longer controls the server side scheduling engine – so from this release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

We are working on the specific CU installation documentation 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.

SP1 for Project Professional 2013 can be found here - http://support.microsoft.com/kb/2817433

Also note that Click to Run installations will be automatically patched (mine updated today to the same version as above).  Installations in Enterprise Environments that have been modified will be deployed based on the schedule determined by your Administrator.  See http://support2.microsoft.com/gp/office-2013-click-to-run.

Project and Project Server 2010

An overview of all the Office 2010 releases for November 2014 can be found here – Url TBD - Office 2010 cumulative update for November 2014

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 November CUs from the following articles:

Project Server 2010

Project Server 2010 Individual package (cumulative – but just the Project Server 2010 fixes)

Hotfix KB2899537 for Project Server 2010 November 11, 2014 (Pjsrvwfe-x-none.msp)

http://support.microsoft.com/kb/2899537

Localization fixes (this one will highlight if you haven’t loaded the language pack SP2 yet!)

http://support.microsoft.com/kb/2899549

Project Server roll-up package

Hotfix KB2899479 for Project Server 2010 November 11, 2014

http://support.microsoft.com/kb/2899479

The Project Server database version will be updated to 14.0.7137.5000 after applying this or the package hotfix above, and running the configuration wizard.

Project 2010 Client Package:

Hotfix KB2899539 for Project 2010 November 11, 2014 (Project-x-none.msp)

http://support.microsoft.com/kb/2899539

The client version number is 14.0.7136.5000, in case you want to limit the connection of certain patched release to Project Server 2010.

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 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 (when available) 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 the November 2014 Cumulative Update requires your client and server to already be at the Service Pack 1 (SP2) level – if you get a message saying the patch does not apply to your system then this may be the reason – the message may be “expected version of the product was not found”

SP2 for the Project Server 2010 can be found at Service Pack 2 for Microsoft SharePoint and Project Server 2010 (KB2687452)and a description at SP2 at Description of Project Server 2010 SP2.  If you have language packs installed then these will also need to be patched to SP2 or the message above will be seen – SP2 for the server language packs can be found at Download the Microsoft Office Servers 2010 Language Pack Service Pack 2 package now and a description at http://support.microsoft.com/kb/2687462.

SP2 for the Project Professional 2010 client can be found at http://www.microsoft.com/en-us/download/details.aspx?id=39669 for the 32-bit and http://www.microsoft.com/en-us/download/details.aspx?id=39661 for the 64-bit and a description at http://support.microsoft.com/kb/2687457

Client Installation:

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.

Comments (0)

Skip to main content