Microsoft Project Server 2010 and 2013 February 2015 PU Announcement


I am very pleased to announce the release of the February 2015 Public Update (PU) for Project, Project Server and SharePoint for 2013, and Project and Project Server and SharePoint 2010.  This is the first time all the updates have been included in a PU – rather than a Cumulative Update (CU) for some fixes and Public Update for others.  These are still cumulative.

The downloads will be available via the Windows Update service and from the Download Center – and the links will be found on the KB articles listed below.  At the time of writing I am seeing the patches available from Windows Update, but some of the Download Center links are not live quite yet.  Server rollup packages will only be available from the Download Center.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

The 2013 PU releases also have a prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below.

This release for the 2010 products, like the November CU, 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 February PU 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 February 2015 PU 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 February 2015 can be found here – http://support.microsoft.com/kb/3032763Description of the Office updates: February 10, 2015

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

Project Server 2013 Server Rollup Package

As mentioned above – this rollup package will only be available via the Download Center – not Windows Update.

February 10, 2015 cumulative update for Project Server 2013 (KB2920796)

http://support.microsoft.com/KB/2920796

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

February 10, 2015 update for Project Server 2013 (KB2880996)

http://support.microsoft.com/KB/2880996

The dbo.Versions table should show 15.0.4693.1000 after applying the February 2015 PU.  The version number 15.0.4693.1000 can be used to control the connecting client to the February 2015 level, but only if you are loading the November CU or more recent to the server.  This version control no longer blocks server side scheduling engine since the November CU, but as this fix is server side you cannot use a higher value until you have this server patch or a more recent one.

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

Project 2013 Client Package:

February 10, 2015 update for Project 2013 (KB2956091) (Ignore the mention of April 2014 in the KB text – just a typo…)

http://support.microsoft.com/KB/2956091

The client version number will be 15.0.4693.1000 (I see 15.0.4693.1001 on my click to run Project Pro for Office 365).  The server scheduling engine is no longer blocked by version control since the November CU on the server, so providing you have November 2014 CU ort above on the server you can use the 15.0.4693.1000 value to control connection of the February 2015 PU patched client..  If you are running a server CU earlier than November 2014 CU 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 the November 2014 CU 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 February 2015 can be found here http://support.microsoft.com/kb/3032763Description of the Office updates: February 10, 2015

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

Project Server 2010

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

February 10, 2015 update for Project Server 2010 (KB2881024)

http://support.microsoft.com/KB/2881024

Project Server roll-up package

February 10, 2015 cumulative update for Project Server 2010 (KB2899557)

http://support.microsoft.com/KB/2899557

The Project Server database version is not updated with the February 2015 PU, but if you were running an earlier release than November 2014 you will see the version updated to 14.0.7137.5000 after applying this or the package hotfix above, and running the configuration wizard.

Project 2010 Client Package:

February 10, 2015 update for Project 2010 (KB2589387)

http://support.microsoft.com/KB/2589387

The client version number is 14.0.7141.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, the November 2014 Cumulative Update and above 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.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Comments (6)

  1. anonymouscommenter says:

    Brian in an earlier posting (November I think) you responded to an inquiry about SQL 2014 being supported for use with Project Server 2013. I think you suggested that SQL 2014 would work with Project Server 2013 and that the documentation was being updated
    to reflect that change. I haven’t seen or found anything since then. Is there any additional information available that you can share?

    Thanks

  2. anonymouscommenter says:

    Hi Brian. In the blog about user permissions sync changes, you mention the permissions sync issue that is fixed in this update. Can you talk about what the fix is doing behind the scenes (any specific SQL stuff happening for this fix)? I’m curious how
    the CU fix differs from the workaround I needed when the ULS logs and queue logs seem to be similar.

  3. anonymouscommenter says:

    Hi Brian, where can we find the release schedule for the updates to appear in Project Online?

  4. DonOfBran says:

    I think the site @
    http://blogs.technet.com/b/projectsupport/p/ps10cu.aspx has the rollup/individual links reversed.

  5. Thanks Don – good catch! I’ve swapped them now.
    Jim, there isn’t a schedule – and all the same fixes don’t necessarily get fixed in Project Online and Project Server at the same time – or even at all.
    Aaron – I’ll need to investigate a bit deeper to know exactly what we fixed there, and finally Lou – SP1 added support for SLQ Server 2014 and the documents have finally been updated – see
    https://technet.microsoft.com/en-us/library/ee683978.aspx.

  6. anonymouscommenter says:

    Hi Brian,
    Is the fix for project server 2013 "The permissions for all users who should have access to a project site may be synchronized incorrectly when you publish a project."

    the same as the fix in july CU and August CU "If you publish many projects to a Project server in a very short time span, the "Synchronize Project Web App Permissions to Project Site" user synchronization job may fail and you may no longer be able to access
    the given project site"?

    I have the september CU installed but this specific problem still occurs.

Skip to main content