Project and Project Server and SharePoint October 2007 Cumulative Update
Updates for Project Server 2007

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.

Deploy cumulative updates (Project Server 2007)

http://technet.microsoft.com/en-us/library/dd239177.aspx

Service Pack 2 for both WSS and Office Servers 2007 are required for this Cumulative Update. The KB articles below provide information on how to download and install SP2 if you have not already done so.

Note: The SP2 Requirement is new as of the August 2010 Project and Project Server 2007 Cumulative Updates.

Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2

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

Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2

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

The Server 2007 CU is released in two different versions. The first version is in Individual Packages specific to a particular product like WSS and Project Server. These are smaller downloads but they do not include language packs or patches for other products so patches for those products would have to be downloaded and installed separately. 

The second version is the Server Rollup Packages. This is a set of two rollup packages which contains all the fixes for WSS, Project Server and MOSS. These packages should be used when MOSS is part of the deployment and/or you have language packs installed. The Server Rollup Packages are much larger (~100MB each) but they will greatly simplify MOSS patch deployment.

You can read about the fixes included in the October CU from the following articles:

• Server Rollup Packages: Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): October 26, 2010 http://support.microsoft.com/kb/2412268
• Description of the Office SharePoint Server 2007 Cumulative Update server hotfix package (MOSS server-package): October 26, 2010 http://support.microsoft.com/kb/2412267
• Individual Product Packages: Description of the SharePoint Server 2007 hotfix package (sts-x-none.msp): October 26, 2010 http://support.microsoft.com/kb/2412258
• Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp; Pjsrvwfe-x-none.msp): October 26, 2010 http://support.microsoft.com/kb/2412269
• Description of the Office Project 2007 hotfix package (project-x-none.msp): October 26, 2010 http://support.microsoft.com/kb/2412260
• Client Installation: In order to install this hotfix, you will need to have Microsoft Project 2007 SP2 installed on the client.
• Description of Office Project 2007 Service Pack 2 (SP2) and of Office Project Language Pack 2007 Service Pack 2 (SP2) http://support.microsoft.com/kb/953326

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

The Microsof Office Project Support blog is reporting an issue that has appeared for users of Project Server 2007, Service Pack 2 and its connectivity to Project Professional when trying to update the Enterprise Global settings. 

There is a fix in the pipeline which should see the light of day in August which we will report to you here. 

There is both a description of the problem and Microsoft’s suggested workaround.

Description:
The problem and fix is for Project Professional 2007, but only in an Enterprise environment with connectivity to Project Server 2007.  the views that are referenced here are the views within the client application. 

When you open the Enterprise Global from Tools, Enterprise Options, Open Enterprise Global and then go to edit a view (View, More Views) you will find that the view it brings up for editing is not the one you thought you should see, but a random view from the list.

Suggested Workaround:
The suggested workaround is that those few administrative users who need the ability to open the enterprise global should hold off installing SP2, but instead install SP2 with the August Cumulative Update when it becomes available. 

If you have already upgraded to SP2 then just for those few admins who need to open the EGT you could return to pre-SP2.  First make sure that for the user who needs to be “downgraded” that their projects are checked in, then uninstall Project Professional, then remove your cache files from <drive>:\Documents and Settings\<user>\Application Data\Microsoft\MS Project\Cache (or for Vista and Windows 7 users <drive>:\Users\<user>\AppData\Roaming\Microsoft\MS Project\Cache)  and then re-install to the level you were at prior to SP2.

The reason for checking in your projects first is that deleting from the Cache will lose any local changes that have not been saved. 

If you prefer not to go dabbling and deleting in the OS then another option would be to create a new connection account that would then give you a brand new cache.  This refers to the account you set up in Office Project Professional 2007 on the Microsoft Office Project Server Accounts page. You can access this page by clicking the Tools menu and then clicking Enterprise Options.

For more information on the local cache can be found at Understanding the Local Project Cache feature.

News out of Microsoft today that we’ve already seen here with at least one client.  It seems that upgrading your Microsoft Office SharePoint Server (MOSS) or Microsoft Project Server environments to SP2 results in your SharePoint environment being converted back into a Trial version.  If not changed back, you may see a message saying that “the trial edition will expire in October 2009″ or to some other date or even “trial edition has expired”.

The fix is pretty easy.  You’ll need to re-enter the Product Key in the WSS Central Administration page.