Project server 2007 august 2012 cumulative update

Edit Access. A named Enterprise resource is assigned to one or more tasks in the schedule and the schedule has been published. Edit access allows the user to create and edit items in lists or libraries within the project site. Designer Access. This is generally provided to the project manager as the owner of the project. It extends the edit access by allowing this user to perform design type changes such as adding or modifying list columns, views and certain list or library type settings.

Full Access. Administrator access which provides Full Access to the project site. This generally handles the majority of security requirements however there are situations whereby your project site requires a bit more flexibility. For example the Project Manager may require a secured area to maintain Project sensitive documentation. To achieve this requirement we can utilise the SharePoint security model but there are some rules to abide by.

The following process provides instructions on how private document library can be configured and secured in a project site. Please note the same concept can be applied to any SharePoint list or library within the Project Site. Navigate to the Project site. Complete the base details. Consider turning on version control as this is a nice SharePoint feature to utilise.

By default the library will inherit permissions from its parent. Click OK to confirm the change. Ensure you leave administrator accounts and most importantly, your own account. The trick with configuring unique project permissions is to ensure the user is not associated to any of the project server permission.

Leaving the Project Server permission could result in a loss of permissions the next time a project site permission synchronisation job is triggered.

Click OK to apply the permission change. Using this same technique, unique permission can be applied to any list or library within the project site. It is also worth mentioning this example reveals how to secure an individual document library but unique permission could also be set at an individual item level within the library or list. The following table provides a mapping between SharePoint permissions and Project Server monitored permission within the Project Site.

SharePoint Permission. Project Server Monitored Permissions. Readers Microsoft Project Server. As the name suggests, provide read access to the project site. This access is generally triggered by adding a named Enterprise Resource to the Project schedule and the schedule has been published. Team Members Microsoft Project Server. Provides edit access to the project site.

Project Managers Microsoft Project Server. Web Administrators Microsoft Project Server. Even AD groups can be added and granted permission in the same way as a single user. It is also worth mentioning SharePoint groups can also be used to maintain project site permissions. Version Number. Download Link. Original Version. Service Pack 1. June CU. August CU. October CU. December CU. Feb CU. April CU. To locate your Project Professional version number. Open MS Project.

Note the version number at the top of the dialog box. Issues that this service pack fixes. Project is very slow to respond when you sychronize with a SharePoint Tasks list. Changes that you make to the Print Properties dialog settings do not take effect when you print the document.

When you add a task to the timeline and then cut that task and paste it in another location on the timeline, the task will no longer appear on the timeline. The only way to get it to appear on the timeline is to re-open the project plan. Task information is not imported correctly from a tab-delimited file to a project file on the server. After you set up a new baseline, the "Baseline Work" and "Work" values do not match.

Saving a file in the Project format can corrupt the file. When you remove leveling, pinned tasks that have actuals are moved. When Project checks to see whether an assignment is over allocated, the program incorrectly checks whether the resource is over allocated at any time during the span of the task. Because of this behavior, assignments may be falsely flagged as over allocated.

After SP1, Project instead correctly checks to see whether the resource is over allocated at any time when there is work on the assignment. Find and replace does not work for some Romanian characters. This update has a prerequisite. Note This is build We recommend that you test those hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new release contains all the hotfixes and security updates that were included with the previous Project Server update package releases.

Important notes about the cumulative update package. The Microsoft Office hotfixes are now multilingual. I have just updated my virtual machine with the last October CU. One big change in this CU is the following: This hotfix configures the Approval Center to highlight task updates when a task is updated in Project Server I try to repro this change in order to understand how the updates are highlight.

The following is what I get in my test. In my opinion is a good and important change for Project Server , definitely. October CU live now! November 2, Leave a comment. August CU live now! September 5, Leave a comment. For more detail about how to apply update and other useful informations, see Brian Smith Blog here Again you can register on a webcast on September 27th by Brian Smith and Adrian Jenkins for detailed informations on this CU Good fix! April CU live now!