The Microsoft Project and Project Server 2010 Service Pack 1 were released today. You can read about it here:
announcing-the-release-of-service-pack-1-sp1-for-microsoft-project-and-project-server-2010
To entice you to read the article and get yourself up to date (after a reasonable testing period of course) I present my list of the top ten reasons to install SP1. Without out it you face these potential problems:
- Saving a file in the Project 2007 format can corrupt the file.
- Project is very slow to respond when you sychronize with a SharePoint Tasks list.
- After you set up a new baseline, the "Baseline Work" and "Work" values do not match.
- When you remove leveling, pinned tasks that have actuals are moved.
- You are editing a project plan that is stored on a remote computer when the remote computer becomes disconnected. You are prompted to save the file locally, and you click OK. If you cancel the save process, any future saves will cause a crash.
- When the Team Planner view is opened, Project stops responding.
- When you have more than one project open and connected to the server and you save a baselines in one of the plans, the timephased baseline data in the other plan is changed.
- Text fields are not visible for a project that is saved in Project 2007 format in Project 2010 and then opened in Project 2007.
- Project does not refresh earned values (such as BCWS) when you click F9.
- Data corruption occurs for custom number fields.
Comments (2)
Yes
And reason to damage pf MSPS. :)
http://blogs.msdn.com/b/brismith/archive/2011/07/06/project-server-2010-sp1-and-june-2011-cu-formatexception-when-trying-to-provision-a-pwa-site.aspx
Posted by Vladimir Ivanov | August 10, 2011 11:10 AM
Posted on August 10, 2011 11:10
I heard that SP1 also resolved the Auto Scheduled Task Sync Issue with Sharepoint Calendar, is it True?
I believe that is the case, but with any thing, test it first before you believe it. -Jack
Posted by Senthil | February 8, 2012 10:23 PM
Posted on February 8, 2012 22:23