This is an updated version of the post from February, 2010, when Project Professional 2010 and Project Server weren’t really in the wild yet.  I have now included the 2010 versions and updated the 2007 information.  This information is everything I could find as of January 10, 2012.

I am asked “What release (version) of Project do I have?” and “What is the latest update?” quite often and this is an attempt to help answer those questions.  And, this also answers the question about what the differences are between a hotfix, patch, update and service pack.

Please note – always read the installation instructions on any update for software as there are pre-requisites that sometimes must be installed first or at best the update won’t work and at worst case it could stop your program from working at all.  And, of course, always back up your software and data prior to patching anything!  Also note that it is important that the Server and Client versions of the software stay as close to the same version as possible with updates as problems can occur if they are not equal.

2010 Versions

Note that along with Project Server 2010 you need to update SharePoint Server 2010.  They aren’t just dating like they we in 2007, they are fully married now and almost always both have to be updated for full effect.  (I put some SharePoint 2010 update information at the end of this post.)

To see what version of Project Professional 2010 is on your computer, open Professional, go to File, Help and on the right hand side will be the Version number under the “About Microsoft Project” heading.  This is known as the “Backstage” area and is listed that way in the table below.  There is also a link called “Additional Versions and Copyright Information” which gives a bit more information if you select it.  Or, you can go to your Control Panel and view the version at that location.  The version numbers will look different in the Control Panel or in the Professional.  The list of the Project Professional versions are in the following table.

