Microsoft has announced the release of the April 2013 Cumulative Update (CU) for Project, Project Server and SharePoint for 2007, 2010 and 2013.
You can find the details of the updates here: http://blogs.technet.com/b/projectsupport/archive/2013/04/11/microsoft-project-server-2007-2010-and-2013-april-2013-cu-announcement.aspx
Note that March 2013 Public update of Project Server 2013 was set as baseline requirement for all the future updates of Project Server 2013, however there was an issue with running the SharePoint Configuration Wizard after applying March 2013 update on a server with Project Server 2013 installed and this is fixed by applying the April CU – so a good practice would be to load the March PU, then the April CU and then run the configuration wizard.
Detail of March 2013 update issue can be seen here: http://blogs.technet.com/b/projectsupport/archive/2013/04/11/project-server-2013-march-public-update-problems-running-the-sharepoint-configuration-wizard.aspx
Also note that there is a slight delay in Project Server 2013 roll out package, the package includes SharePoint server fixes as well since Project Server 2013 is based on SharePoint platform and Microsoft recommends to apply the update package on your environment.
Due to the issue with the March PU and running the Configuration Wizard, you could consider loading the individual Project Server patch which does not include the SharePoint updates http://support.microsoft.com/kb/2760261 if you need to get the configuration of the March PU completed. If you haven’t yet loaded the March PU then I would suggest waiting for the roll-up package for the April CU.
And as usual, always try the patches to test servers prior to apply to productions environment.
You can find the details of the updates here: http://blogs.technet.com/b/projectsupport/archive/2013/04/11/microsoft-project-server-2007-2010-and-2013-april-2013-cu-announcement.aspx
Note that March 2013 Public update of Project Server 2013 was set as baseline requirement for all the future updates of Project Server 2013, however there was an issue with running the SharePoint Configuration Wizard after applying March 2013 update on a server with Project Server 2013 installed and this is fixed by applying the April CU – so a good practice would be to load the March PU, then the April CU and then run the configuration wizard.
Detail of March 2013 update issue can be seen here: http://blogs.technet.com/b/projectsupport/archive/2013/04/11/project-server-2013-march-public-update-problems-running-the-sharepoint-configuration-wizard.aspx
Also note that there is a slight delay in Project Server 2013 roll out package, the package includes SharePoint server fixes as well since Project Server 2013 is based on SharePoint platform and Microsoft recommends to apply the update package on your environment.
Due to the issue with the March PU and running the Configuration Wizard, you could consider loading the individual Project Server patch which does not include the SharePoint updates http://support.microsoft.com/kb/2760261 if you need to get the configuration of the March PU completed. If you haven’t yet loaded the March PU then I would suggest waiting for the roll-up package for the April CU.
And as usual, always try the patches to test servers prior to apply to productions environment.
0 comments:
Post a Comment
Spammers, don't waste your time as the comments will only appear after moderation.