The information in the tables below for Project 2010 and Project Server 2010 comes from Brian Smith’s blog (http://bit.ly/cHxHPW).

Project Professional 2010

June 2011                 Service Pack 1 – Build 14.0.6106.5000        KB 2460047

August 2011             Build 14.0.6109.5000                                      KB 2584056

October 2011           Build 14.0.6112.5000                                       KB 2596498

December 2011       Build 14.0.6114.5000                                       KB 2597006

For Project Server 2010

Also from Brian Smith’s blog (http://bit.ly/cHxHPW) is this information on how to run a query or use the control panel to get the version.

The version can be different depending where you look, so I will tabulate the version you will see in Control Panel, Programs and Features (binary version) or on the individual binaries – which is also listed in Central Administration under Upgrade and Migration, Check Product and Patch Installation Status – and also the version you will see in the databases. I’ll mention too various other components that might be of interest. I have listed just the Project Server KB for the CU – but the DB Version noted for SharePoint assumes that either a SharePoint Server or Server rollup has also been installed

As a reminder to get the version from the database there is a table in each SharePoint DB, and each Project Server DB called Versions so a query such as the following will return the current version, which will be the highest Version next to the NULL GUID.

USE <PROJECTSERVERNAME>_Published

SELECT * FROM Versions

WHERE VersionId =’00000000-0000-0000-0000-000000000000′

June 2011                       Service Pack 1 – Build ​​14.0.6029.1000      KB 2460047

August 2011                   Build 14.0.6109.5005                                     KB 2553049

October 2011                 Build 14.0.6112.5000                                      KB 2596506

December 2011             Build 14.0.6114.5000                                      KB 2597015

­2007 Versions

To determine the version of Project that you have, open Project Professional, go to Help and then select About.  (There are other ways to determine the version, but we will only cover this one method.)

A pop-up box will appear and the top line will have the information that answers the question “What version of Project do I have?”  The first part of the line will be descriptive of the version and will say something like “Microsoft Office Project Professional 2003” or “Microsoft Office Project 2007” (or 2000, 2002, 2010) as appropriate.

The next part of that line is the “File Version” or “Build” for that product.  If you have installed a Service Pack then the file version or build of the Service Pack is listed as well.  Here is an example:

“Microsoft Office Project 2007 (12.0.6524.5000) SP2 MSO (12.0.6425.1000)”

This means that this computer is using Project 2007 with the December 15, 2009 hotfix update (found by knowing what the number “12.0.6524.5000” means) and with Service Pack 2 that has been updated with the latest Office Service Pack (that is what “12.0.6425.1000” means).

I have included a list below of the Project 2007 release numbers as of today, with the Microsoft KB article explaining the modifications:

I don’t have a full listing for Project 2003 like I provided above for 2007, but here are the original release values for Project 2003:

How do you determine what version of Project Server are you running?  If you go to the Project Server itself, to the currently installed program list it will have a line for Project Server.  In the 2007 version, that is called “Microsoft Office Project Server 2007”.  When you select that line, there is a “Click here for support information” option.  Selecting that will bring up a pop-up with the server version of the product that you are using.

As a rule, the file version of the Server should be the same as the file version on the Client.  When the client says this:  “Microsoft Office Project 2007 (12.0.6524.5000) SP2 MSO (12.0.6425.1000)” the Server version should also be “12.0.6425.1000” – demonstrating that they are on the same Service Pack.

Here are the Project Server 2007 release numbers as of today:

Finally, here are the definitions and differences of the various update types (as taken directly from Microsoft’s TechNet Project information):

Hotfix:

A hotfix is a single cumulative package composed of one or more files used to address a problem in a product. A hotfix addresses a specific customer situation and is distributed by Microsoft Customer Service and Support. Customers may not redistribute hotfixes without written, legal consent from Microsoft.  Individual hotfix releases are no longer available. Hotfixes are released to customers by Microsoft Customer Service and Support through cumulative updates.

Cumulative Update:

A Cumulative update is a method of providing hotfix releases on a scheduled delivery basis for Office Server products, including Office Project Server 2007. Through this model, Office hotfixes are released every two months in the form of a downloadable package of current and previous hotfixes. The primary goal is to deliver high-quality fixes on a predictable schedule.

Service Pack:

A service pack is a tested, cumulative set of all hotfixes, security updates, critical updates, and updates. Service packs may also contain additional fixes for problems that are found internally since the release of the product and a limited number of customer-requested design changes or features. Microsoft service packs are public updates that are available for download from the Microsoft Download Center.

Infrastructure Updates:

The Infrastructure Update for Microsoft Office Servers is a set of public updates to improve platform performance and also contains several customer-driven fixes.

The SharePoint updates also are important.  I ran across this blog posting from Technet’s Joe’s SharePoint Blog (sorry, I don’t know the author’s name).  (http://blogs.technet.com/b/sharepointjoe/archive/2011/02/01/sp2010-sharepoint-2010-build-level-and-version-numbers.aspx)

I removed non-SharePoint information and the download and revisions columns.

​October   2010 CU​SharePoint Foundation​ 2010KB2394323​14.0.5128.5000​October   2010 CU​SharePoint Server 2010​KB2394320​​​​​14.0.5130.5002​​December 2010 CUSharePoint Foundation 2010

​KB2459125   ​14.0.5130.5002​

​December 2010 CU​SharePoint Server 2010​KB2459257​​​​​14.0.5136.5002​February 2011 CU​SharePoint Foundation 2010

​KB2475880​14.0.5136.5002​February 2011 CU​SharePoint Server 2010​KB2475878​​​​14.0.5138.5000​April 2011 CU​SharePoint Foundation 2010​KB2512804​14.0.5138.5000​April 2011 CUSharePoint Server 2010​​KB2512800​14.0.6029.1000​Service Pack 1​SharePoint Server 2010​KB2460045​14.0.6029.1000​Service Pack 1​Office Web AppsKB2460073​14.0.6029.1000​Service Pack 1​SharePoint Foundation 2010KB2460058​​​​​14.0.6105.5000​June 2011 CU Version 1​​SharePoint Server 2010​KB2536599​14.0.6105.5000​June 2011 CU Version 1​SharePoint Foundation 2010KB2536601​​​​​14.0.6106.5002​​June 2011 CU Version 2​​​SharePoint Server 2010​KB2536599​14.0.6106.5002​​June 2011 CU Version 2​SharePoint Foundation 2010KB2536601​14.0.6105.5000​June 2011 CU​Office Web AppsKB2553919​​​​14.0.6109.5002​August 2011 CU​SharePoint Server 2010KB255304814.0.6109.5000​August 2011 CU​​SharePoint Foundation 2010KB255311714.6112.5000​October 2011 CU​SharePoint Server 2010KB259650514.6112.5000​​October 2011 CU​​​SharePoint Foundation 2010KB259650814.6112.5000​​October 2011 CU​​Project Server 2010KB2596506

This article, written by Collin Quiring, first appeared in Wellington Project Management newsletter in December  2011. (http://www.projectserver2010.co.uk/2011/11/08/resource-management-with-project-server-2010/)

Last time we started this two-part article by asking some questions about resource management that might be on your mind.  We focused on six questions.  They were:

• ·         Who is working on what projects?
• ·         What tasks are they doing on those projects?
• ·         When are they doing those tasks?
• ·         How many hours of work are assigned for those tasks?
• ·         What is the capacity of each person?
• ·         Who is scheduled to their capacity, over-capacity or dramatically over-capacity?

We also focused on how to see all the resources assigned to one project and then seeing how one resource can see their information.  Our goal in this article is to see how Project Server 2010 allows us to see the information for a resource assigned to many different projects and to see all the resources from the perspective of a schedule or multiple schedules.

In Part One, we looked at our resource, Shelly Smith, for a time period where she was assigned to one schedule.  Now, we need to look at a time period where Shelly is assigned to many different schedules.  Since the picture view might be more easily understood, we will review that one first.  The black line represents Shelly’s capacity – at 40 hours a week.  The blue bar represents the amount of work assigned.  We can easily see that she is way over capacity! 

Now we can review which projects are causing these problems by reviewing the data view.  (We review this in image form at the end of this article.)  We can see that she is over capacity by between 24 and 104 hours for January.  Be able to review this information allows you to go to the various Resource Managers or Project Managers (or the resource) and discuss what the priorities are and what tasks can be moved to other resources or other time periods.  From this chart, we can determine that the Resource Managers for both the “Infrastructure Plan” and the “Residential Construction” schedules think they have 100% of Shelly’s time for the week of 1/9/12.

If one of the potential results of seeing a view like this is to determine if we can move work to other resources we need to be able to see those resources for the same time period.  We can look at each resource individually as we have done or we can see all the resources that we want to during this time period.  For this example, I have chosen to include two more resources, Ryan and Jessica.  I now have a new black line that represents the capacity of all three individuals and I can see the work assigned for the three of them combined.  Note that Shelly is now the yellow and that Ryan is green but Jessica is Blue and she is seriously UNDER capacity.  In one quick look we know who can get some of Shelly’s work.  And, we have also discovered that Ryan is over capacity.

These last few images were from the resource’s perspective but we can also view the work from the schedule perspective.  Earlier, while we were concentrating on Shelly, we looked at which projects were assigning her the most work.  But, we can view how many hours of work are being assigned to resources based on the perspective of projects.

In this chart we are still only looking at three resources but this time by project – that is why the black line representing capacity is still at 120 hours a week (40 hours each per week).  But on the right hand side the names of the projects are all color coded.  Just by reviewing the chart we can determine that the “Commercial Construction” project is taking the most time for the most weeks.